DISM Error 1009 COMPONENTS Corrupt - Server 2016

E

EarlGrei

Member
Joined
Aug 18, 2022
Posts
9
We recently switched backup vendors. They are unable to successfully backup VMs on this one node due to their PowerShell scripts failing. After much ado they had me run an SFC scan which shows "Windows Resource Protection could not perform the requested operation." Which lead to then DISM. It is throwing an Error 1009 at 4.5%


I've resolved a fair few SFC/DISM failures in my day. But I fear this one is beyond me. You folks fix this and I guarantee a donation and my gratitude for ever!


---SFCFix---
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-18 10:43:59.488
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Failed to check store directories with return code 1 and error code ERROR_FILE_NOT_FOUND. COMPONENTS hive may be corrupt.


WARNING: Components hive failed load test and may be corrupt.


WARNING: Components hive failed final reload test with error code ERROR_BADDB and may be corrupt.





SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to process registry database in location 1.
Failed to load registry hive C:\Windows\System32\config\COMPONENTS into key HKEY_LOCAL_MACHINE\COMPONENTS with error code ERROR_BADDB.

Failed to process registry database in location 2 with error code ERROR_FILE_NOT_FOUND.
WARNING: Failed to process registry database in location 3 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_INVALID_HANDLE.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.
Failed to process registry database in location 4 with error code ERROR_FILE_NOT_FOUND.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-08-18 10:50:40.272
----------------------EOF-----------------------
Click to expand...
 

Attachments

I should add that this host is one of three IDENTICAL hosts that really the only different between them is going to be some windows updates. So if whomever is kind enough to help we can explore pulling files from one of the other nodes if needed.
 
Could you please run the ComponentsScanner tool on your problematic hive? If it requests to make repairs then please allow it to do so. Once complete, please attach the log file it produces and then attempt to run DISM again.
 
I doesn't generate a log file at all.

Loading registry hive from C:\Windows\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Unable to find root key based on flag HiveEntryRootKey. Looking for root key via Header.RootCellOffset value...
Failed to parse hive. This could indicate major hive corruption (System.Collections.Generic.KeyNotFoundException)
Press any key to continue. . .
Click to expand...
 
It looks like a erroneous string has been repeatedly written to the beginning of your COMPONENTS hive.

Rich (BB code): 
2020-02-03 07:13:47.0542    Waiting for process to end...
2020-02-03 07:13:47.0129    Waiting for process to end...
2020-02-03 07:13:48.0632    Waiting for process to end...

I've just had a further look and the entire hive is corrupted. There is no salvageable data at all. Something has come along and totally written rubbish everywhere inside the hive file. There is only two options really:
  1. Perform a clean install
  2. Restore the COMPONENTS hive from an earlier backup, although, this isn't recommended since it can lead further problems
 
I have two IDENTICAL nodes in this cluster. Only difference would be updates. Is this a possible option to help?
 
So I grab a copy of the components file, move it over from Node C to Node A (problem child). Do I need to do a restart or just fire off the DISM right away?
 
AFTER COPYING COMPONENTS FROM NODE-C

sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


C:\Windows\system32>Dism /Online /Cleanup-Image /CheckHealth /english

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

The component store is repairable.
The operation completed successfully.

C:\Windows\system32> Dism /Online /Cleanup-Image /RestoreHealth /english

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.



C:\Windows\system32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 
Last edited:
How promising do you think this is going to be??

My next step here is a reboot and pray to god it boots.



Code: 
C:\Windows\system32> Dism /Online /Cleanup-Image /RestoreHealth /Source:\\ntnx-cluster-c\c$\Windows

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 
It seems that DISM managed to repair those missing files? The COMPONENTS hive isn't a boot critical hive so it shouldn't cause any problems.
 
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