How do you repair the component store of Windows Server 2012 Standard?

Davester44
Davester44 used Ask the Experts™
on
I tried to do a SFC /scannow on our company's terminal server which is on a virtual machine in Hyper-V.  I got the message back that it found integrity violations, but was unable to fix them.  I ran DISM /Online /Cleanup-Image /RestoreHealth to repair the WinSxS folder, but then got DISM failed.  No operation has been performed.  So I ran Dism /Online /Cleanup-Image /StartComponentCleanup - which I believe tried to compress the folder.  That completed successfully.  Then ran DISM /Online /Cleanup-Image /RestoreHealth -  I got the same message - DISM failed.  No operation has been performed.  I rebooted the server and tried the same thing - same message. It hung at 20% for a while, then at 40%.  I'm I missing a switch with the DISM command to properly fix the WinSxS folder?  My server is online and everyone is out of it, except me.

On our file server, I ran Dism /Online /Cleanup-Image /ScanHealth , just to see if the WinSxS folder is okay, it is. Got the message "No component store corruption detected.  The operation completed successfully."  The terminal server and file server are the same OS - Windows Server 2012 Standard (not R2).  Their Windows Updates history are pretty close (I believe -I'm not sure if that makes a difference)  Can I rename the corrupt WinSxS folder on the terminal server to WinSxS.old, then copy the good WinSxS folder from the file server to WinSxS?  Then would the SFC /Scannow run successfully?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Elango SathyadevSenior Systems Engineer

Commented:
Don't Rename the WinSxS folder.

Try by running Dism with Source Windows DVD

Command (Assuming D drive is Cd Drive)

 Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1

Open in new window


If it fails, Try

 Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1  /limitaccess

Open in new window

This will also run by avoiding checking internet for updates and fix corruption without using windows updates.

If this fails can you post logs of the following files

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\DISM\dism.log

Author

Commented:
It didn't work.  When I ran
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1
it came up with "DISM failed.  No operation was performed"

I then tried
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1  /limitaccess
got "The source files could not be found"

Both scans took about 30 minutes.  I'm using an ISO, I'm not sure if that matters.  It's not the original installation ISO, as the previous IT company that installed the OS is gone.  This server is Windows Server 2012 Standard.  The ISO disk comes up as Windows Server 2012  (no standard).  I'm not sure if that makes a difference.
CBS.log
dism.log
I fixed it. Not with the ISO though.  Our file server had a good component store, as I verified with Dism /online /cleanup-image /CheckHealth on that server.  I mapped the file server's winsxs folder to T: on the terminal server.  Then I ran the command:
Dism /online /cleanup-image /restorehealth /source:T:

After that SFC /scannow completed successfully.

Author

Commented:
My solution resolved the issue.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial