[SOLVED] w2022 sfc/dism error "0 of 2 instances of system store corruption have been repaired"

[StefanoZ]

Hi there

w2022 server, we're having some issues

after a sfc /scannow I found the vm has errors
sfc and dism aren't able to solve the corruption

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

in attach the requested files

TIA for your support, I donated 20 buck to thank and support you

 

[Windows Update Bot]

Hi @StefanoZ,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Maxstar]

Hi,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[StefanoZ]

hi there..
thank you for your post, everything is ok now, no more corruption.

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved, and also thanks for your donation to Sysnative as mentioned in your first post...