[SOLVED] Win Server 2012 R2 Windows Update / Component Store Corruption

Here is the log. Attempting the KB install now. I'll let you know when it completes.
 

Attachments

The KB install completed successfully and asked for a restart. I'll try a dism restorehealth again.
 
The KB install completed successfully and asked for a restart. I'll try a dism restorehealth again.
That's good! Let me see the cbs.log after the restorehealth, if there are any problems.
 
Getting closer! But not yet...

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


CBS is here.
 
Based on your previous instructions, it looked to me like it was missing KB3185319, which I attempted to install with DISM, and it appeared to succeed. Then I ran another restorehealth, and it failed again. It seems to still be looking for the same package, but you're the expert. Attached is the latest CBS.

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 0x80240021

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Hello adamjw,

Thanks for the progress report. The log files are more complete now and reveal the full list of corrupt files. I can see why you wanted to try KB3185319 but there are other things that need doing. I will look into it when I get time, probably not today though.

In the meantime it would help if you could provide your current Components hive - the last one you sent will have changed considerably with the repairs now done. Here are the instructions again:

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.
 
Thanks again for all your help. I really appreciate it. Here is the Components hive. Obviously I'm eager to get it solved but if you can't get to it right away I understand. Thanks again.
 
You are welcome! It's a holiday weekend in the UK so that is why I am not so active on the forum.
 
OK, so I've looked at the latest errors and provide the following to correct them.

Step 1:
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. If needed, download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file 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. Attach this file into your next post for me to check please.

Step 2:
After this has completed you can run SFC /scannow and then follow this with another DISM restorehealth as you did before to see what remaining files still need to be repaired.
 

Attachments

It still failed but the number of corruptions and the size of the CBS log seem to be way down.

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Hello adamjw :-) ,

There are just three corruptions left according to the latest log. Please try and run the SFCFix.exe tool on its own - I am interested to see if it will automatically fix these corruptions. Let me know the result.
 
Doesn't appear that it will fix them on its own:

Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

SUMMARY:
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0

Press any key to continue to explanation of summary . . .

Successfully processed all directives.
Failed to prepare and open final logfiles.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-09-01 02:29:20.347
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.




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




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 331 datablocks.
Finish time: 2021-09-01 02:30:19.988
----------------------EOF-----------------------
 
I will need to check through the current state of the Registry Hives for your system.

Step#1 - Export CBS hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.

Step#2 - Export SideBySide
  1. Click on the Start button and type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
  7. Once done please upload this file via Dropbox or OneDrive or SendSpace.

Step#3 - Export 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.
 
Thank you! The three missing payload files are:
Code:
(p)    CSI Payload Corrupt            wow64_microsoft-windows-tabletpc-inputpanel_31bf3856ad364e35_6.3.9600.18108_none_0cfc6f4f7f95d455\TabTip32.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17705_none_43e54923a795541c\Amd64\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17705_none_43e54923a795541c\prnms003.cat
Repair failed: Missing replacement payload.

The following search will reveal all the versions present on your system:

  1. If needed, download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this log into your next post for me to check the results.
 

Attachments

Hello adamjw :-)

Please do the following to repair these corruptions:
Step 1:
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. If needed, download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file 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. Attach this file into your next post for me to check please.

Step 2:
After this has completed you can run SFC /scannow and post a new CBS.log
 

Attachments

Please apply the fix below to sort out more errors

  1. If needed, download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this log into your next post for me to check the results.
After this has completed you can run SFC /scannow and post a new CBS.log
 

Attachments

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

Back
Top