rvtkruys
New member
Step #1: Performed at 09:29 - Windows Resource Protection could not start the repair service.
Step #2: Performed at 09:31 - No issues
Step #3: Performed at 09:50 - Completed and uploaded @ 10:04
Step #4: Compressed file of CBS prepared
We are running a SQL Server on a virtual Windows Server 2019 Standard, within the Hyper-V cluster. We have noticed that the server didn't receive any Microsoft Updates, after the successful update of KB5005112.
A week ago, we have attempted to run a standard update to download KB5036896 and the latest Service Stack Update. But this failed every time.
To recover from this issue, we have performed the following steps and commands:
At first with DISM, we could see more than 5000 instances being corrupt, but now we do not see this anymore. Also, with DISM today, we do not see that the Component Store is corrupt.
Step #2: Performed at 09:31 - No issues
Step #3: Performed at 09:50 - Completed and uploaded @ 10:04
Step #4: Compressed file of CBS prepared
We are running a SQL Server on a virtual Windows Server 2019 Standard, within the Hyper-V cluster. We have noticed that the server didn't receive any Microsoft Updates, after the successful update of KB5005112.
A week ago, we have attempted to run a standard update to download KB5036896 and the latest Service Stack Update. But this failed every time.
To recover from this issue, we have performed the following steps and commands:
- Resetting Windows Update (even ran the Troubleshooter) > issue remains
- SFC /SCANNOW > issue remains
- DISM commands > issue remains
Code:
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:E:\Sources\install.wim:2 /LimitAccess
Dism /image:C: /Cleanup-Image /RevertPendingActions
Dism /Online /Cleanup-Image /AnalyzeComponentStore
Dism /Online /Cleanup-Image /StartComponentCleanupAt first with DISM, we could see more than 5000 instances being corrupt, but now we do not see this anymore. Also, with DISM today, we do not see that the Component Store is corrupt.