asked on How do you repair the component store of Windows Server 2012 Standard?
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?
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?
* Switch* Deployment Image Servicing and Management (DISM)Windows Server 2012* SFC
Last Comment
Davester44
ASKER
It didn't work. When I ran
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\ins
it came up with "DISM failed. No operation was performed"
I then tried
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\ins
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
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\ins
it came up with "DISM failed. No operation was performed"
I then tried
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\ins
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
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
My solution resolved the issue.
Try by running Dism with Source Windows DVD
Command (Assuming D drive is Cd Drive)
Open in new window
If it fails, Try
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.lo
C:\Windows\Logs\DISM\dism.