Windows 10: sfc /scannow without /offline found and repaired corruption on WinRE X:\

As part of trying to solve random blue screens of death that I’ve been having lately on my Windows 11, I rebooted into Recovery Environment → Troubleshoot → Advanced options → Command Prompt and foolishly ransfc /scannowwithout the /offline… parameters.To my shock, not only did it run happily, but it even found and repaired a whole bunch of supposedly corrupted files on X:\ the WinRE partition, not my system partition, which was mounted at C:\.What are the implications of this? How worried should I be?

:)

 

sfc /scannow error repair

Hi,



Thank you for writing to Microsoft Community Forums.



We appreciate the efforts you have taken in trying to resolve this issue. I have analyzed the error logs that you have shared and I would suggest you follow the steps mentioned below:

1. Type Command Prompt in the
   search bar on the Taskbar.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, paste the following command and hit Enter:
   DISM.exe /Online /Cleanup-image /Restorehealth
   
4. Once the DISM command is executed, we would suggest you to run sfc /scannow again.
   

If the integrity violations are not repaired after running sfc scan, the best option will be performing a repair installation. A repair installation will repair all the corrupted files.



Refer the steps mentioned below:



Download the Windows 10 Media Creation Tool (MCT) and use it to perform a repair installation
of Windows 10. We have a video that can show you how if you aren’t sure



Let us know the results.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

SFC scannow not working but verify only is working

there is no problem in chkdsk I've checked When I select command prompt and sfc scannow from f8 and repair.. it shows that a reboot is required for pending repair and pending renames folder in winsxs is full of files.. what should I do??

 

sfc /scannow error

That's why Im asking the question. Am I correct in thinking that its perfectly normal that after the second running of sfc /scannow in your list you would get :-

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired 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.

Then after that..its the third sfc /scannow that you list that comes up clean .
Ivghandi was saying that he presumed that the second sfc /scannow you list showing "Windows Resource Protection found corrupt files and successfully repaired them" meant that he still had a problem.

The way I understand that DISM works is that it repairs the Component Store. Then when you run SFC /scannow again it can then repair the file corruptions it detected originally. Have I got that correct?