[SOLVED] "Failed to load the COMPONENTS hive from 'C:\windows\System32\config\COMPONENTS' into registry key 'HKLM\COMPONENTS'. " on Windows 10

D

desseins

Contributor
Joined
Apr 9, 2022
Posts
5
Location
Belgium
Hi
seems my components hive is damaged
noticed some win updates didn't go through with error 0x800703f1 (KB5011543 KB5011487)
after extended troubleshooting, found this great forum
and people with similar issue.
"Dism /Online /Cleanup-Image /RestoreHealth" :

Deployment Image Servicing and Management tool
Version: 10.0.18362.1316

Image Version: 10.0.18363.1316

[== 3.8% ]
Error: 1009

The configuration registry database is corrupt.


attached the logs (SFCFix, DISM and CBS)
shows "Failed to load the COMPONENTS hive from 'C:\windows\System32\config\COMPONENTS' into registry key 'HKLM\COMPONENTS'
attached Components hive from c:\windows\system32\config


I noticed you provided a (fixed) Components hive for other people with this issue, I hope I can obtain one too.

Win 10 Home 21H2 build 19044.1466

Thanks in advance
Kind regards
 

Attachments

Hi,
thanks for looking into this
componentsscanner repaired the components
- 2nd run : all ok
- sfc and dism: results ok
Tried the windows updates -
KB5012117 : OK (Net framework)
BUT got 0x8007371c on KB5012599 (security update) download goes to 100% - install then also seems to progress -> 100 % ; but fails

tried
-reboot + retry
-winupdate troubleshooter
-Rename SoftwareDistribution and Catroot2 (after stopping needed services/ then restarted those)
-download KB from Microsoft Update Catalog + install
-Dism /Online /Cleanup-Image /RestoreHealth
-SFCFix (found no issues)

Any advice ?

Thanks in advance !
(just donated 10$ Transaction ID: 20994223781661228)

Kind Regards
 

Attachments

Rich (BB code): 
2022-04-13 01:44:12, Error                 CSI    000006db@2022/4/12:23:44:12.884 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-04-13 01:44:12, Error                 CSI    000006dc (F) STATUS_OBJECT_NAME_NOT_FOUND #12871538# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xabf5b7cc98->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[24]'\Registry\machine\Schema'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4122462768)[gle=0xd0000034]
2022-04-13 01:44:12, Error                 CSI    000006dd@2022/4/12:23:44:12.885 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-04-13 01:44:12, Error                 CSI    000006de (F) STATUS_OBJECT_NAME_NOT_FOUND #12871537# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xabf5b7cc98->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[24]'\Registry\machine\Schema'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4122463792)[gle=0xd0000034]
2022-04-13 01:44:12, Error                 CSI    000006df (F) STATUS_OBJECT_NAME_NOT_FOUND #12871536# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0xabf5b7d1f8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[24]'\registry\machine\Schema'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4122464808)[gle=0xd0000034]
2022-04-13 01:44:12, Error                 CSI    000006e0 (F) STATUS_OBJECT_NAME_NOT_FOUND #12871535# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenRegistryKey(flags = (OpenForBackupIntent), da = (KEY_ALL_ACCESS), kn = [l:24]'\registry\machine\Schema', key = NULL, disp = Invalid)[gle=0xd0000034]
2022-04-13 01:44:12, Error                 CSI    00000004 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #5# from CWcmEngineCore::UnregisterNamespace(nsid = { name: Microsoft-Windows-Installer-Engine ver: 10.0.19041.1645 lang: neutral arch: wow64 pkt: 31bf3856ad364e35 verSc: nonSxS }, fRemoveSettings = false, target = NULL)
[gle=0x80004005]
2022-04-13 01:44:12, Error                 CSI    00000005 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #4# from CWcmEngineCore::CreateNamespaceWithOptions(nsid = { name: Microsoft-Windows-Installer-Engine ver: 10.0.19041.1645 lang: neutral arch: wow64 pkt: 31bf3856ad364e35 verSc: nonSxS }, fOverwrite = true, target = NULL, namespace = { name: Microsoft-Windows-Installer-Engine ver: 10.0.19041.1645 lang: neutral arch: wow64 pkt: 31bf3856ad364e35 verSc: nonSxS })
[gle=0x80004005]
2022-04-13 01:44:12, Error                 CSI    000006e1 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #6# from CSmiPrimitiveInstaller::ProcessComponent(fromComp = { name: Microsoft-Windows-Installer-Engine, ver: 10.0.19041.1466, lang: neutral, arch: wow64, pkt: 31bf3856ad364e35, verSc: nonSxS }, toComp = { name: Microsoft-Windows-Installer-Engine, ver: 10.0.19041.1645, lang: neutral, arch: wow64, pkt: 31bf3856ad364e35, verSc: nonSxS })
[gle=0x80004005]
2022-04-13 01:44:12, Info                  CSI    000006e2 SMI Primitive installer failed.

2022-04-13 01:44:12, Error                 CSI    000006e3@2022/4/12:23:44:12.885 (F) onecore\base\wcp\primitiveinstallers\settingsinstaller.cpp(611): Error STATUS_SMI_PRIMITIVE_INSTALLER_FAILED originated in function CSettingsInstaller::ProcessComponentChange expression: (null)
[gle=0x80004005]
2022-04-13 01:44:12, Error                 CSI    000006e4 (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #12871517# from CSettingsInstaller::ProcessComponentChange(...)[gle=0xd0150025]
2022-04-13 01:44:12, Error                 CSI    000006e5 (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #12871338# from PrimitiveInstaller::CCoordinator::ProcessChange(Change 10.0.19041.1466 -> 10.0.19041.1645 for Microsoft-Windows-Installer-Engine, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35})[gle=0xd0150025]
2022-04-13 01:44:12, Info                  CSI    000006e6 SMI Primitive Installer [done]

2022-04-13 01:44:12, Error                 CSI    000006e7 (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #9017754# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150025]
2022-04-13 01:44:12, Error                 CSI    000006e8 (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #9017753# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150025]
2022-04-13 01:44:12, Error                 CSI    000006e9 (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #9017752# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150025]
2022-04-13 01:44:12, Error                 CSI    000006ea (F) STATUS_SMI_PRIMITIVE_INSTALLER_FAILED #9017751# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150025]
2022-04-13 01:44:12, Error                 CSI    000006eb (F) HRESULT_FROM_WIN32(14108) #8821267# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x8007371c]
2022-04-13 01:44:12, Error                 CSI    000006ec (F) HRESULT_FROM_WIN32(14108) #8739531# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47, pSink = NULL, disp = 0)[gle=0x8007371c]
2022-04-13 01:44:12, Error                 CSI    000006ed (F) HRESULT_FROM_WIN32(14108) #8739530# 40071080 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)

I've never actually seen this error before but it seems that a temporary subkey is missing from HKEY_LOCAL_MACHINE. Could you please open a command prompt window and then enter the following command:

Code: 
reg query HKEY_LOCAL_MACHINE

Please post the output in your next post. Afterwards, please gather a ProcMon trace using the following instructions:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
Nevermind, could you please check the following directory:

Rich (BB code): 
%systemroot%\System32\SMI\Store\Machine\SCHEMA.dat

I've also managed to get the Schema to load on my virtual machine so we can try and load it manually if needs be. Although, I suspect that the Schema.dat is missing from your system, hence why it isn't able to load during an update.
 
Hi,
info you requested:
C:\WINDOWS\system32>reg query HKEY_LOCAL_MACHINE

HKEY_LOCAL_MACHINE\BCD00000000
HKEY_LOCAL_MACHINE\DRIVERS
HKEY_LOCAL_MACHINE\HARDWARE
HKEY_LOCAL_MACHINE\SAM
HKEY_LOCAL_MACHINE\SECURITY
HKEY_LOCAL_MACHINE\SOFTWARE
HKEY_LOCAL_MACHINE\SYSTEM

C:\WINDOWS\system32>C:\Windows\System32\SMI\Store\Machine>dir
Volume in drive C is Acer
Volume Serial Number is 90C7-4C89

Directory of C:\Windows\System32\SMI\Store\Machine

13/01/2022 10:24 <DIR> .
13/01/2022 10:24 <DIR> ..
12/01/2022 20:36 12.582.912 SCHEMA.DAT
1 File(s) 12.582.912 bytes
2 Dir(s) 95.609.946.112 bytes free

C:\Windows\System32\SMI\Store\Machine>

I tried the update (from the update catalog) but procmon64.exe hung after a while (the update is a big one)

You want me to upload cbs log file and/or schema.dat ?
 
Hi
here wetransfer link files
contains
-cbs log files folder
-schema.dat file
-2 log files procmon (1st one = after starting updates- second one: at end of updates)

Hope this helps
Thanks in advance
Kind Regards
 
Thanks, it looks like your SCHEMA.dat file is corrupt. Could you please create backup of your current SCHEMA.dat file and then replace it using the attached version? If it has been successfully been replaced then please run the following command from an elevated command prompt:

Code: 
reg load HKLM\Schema %systemroot%\System32\SMI\Store\Machine\SCHEMA.dat
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top