2011-05-15 00:47:23, Error                 CSI    00000009 (F) STATUS_RM_NOT_ACTIVE #154# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_SET_VALUE|KEY_WOW64_64KEY), oa = @0x17ff0e0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[28]"\Registry\Machine\COMPONENTS"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 25162328 (0x017ff258))[gle=0xd0190005]
2011-05-15 00:47:23, Error                 CSI    0000000a@2011/5/14:22:47:23.902 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_RM_NOT_ACTIVE originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

This must be some kind of serious error because a WER report is being made from this error. Unfortunately no solution is available.

Often a problem is just that you haven't rebooted recently enough (there's an internal lock for updates held by the MSI installer which can get screwy). It's definitely worth rebooting and trying again with no programs running, even if that is somewhat cliche'd (I for one never reboot - I always hibernate so you might not have rebooted cleanly in months)

You get a WER report because whoever wrote that update isn't propagating the error code upwards, and are probably ending up doing a null-dereference to crash wuacult.

If all of this doesn't work, try and do a system restore. This will clear out any bad updates that you might have recently downloaded and put you back to a "clean" state.

• I'm running Windows 7 SP1.
• I always reboot the system. With my SSD I can't put it in stand-by.
• The update that fails is http://support.microsoft.com/kb/2446710 

Why is the result 0xC0190005 ?

Your best bet with any Windows Update errors is to try and roll back using System Restore. System Restore only changes files and folders in your system directory, so it won't kill any of your other files so you shouldn't need a full backup (although there's certainly no harm in doing so).

After performing a System Restore, reboot the machine and then force a refresh of Windows Update by asking Windows Update to "search for updates".

If this doesn't work, or it keeps happening even after you roll back, you have two choices:
A) Leave it alone and it will go away. It'll take a while but Microsoft release "super patches" which fix Window Update, and the very fact that Windows Update is failing on your machine will be being reported to Microsoft via the Windows Update Automated Error Reporting Tool.

B) If you really really want to get those updates (and let's face it, who doesn't want their juicy goodness) you can try flushing the transaction queue by clearing the files in %SystemRoot%/config/TxR. These are all of the transacted registry update files created by Windows Update / TransactedRegistry. Wiping them and then rebooting might fix your registry, but bear in mind that messing with the registry and files in %SystemRoot% it might also hose your system, so be warned and backup your files (no really) before you do this.

c:/windows/syswow64/config/TxR is empty. For now I'm not going to mess with the registry.

So the STATUS_RM_NOT_ACTIVE code doesn't tell me any details about the error that happened.

54 minutes ago, ZippyV wrote

@evildictaitor: This has been going for a month so I don't have any restore point which is that old.

c:/windows/syswow64/config/TxR is empty. For now I'm not going to mess with the registry.

So the STATUS_RM_NOT_ACTIVE code doesn't tell me any details about the error that happened.

I get random WU errors occasionally too. I find downloading the manual patches and installing them myself (rather than going through WU) sorts the problem out. Have you tried that?

18:55 Check for updates

18:57 Install update

TrustedInstaller service was not set as autostart, or else a reboot is still pending.

16 hours ago, RhymesWith​Orange wrote

You are saying this has been happening for a month now... what last happened that was out of the ordinary in the month? I mean, you were getting updates without a problem, then something happened, and now you can't.. so what happened?

I looked into the reliability history and noticed the problems began the same day as when Office 2010 updates were (sucessfuly) installed. That might have messed up the TxF system.

The NTFS transaction manager is broken. Delete all files (*.*) from C:\Windows\System32\config\TxR, next run

fsutil resource setautoreset true C:\

Don't forget to set the folder options to show all system and hidden files otherwise the TxR directory will look empty.

I'm almost about to headbang like MagicAndre1981's avatar, as his hints have now solved my problem, which was obviously the same as ZippyV's. I know that many people whio had similar problems had resorted to perform an update install of Windows 7. In all the resources I have found so far about the vcredist error 1935 with HRESULT 0x8007054F there was nobody who had a clue what the problem really was about. I have encountered the setautoreset solution somewhere else, but without any reasoning about why it was necessary.

Thanks for posting this solution and also thanks to ZippyV for his perseverence in solving his problem.

If anybody from Microsoft is reading this, it may make sense to spread this knowledge more widely because it might save some people from resorting to more intrusive ways of trying to solve the problem like messing up the registry (I didn't), deleting files by hand in winsxs (I did - had to restore them), etc.

Cheers and happy coding.

6 hours ago, Remigius wrote

If anybody from Microsoft is reading this, it may make sense to spread this knowledge more widely because it might save some people from resorting to more intrusive ways of trying to solve the problem like messing up the registry (I didn't), deleting files by hand in winsxs (I did - had to restore them), etc.

The least they should do is add this solution to the WindowsUpdate repair tool.

Dec 08, 2011 at 3:59 PM, Remigius wrote

as his hints have now solved my problem, which was obviously the same as ZippyV's.

nice to hear that my tip also solved your issue

I was headbanging like MagicAndre1981's avatar because of a transaction manager fault. Why is the vcredist error 1935 sooo poorly documented? I was about to install the Nokia Suite 3.x for a client when I discovered that nothing seems to get installed which required a reboot. Even some Windows updates failed.

So, dear MagicAndre1981, thank you sooooo much for sharing this information about the NTFS transaction manager. It really saved my day and was my very first experience with the FSUTIL command.

Kind regards,

pmm

I have been having a similar issue, except with installing Adobe Photoshop Lightroom. Error 1935 HRESULT 0x8007054F. As per MagicAndre1981's solution, I checked the C:\Windows\System32\config\TxR, there was no file, made sure that 'Show hidden files and systems' was selected but nothing came up.. then ran 'fsutil resource setautoreset true C:\'.. DOS command prompt window appeared and vanished in a millisecond. I figured that would solve the problem, but upon installing the software, same error persists.

I am running Windoes 7, x64. All windows update has been installed successfully, and I have no idea what else to do. Pleas help!

Thanks!

Try this solution: http://forums.adobe.com/thread/847704