Server 2016 DISM corrupt & SFCFix never finishes

SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...
  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Download the file SFCScript.txt, attached below, and save this to your Desktop
  • On your Desktop, make sure you have the two files:
    myjIXnC.png
    SFCFix.exe and
    8RAhYFg.gif
    SFCScript.txt
  • Drag the file SFCScript.txt onto the file SFCFix.exe and release it
  • The SFCFix tool will process the script
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Open the SFCFix.txt log and copy & paste the contents to your post
 

Attachments

SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...
  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Download the file SFCScript.txt, attached below, and save this to your Desktop
  • On your Desktop, make sure you have the two files:
    myjIXnC.png
    SFCFix.exe and
    8RAhYFg.gif
    SFCScript.txt
  • Drag the file SFCScript.txt onto the file SFCFix.exe and release it
  • The SFCFix tool will process the script
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Open the SFCFix.txt log and copy & paste the contents to your post
After the fix run dism and attch the log please.
 

Attachments

I'm trying to find a way to fix this faster because the log show this "Regeneration Candidates: 2429"

Its seems that 2419 keys need adjustments!

Please upload a fresh copy of the components file and move the file from the c:\Windows\System32\config folder to prevent Windows from doing changes.

I will work on the file on my side and will send you the modified file to put in place.
 
okay but one wrinkle: Windows forced an update. Will that affect things or just reboot then do what you asked?
 
Reboot to make sure the update installs and the Components file is not locked.
 
Replace Components Hive Manually

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...
  1. Download COMPONENTS2.ZIP and save it to the 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 you 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

Run dism and post the CBS.log lets see what happens.
 
Hi,

What was the result of Dism?

Please run Dism /Online /Cleanup-Image /RestoreHealth and attach the CBS.log
 
The dism result in the prior post failed with an error that it couldn't find the file specified (dism /online /cleanup-image /startcomponentcleanup /resetbase). /restorehealth completes successfully. /startcomponentcleanup without /resetbase completes successfully (though it's a little odd because it goes to 20% not 100% before saying it completed successfully). Tried /resetbase again and it says it completed successfully though, again, it finishes at 20% not 100% so I'm not sure if it did or not. Log link:

CBS (1).log
 
Repeat the dism /online /cleanup-image /startcomponentcleanup and post the CBS.log
 
Now the log doesn't show the problem...

Capture Process Monitor Trace

  • Download Process Monitor and save it to the Desktop
  • Open an elevated Command Prompt
  • Run Process Monitor from the Desktop. Leave this running while you perform the next steps
  • Return to the Command Prompt and run dism /online /cleanup-image /startcomponentcleanupjust like you have in the past
  • Stop Process Monitor as soon as dism fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
    iiTxmntz9hzmYzZrKwGk9tmnhW5kF0.png
  • 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.
  • Zip up and attach the LogFile.PML file as well as your CBS.log.

Note: To produce a smaller log is recommended to close all other programs that are not needed before starting the trace.
 
Please repeat the dism /online /cleanup-image /startcomponentcleanup with procmon active to see if it fails.
 
ETA: this time it says it completed successfully. Should I do the same thing but with resetbase?
 
It did the same thing as before - got to 20% then said it had completed successfully. I tried running a second time with procmon to see if it would get to 100% but no luck. Link is procmon and cbs log:
CBS.zip
 
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