You are here: » » Sales: 1-888­-3D-OKINO Support: 905­-672-9328 Copyright © 2017 Toronto, Ontario, Canada. How to fix 'Error 1402. Could not open key: UNKNOWN.' Step-by-Step Instructions for Windows Vista/Seven/Win2K8-Server Users Microsoft Windows users will find the following short tutorial useful for solving the ' How to fix 'Error 1402. Could not open key: UNKNOWN.' Call Of Juarez Download Full Game.

SolidWorks 2017 Premium Full Crack Free Download. SolidWorks 2017 Premium Full Crack are a sophisticated solid modeling. Jul 16, 2013. With Associate in Nursing exciting tool for abstract style in 3D and 2nd constant drawing, likewise as key functions to import and publish PDF files, AutoCAD is loaded with powerful skills to assist you style with a lot of result and documents a lot of quickly. For activation with the key initial scan the installation. AutoCAD LT 2007 AutoCAD LT 2007 Service Pack 2 Readme (html - 40Kb) Please review the ReadMe to make sure. MText or Text editor now displays after the text object is moved to a frozen layer; Two key strokes are needed to enter any non-Unicode special.

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 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. Encarta 2002 Portugues Download. ' , 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 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 administrator access) as well as disabling 'UAC' (User Access Control). UAC is disabled by going into the 'User' control panel applet and selecting the 'Change User Account Control Settings'.

In Windows 7 the next dialog box will display a slider which you will want to set to 'Never Notify'. Excel Vba Examples Download. • From the START menu, execute ' Run.'

And then type ' regedit' • Navigate to the following parent container: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Installer UserData S-1-5-18 Components. The 'S-1-5-18' key may be different on your computer. • As in the screen snapshot above, we wish to look for the first of the two GUIDs, namely ' C9AE13788D0B61F80AF18C3B9B1A1EE8'.

Scroll through the children of the 'Components' key to locate this corresponding first of two GUIDs from the message box shown above. Most often this will have a '+' beside the folder since it'll have one or more children items in it (one of which will be the second GUID from the message box shown above). You can also use the 'Find' command within the registry editor but that is a much slower and more tedious operation to do.