Unable to delete registry key that is causing problems with Windows Installer on Win 7

Hi all,

 

I have a problem, mainly with Windows Installer, that is preventing me from installing several things, most noticably .NET 2 and 3 and Visual C# Studio 2010.

 

From looking around the net for answers, and noting other related problems (such as the Turn Windows Features On and Off of Programs and Features not populating) and attempting to follow the fixes listed there, I think I have narrowed the problem down.

 

When attempting to run anything which makes use of the Windows Installer, CBS.log brings up the following error:-

[code]2012-12-07 23:43:32, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #3028289# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x13aca50->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[168]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..l-keyboard-00000850_31bf3856ad364e35_none_e4f2a31a524552fc\6.1"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 20631064 (0x013ace18))[gle=0xd0000034]
2012-12-07 23:43:32, Error                 CSI    0000000e@2012/12/7:23:43:32.013 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2012-12-07 23:43:32, Error                 CSI    0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #3028288# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 0, da = (KEY_READ), oa = @0x13acf10, key = NULL, disp = (null))[gle=0xd0000034]
2[/code]

 

Going to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..l-keyboard-00000850_31bf3856ad364e35_none_e4f2a31a524552fc\6.1 in the registry brings me to a corrupt entry. Clicking on the 6.1 Key in the tree brings up the error message:- "Error Opening Key. 6.1 cannot be opened. An error is preventing this key from being opened. Details: The system cannot find the file specified." And clicking okay on that reveals no values in the right pane, whereas all the other very similar nearby keys have a REG_SZ value called (Default) and data of 6.1.7600.16385 and a REG_BINARY called 6.1.7600.16385 with a data of 01.

 

As the value apparently refers to the Mongolian (Mongolian Script) Keyboard layout (KBDMONMO.dll) it's kind of annoying as I don't think I would ever have need of that keyboard.

 

I cannot rename, delete or add values to, or look at permissions on the key to try and fix it, and RegDelNull and CCleaner don't register it as a problem registry entry.

 

I am unable to use system restore (0x80042302 error) and the system also failed when attempting a Repair Install. sfc /scannow under admin level prompt fails with Windows Resource Protection could not perform the requested operation and populations the CBS log with the above CSI error message. The FAST wizard also fails (so there would be no easy way of transferring info over to a clean install of Windows 7).

 

I have also ran the system update readiness tool which fixed some errors, but not that one.

 

OS:- Microsoft Windows 7 Ultimate 64bit insall
Version:- 6.1.7600 Build 7600
System Type:- x64-based PC
Processor:-Intel Core i5 CPU 760

 

Thanks for any help

 

Question Info


Last updated November 9, 2018 Views 4,623 Applies to:
Restart your computer and immediately tap on the F8 key until you reach the Advanced Boot Optionsmenu. Select Repair Your Computer (If you do not see that option, you will need a Windows Recovery disc). This will take you to the System Recovery Options menu. Select System Restore.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

A bit of a delayed respone Justice 3X, but that unfortunately did not work as I did not have an earlier enough system restore (for that matter they all appeared to be missing).

 

 

However, I did manage to find a way to fix this elsewhere.

 

****Back up your registry first, this may not work for you****

 

1. Go to the parent key in the registry, and then export that as a .reg file (ie in my case HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners).

 

2. Edit this .reg file in an editor (Notepad works) and either delete the problem key, or modify it to be correct.

 

3. Create a dummy key somewhere in the registry. (I created HKLM\Software\dummykey).

 

4. Export this dummy key as a registry hive file

 

5. Select the parent key you exported earlier, and then import the dummykey registry hive over it. This should wipe the contents of the parent key including the problem key.

 

6. Import the parent key exported .reg file back into the registry by double clicking on it. If you have fixed or deleted the problem key, it should now be gone, and all the other keys that the above step deleted should have been restored.

 

7. Delete the dummy key you created at step 3.

 

 

Hope that helps anyone else that has a similar problem.

13 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

TDarksword, your procedure worked perfectly. I've made a note of it. Thanks for sharing.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you!!! Finally. Why does your fairly simple solution took so long to find? There are literally hundreds of other search results pointing to permissions and such, but this is the only one that helped.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.