"Error 1402" is a MSI error:-
“Could not open key: . System error .”
The “key” is a Registry Key, and the direct meaning of this error is that some specialised functions of the Windows Registry have become corrupted. I do not know why, although it often seems to be reported by folks that have upgraded from an earlier to a later version of Windows.
Here are some things to try:
- Try the “Microsoft Fix-It” website:-
"Automatically repair issues that block program installation or removal because of corrupted registry keys."
This is an attempt by M$ to help you avoid the ultimate fix for MS Windows, which is to wipe the disc & re-install the OS + Programs from scratch. It is a replacement for the Windows Installer Cleanup utility (MSICUU2.exe) which has been retired by M$ as they said that it corrupted some Registry instead of fixing them (whoops).
The website will test out + fix the Registry. There is also a Windows Update onsite & it seems more thorough than the normal Update.
If you did not use the Windows Update in the previous step, go back & use it. If necessary, after a restart go back & see if there are any more Updates until it reports that everything is updated.
Hack the Registry
(now the scary fix, if the above has not worked)
“manually fix Registry key permissions”
First, you may need to find the bad container.
MSI leaves an extended error message within a file in the user’s profile.
Example: an MSI error whilst attempting to install ‘.NET framework 4.5’
Name of error file: %USERPROFILE%\AppData\Local\Temp\Microsoft .NET Framework 4.5.1 Setup_20140917_191645234.html
Error file content:
MSI (D:\4113948000d14764646c\netfx_Full_GDR_x64.msi) Installation failed.
Msi Log: Microsoft .NET Framework 4.5.1 Setup_20140917_191645234-MSI_netfx_Full_GDR_x64.msi.txt
Msi Log text:
MSI (s) (4C:80) [19:19:19:653]: Product: Microsoft .NET Framework 4.5.1 -- Error 1402.
Could not open key:
System error 5.
Verify that you have sufficient access to that key, or contact your support personnel.
We now have the base key (D30312665D61E0E44A85EEBAFAF27C86\BE4EBED704B66673BB53C5BB3C58AD73). Searching within the Registry with that key identified the “UNKNOWN” in the log-text above as “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18”. Checking the permissions on that key showed them as … none. It did not have any. Jan-Philip Gehrcke shows step-by-step how he added those permissions back into that key & all sub-keys.
In our situation, curiousdisposition knows the key already (HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft\Windows|CurrentVersion|SharedDlls). It is that key (plus sub-keys) that will need correct permissions.
If none of the above works:-
- Wipe the HDD & re-install Windows, then Update.
- At this stage it’s a bug, no mistake.
Use Bugzilla or the Bug Submission Assistant + point out that Windows was installed on to a blank disc then updated immediately prior to LO installation.
If this helps then please tick the answer ()
…and/or show you like it with an uptick (∧)