Microsoft Office Error 1402
Contents |
Xbox error 1402 setup cannot open the registry key office 2013 360 games Windows games Games for Windows
Error 1402 Setup Cannot Open The Registry Key Unknown Components
Phone Entertainment All entertainment Films & TV Music Business & Education error 1402 uninstall office 2010 Business Student store Sales Back to school Sales Gift cards Products Software & services Windows Office Free downloads error 1402 office 2013 & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Films & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC Accessories Xbox
Error 1402 Office 2013 Windows 7
& games Microsoft Lumia For business Cloud platform Microsoft Azure Microsoft Dynamics Windows for business Office for Business Skype for Business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN Technet Visual Studio For students & educators Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United Kingdom) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Modules Notable Users Brochures Testimonials Supported Platforms NuGraf PolyTrans-for-Cinema-4D PolyTrans-for-3ds Max PolyTrans-for-Maya NuGraf 3D Toolkit Specialized Sections Image Galleries Download Demos Sales/Ordering Support & Updates Developer Info Press Info Contact Okino Links Sales: 1-888-3D-OKINOSupport: 905-672-9328Copyright © 2016 OkinoToronto, Ontario, Canada. error 1402 office 2010 How to fix 'Error 1402. Could not open key: UNKNOWN...' Step-by-Step Instructions for error 1402 setup cannot open the registry key hkey_local_machine Windows Vista/Seven/Win2K8-Server Users Microsoft Windows users will find the following short tutorial useful for solving the 'How to fix 'Error
Error 1402 Windows 8
1402. Could not open key: UNKNOWN...' problem which is becoming prevalent in online forum postings. Please use this information at your own discretion. A Quick Overview When installing or un-installing Microsoft Windows component technologies https://support.microsoft.com/en-gb/kb/838687 on Windows Vista/Seven/Win2K8-Server (or newer) you may encounter a message box similar to "Error 1402. Could not open key: UNKNOWN\Components\C9AE13788D0B61F80AF18C3B9B1A1EE8\...", This long number is not an "address" as many believe but rather a registry parent container key name (as a GUID) and its child name (as a GUID). The last "\" character separates the two parent/child GUIDs. This is not related to Okino software, but rather to components which http://www.okino.com/conv/changing_windows_registry_permissions.htm are usually provided by Microsoft Corp. The following tutorial will outline our own personal experiences at Okino Computer Graphics of dealing with this problem. We have seen this problem posted in many forums but the simple solution we outline below which has not been properly documented as we have done so here. Windows Vista/Seven/2K8: How to fix 'Error 1402. Could not open key: UNKNOWN...' The error is generally caused by insufficient or incorrect permissions on the named registry keys, or parent container of such registry keys. For Okino, it occurred on multiple occasions after upgrading some of our machines from Windows 2K3 to 2K8 server or from XP to Windows 7, and then upgrading/re-installing Microsoft products or components (Visual Studio and MSXML4 in our case). It is generally a simple matter to fix, once you know how. We recommended that you back-up your computer or at least the registry before taking this action. Microsoft's built-in backup program allows for the "system state" to be selectively backed up. Or, you can ZIP up the "windows\system32\config" directory while running in a backup operating system (this is where the registry hive files are located). You must be logged in as the 'administrator' (or an account with full admin
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://superuser.com/questions/127013/how-to-solve-microsoft-office-error-1402-on-windows-7 policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered https://support.techsmith.com/hc/en-us/articles/203731008-Snagit-Windows-Error-1402-Could-not-open-key-HKEY-LOCAL-MACHINE Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody error 1402 can ask a question Anybody can answer The best answers are voted up and rise to the top How to solve Microsoft Office error 1402 on Windows 7? up vote 0 down vote favorite I have installed Microsoft Office on my new Windows 7 64-bit system. Recently, it encounter some error and I tried to re-install it. It wasn't successful. So, I error 1402 setup have to use Microsoft Install Clean Up to uninstall Microsoft Office. When I tried to install it again, I received this message: Microsoft Office 2007 encountered an error during setup. Error 1402. Setup cannot open the registry key. {a bunch of long keys}. Verify that you have >sufficient permissions to access the registry or contact Microsoft Product Support Service for >assistance. For information about how to contact PSS, see {a *chm file}. After that, I tried to run the setup as administrator but I ended up with the same error. So what should I do to solve this problem? windows-7 microsoft-office-2007 share|improve this question edited Jan 28 '11 at 22:35 Not Kyle stop stalking me 8,38122144 asked Apr 3 '10 at 6:06 yihangho 1951413 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote Microsoft Install Clean Up to uninstall ... Microsoft Office 2007 Uh... why? Warning The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs. Cautio
Analysis & Sharing iOSAndroidWindows Screencast.com Video & Content Hosting Learn More All Products & Downloads › Help Find Software Key Tutorials Support Community Product Registration All Help Options Company About Contact Careers Partner Programs Press Room Customer Stories Email Subscription All Company Information Blog TechSmith Blog Store TechSmith Store Education Pricing Gov't/Non-Profit Pricing Volume Pricing Online Store FAQ All Store Options Contact Us U.S. English U.S. English Deutsch Français 日本語 0 Items 0 My Account Sign In Sign in My Account Sign Out Submit a ticket View your ticket(s) Sign in to chat Need help? Chat with us Need help? Chat with us TechSmith Support Snagit (Windows) - Technical Issues Install Choose another category Snagit (Windows): Error 1402 Could not open key: HKEY_LOCAL_MACHINE Posted by: Mike Spink Last Updated: March 31, 2016 16:19 To resolve this Error Message, please use the following steps: Depending on your version of Windows, use these steps to open the Registry Editor: Windows XP: Open the Start Menu, click Run, and type regedit, then press EnterWindows Vista / 7:Open the Start Menu, click in Search programs and files, type regedit,then press EnterWindows 8 / 10:Right click on the Start button and choose Run.  Then type regedit and hit Enter. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Classes Right-click on Classes and go to Permissions Depending on your version of Windows, this step will vary: Windows XP Click on Advanced and verify your Username is listed there and that the following checkbox is checked: Click Apply and OK to apply the changes in order to correct this issue. Windows Vista / 7 / 8 / 10 Confirm the User Group you belong to, such as Administrators or Users, then click on Advanced to confirm that your User Group's permission is set to Full Control: If the permissions are not set properly, or if your User Group does not have the correct permissions you will need to correct this issue. Once you have corrected the permissions, close Registry Editor and try to insta