[SOLVED] Components hive corrupt

[08cookie]

Hello,

I'm having a similar issue to this - [SOLVED] - Components Hive may be corrupt

I've uploaded a copy of components.zip here:
COMPONENTS.zip (17.92MB) - SendSpace.com

And the CBS.log file here after running sfc /scannow
CBS.log (5.33KB) - SendSpace.com

This is blocking Windows updates. I have tried DISM with multiple different parameters without success (including repair from install.wim).

I copied COMPONENTS from another similar Windows Server 2019 install which allows sfc /scannow to run but both DISM and Windows Updates still continue to fail.

Any help would be greatly appreciated

 

[Gary R]

Warning: this fix is specific to the user in this thread, and no one else should follow these instructions.

• Download COMPONENTS.ZIP and save to your Desktop.
• Right-click on it and select Extract all....
  • Make sure the Show extracted files when complete is checked and click Extract.
  • You should now have the COMPONENTS file that we will be using to replace your current one.

Next ...

• Navigate to C:\Windows\System32\config
• Right-click on the current COMPONENTS file and select Rename.
  • Rename it to COMPONENTS.old
  • Note .... If you get an error that the file is in use, reboot your computer and then try again.
• Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

Next ....

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[08cookie]

The Dism command worked this time (usually failed at 5%).

Attached it the latest CBS.log file.

Thank you for your assistance @Gary R !

 

[Gary R]

Nothing being flagged in your latest CBS.log, so please try updating again.

If successful please let me know.

If not, please post the CBS.log created after your update attempt.

 

[08cookie]

@Gary R Amazing, updates working perfectly!

20+ years in the industry and I've never had this issue. Can you divulge how you went about fixing it? I'm deeply interested :)

Thank you so much

 

[Gary R]

Glad to hear you're now able to update.

So basically your COMPONENTS hive file got corrupted, so that a couple of sequence numbers in the file header didn't match. Because of that the hive wouldn't load, so what I did is run your COMPONENTS hive file through a tool we have, that re-writes the two sequence numbers so they match, and then updates the file's checksum, so that your COMPONENTS hive would load.