DISM RestoreHealth fails with component store corrupt (Server 2012 R2)

D

dcorrons

Member
Joined
Jul 30, 2018
Posts
7
I have a terminal server that has an issue with the Windows Search service not functioning properly. After basic troubleshooting with the indexer, I decided to reinstall the Windows Search feature. I could not find it listed as a feature in Server Manager so used DISM to disable it. When trying to re-enable it, received errors stating that one or several parent features are missing.

When I run CheckHealth the result is The component store is repairable.

When I run ScanHealth the result is Error 14098 The component store has been corrupted.

When I run RestoreHealth the result is the same.

When I run SFC /SCANNOW the result is Windows Resource Protection could nto peform the requested operation.

When I check the CBS log it says:

Checking System Update Readiness.


(w) CBS Package Index Package Missing 0x80070490 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~en-US~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Package Index Package Missing 0x80070490 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Package Index Package Missing 0x80070490 Microsoft-Windows-PowerShell-V2-ServerCore-Package~31bf3856ad364e35~amd64~en-US~0.0.0.0 Microsoft-Windows-PowerShell-V2-ServerCore-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-NetFx4-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-PowerShell-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-PowerShell-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-PowerShell-V2-Server-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-PowerShell-V2-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-V2-ServerCore-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 MicrosoftWindowsPowerShell Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 MicrosoftWindowsPowerShell-WOW64 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 MicrosoftWindowsPowerShellRoot Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 MicrosoftWindowsPowerShellV2 Microsoft-Windows-PowerShell-V2-ServerCore-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 NetFx4 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
(w) CBS Update Watchlist Package Missing 0x80070490 ServerCore-WOW64 Microsoft-Windows-PowerShell-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~6.3.9600.16384


Summary:
Operation: Detect and Repair
Operation result: 0x80073712
Last Successful Step: CBS store detection completes.
Total Detected Corruption: 19
CBS Manifest Corruption: 0
CBS Metadata Corruption: 19
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: False

Can anyone assist me with repairing this?
 
Pressed enter and it completed. Not sure if I interrupted it or not. Here is the log.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-07-30 14:37:57.709
Microsoft Windows Server 2012 R2 Update 3 - 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.










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








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-07-30 15:07:30.785
----------------------EOF-----------------------
 
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 and just provide the link here.
 
Thanks, do this as well:

Export Component Based Servicing


  1. Click on the Start button and in the search box, 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\Component Based Servicing\
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  7. Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.


Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace etc. and include the link with your reply.
 
Let's start with the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Run DISM again and attach CBS.log.
 

Attachments

Thank you so much from your help. This is a production server so I will need to do this tonight as it requires a reboot.
 
Just wanted to give you a bit of background on how I discovered this mess. The local indexing is not indexing all locations and seems to produce random results after rebuilding the index. So I decided to uninstall the Windows Search feature and reinstall it. But I then discovered that it is not in the feature list in Server Manager. After digging around, it seems like many of the features are not shown as an option. So I tried using Dism. I was able to uninstall it but when I tried to reinstall, it kept giving me errors. One or several parent features are missing (even though I was using the /all switch). I also noticed that the server is displaying a warning that PowerShell is not installed, but I have been using it this whole time to run all of the commands. So I figured the component store needs to be repaired but I wasn't able to do that either.

This is the fix log.

https://appriver3651011060-my.sharepoint.com/:t:/g/personal/dcorrons_wdigitech_com/EYoJKmuwiYlOshqIJOX8ZlkBwr3fcmTJ0vaEYhmDi7KZNg?e=zCTpgU

This is the CBS log after running Dism /Online /Cleanup-Image /RestoreHealth and it failing at 80% due to the remote call procedure failing.

https://appriver3651011060-my.share...9BpOVbsSXMKO8BIzG6YyV-eImnqH_ldRd7pQ?e=tSmWBh
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run DISM again just like you have in the past.
3. Stop Process Monitor as soon as DISM throws an error. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log
 
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