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?