The problem started with Windows Update not working. "Errors found: Code 80080005 Windows Update encountered an unknown error."
I think I have narrowed it down to the following root cause: my configuration registry database is corrupt.
Here is my question: how do I fix my configuration registry database without doing an in-place upgrade or reinstall?
Some symptoms:
I have tried resetting Windows Update, I have tried installing the Windows Update Readiness Tool to troubleshoot but failed installing it, I have tried the Registry key with RegistrySizeLimit, and a bunch of others I can't remember.
Basically, my problem boils down to this link which shows some people running into this very same issue but no solution, as far as I can tell.
Someone on reddit pointed me to https://www.sysnative.com/forums/windows-update/3791-windows-update-not-working.html, which prompted me to post here. I tried to load the COMPONENTS hive as described here, but I get the following error: "Cannot load COMPONENTS: Error while loading hive." The file is around 30 MB, the total folder size is around 100 MB, way below the 2 GB limit...
Any ideas or pointers?
I do not have a system restore point, btw, so that is not an option... I assume there must be an easy way out, since I don't really have a custom config, so I am sure restoring some standard registry keys must fix this...
I think I have narrowed it down to the following root cause: my configuration registry database is corrupt.
Here is my question: how do I fix my configuration registry database without doing an in-place upgrade or reinstall?
Some symptoms:
- Starting Windows Modules Installer in services.msc gives me "Error 1009: The configuration registry database is corrupt."
- sfc /scannow in elevated cmd prompt yields "Windows Resource Protection could not start the repair service."
- C:\windows\logs\cbs\cbs.log shows:
Code:
2013-09-15 17:35:56, Info CBS Starting TrustedInstaller initialization.
2013-09-15 17:35:56, Info CBS Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cbscore.dll
2013-09-15 17:35:57, Info CBS Failed to load the COMPONENTS hive from 'C:\Windows\System32\config\COMPONENTS' into registry key 'HKLM\COMPONENTS'. [HRESULT = 0x800703f1 - ERROR_BADDB]
2013-09-15 17:35:57, Info CBS Failed to load WCP DLL. [HRESULT = 0x800703f1 - ERROR_BADDB]
2013-09-15 17:35:57, Info CBS Failed to initialize the Core DLL: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cbscore.dll [HRESULT = 0x800703f1 - ERROR_BADDB]
2013-09-15 17:35:57, Info CBS Failed to initialize CBS Core. [HRESULT = 0x800703f1 - ERROR_BADDB]
2013-09-15 17:35:57, Info CBS Ending TrustedInstaller initialization.
2013-09-15 17:35:57, Info CBS Failed to initialize Trusted Installer. [HRESULT = 0x800703f1 - ERROR_BADDB]
2013-09-15 17:35:57, Info CBS Starting TrustedInstaller finalization.
2013-09-15 17:35:57, Info CBS Trusted Installer core was not initialized.
2013-09-15 17:35:57, Info CBS Ending TrustedInstaller finalization.
I have tried resetting Windows Update, I have tried installing the Windows Update Readiness Tool to troubleshoot but failed installing it, I have tried the Registry key with RegistrySizeLimit, and a bunch of others I can't remember.
Basically, my problem boils down to this link which shows some people running into this very same issue but no solution, as far as I can tell.
Someone on reddit pointed me to https://www.sysnative.com/forums/windows-update/3791-windows-update-not-working.html, which prompted me to post here. I tried to load the COMPONENTS hive as described here, but I get the following error: "Cannot load COMPONENTS: Error while loading hive." The file is around 30 MB, the total folder size is around 100 MB, way below the 2 GB limit...
Any ideas or pointers?
I do not have a system restore point, btw, so that is not an option... I assume there must be an easy way out, since I don't really have a custom config, so I am sure restoring some standard registry keys must fix this...