[SOLVED] [Server2012R2] DISM Corrupt + Failed to load COMPONENTS hive

R

reallywildstuff

Contributor
Joined
Nov 8, 2017
Posts
4
W2012R2 Server (Cluster Node) won't load Windows Updates.

dism /online /cleanup-image /scanhealth =
Error:1009 The Configuration registry database is corrupt

sfc /scannow =
Windows Resource Protection could not perform the requested operation.

c:\windows\system32\config\COMPONENTS is dated 4.13.2016 (all other hives dated today) and is 64,000 KB (exactly)

CBS.log attached
 

Attachments

Re: WS2012R2 DISM Corrupt + Failed to load COMPONENTS hive

Step 1 - Replace Components Hive Manually

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download COMPONENTS.ZIP here:Download COMPONENTS.zip from Sendspace.com - send big files the easy way and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

Step 2 - DISM /RestoreHealth Scan

  1. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log
 
Re: WS2012R2 DISM Corrupt + Failed to load COMPONENTS hive

C:\Windows\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
repaired.
The operation completed successfully.
 

Attachments

Re: WS2012R2 DISM Corrupt + Failed to load COMPONENTS hive

Code: 
2017-11-13 14:49:11, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30629056_3691068351
2017-11-13 14:49:11, Info                  CBS    Reboot mark set
2017-11-13 14:49:11, Info                  CBS    Winlogon: Registering for CreateSession notifications
2017-11-13 14:49:21, Info                  CBS    Repr: CBS Store check completes
2017-11-13 14:49:21, Info                  CSI    00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x322113f760
2017-11-13 14:49:21, Info                  CSI    00000003 Creating NT transaction (seq 1), objectname [6]"(null)"
2017-11-13 14:49:21, Info                  CSI    00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x3b8
2017-11-13 14:49:21, Info                  CSI    00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2017-11-13 14:49:21, Info                  CSI    00000006@2017/11/13:20:49:21.826 Beginning NT transaction commit...
2017-11-13 14:49:21, Info                  CSI    00000007@2017/11/13:20:49:21.826 CSI perf trace:
CSIPERF:TXCOMMIT;470
2017-11-13 14:49:21, Info                  CSI    00000008 CSI Store 215287348224 (0x0000003220203c00) initialized
2017-11-13 14:49:21, Info                  CSI    00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17709 (winblue_r9.150219-1500)".
2017-11-13 14:49:21, Info                  CSI    0000000a@2017/11/13:20:49:21.842 Starting corruption detection (InnerFlags=5)
2017-11-13 14:56:24, Info                  CSI    0000000b@2017/11/13:20:56:24.940 Corruption detection complete. numCorruptions = 0, Disp = 1.
2017-11-13 14:56:24, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2017-11-13 14:56:24, Info                  CBS    Repr: CSI Store check completes
2017-11-13 14:56:24, Info                  CBS    Exec:Only CSI metadata corruption found, Process CSI repair.
2017-11-13 14:56:24, Info                  CSI    0000000c Creating NT transaction (seq 2), objectname [6]"(null)"
2017-11-13 14:56:24, Info                  CSI    0000000d Created NT transaction (seq 2) result 0x00000000, handle @0x368
2017-11-13 14:56:25, Info                  CSI    0000000e@2017/11/13:20:56:25.081 Beginning NT transaction commit...
2017-11-13 14:56:25, Info                  CSI    0000000f@2017/11/13:20:56:25.143 CSI perf trace:
CSIPERF:TXCOMMIT;85538
2017-11-13 14:56:25, Info                  CSI    00000010 StoreCorruptionRepair transaction completed.
2017-11-13 14:56:25, Info                  CBS    Repr: Finished repairing CSI store.
2017-11-13 14:56:25, Info                  CBS    Ensure CBS corruption flag is clear
2017-11-13 14:56:25, Info                  CBS    Ensure WCP corruption flag is clear
2017-11-13 14:56:25, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 433 seconds.

2017-11-13 14:56:25, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2017-11-13 14:56:25, Info                  CBS    Count of times corruption detected: 0
2017-11-13 14:56:25, Info                  CBS    Seconds between initial corruption detections: -1
2017-11-13 14:56:25, Info                  CBS    Seconds between corruption and repair: -1

Looks good :thumbsup2:

Go ahead and check for Windows Updates
 
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