Window Server 2012 R2 Version 6.3 (Build 9600) Unable to run DISM, SFC, and SFCFix. (Component Store Corrupt)

jmjoyner

Member
Joined
Feb 8, 2021
Posts
12
Good Morning, I have been trying to repair a server running windows 2012R2. When I run windows updates it is trying to install a server stack update from 2019. I have tried to manually install new updates and I keep getting "Not Applicable". So I tried to run DISM and it comes back with "The component store has been corrupted". Then I try SFC and I get "Windows resource protection could not preform the required operation". So I also tried the SFCFix and after the DISM fails it just hangs. I would like to fix this issue without having to rebuild the server. This server is running all our VDIs. What could I do to resolve this issue? I have attached links to the CBS and DISM logs. Thank you for your time and help on this.

Link for CBS log
CBS.log (12.04MB) - SendSpace.com

link for DISM log
dism.log (20.79MB) - SendSpace.com
 
Hi

Apologies for the delay. Please do the following.


Step#1 - SFCFix Script

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 SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put </> tags around the log to break up the text.

Step#2 - DISM /RestoreHealth Scan
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. Right-click on the Start 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. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 

Attachments

Good Morning Bruce1270,

I am just happy to have some help. Thank you for your time on this. I have attached the logs you requested. I was going to copy the components file from an identical server to this one. I just started this job 2 weeks ago so I finding all these little issues.
 

Attachments

Hi

Please do the following

Step#1 - SFCFix Script


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 SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put </> tags around the log to break up the text.

Step#2 - DISM /RestoreHealth Scan
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. Right-click on the Start 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. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 

Attachments

Good Morning Bruce1270,

I have attached the files you requested. I was unable to upload the CBS file so I used SendSpace. The link is listed below. I tried to copy the component file from another server but I had no luck. Thank you for your help.

cbs.txt (11.32MB) - SendSpace.com
 

Attachments

Hi

Please do the following.

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 magnifying glass on the toolbar as shown below.

i3yiUac.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 SendSpace.
 
Good Morning Bruce1270,

I have attached the logs you requested. I had to use sendspace for the Logfile.PML. So I found out a little more about this server. The server crashed about a year ago and they tried to recover it. Ever since they tried to restore the server it has had update issues. The server will pull office update but OS updates. Thank you for your help.

Logfile.PML (176.06MB) - SendSpace.com
 

Attachments

Hi

Please do the following

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Hi

Unfortunately, I am the bearer of bad news.. the COMPONENTS hive is completely corrupt beyond any repair and it will have to be a re install I'm afraid. :(

The hive is only 256KB in size and is missing the branches and keys required for windows update to perform and which I am unable to repair.

I'm sorry I can't be of any more help.
 
Hello,

Thank you so much for your help. What would be the best way of fixing the issue without data loss?
 
Hi

Due to the state of the COMPONENTS hive the only way I am aware of is a full clean installation. It might be worth posting in our windows forum here to see if any of the software experts may know of a solution for you.

When posting please reference this thread so they know what has happened so far.

Again, sorry I can't be of more help.
 
Hi

I would strongly advise against this. The components hive is inextricably linked to the file system for the components store and controls the installs and versions of various windows updates.Even if the server and operating system appear identical there are likely to be subtle differences. Copying an entire components hive introduces too many unknown factors which may lead to system unstabilty and windows update not working as it should and your system could be at risk if not patched and updated.

As I mentioned, the only way I am aware to get round this is a fresh install.
 

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

Back
Top