Windows 10: sfc /scannow Finds & Repairs after Storage Sense Temp Clean

Saw this on both my platforms today after running <Settings><Storage><Temporary files><Remove Files>
with just the default boxes checked.

There was about 2.5G of Updates that it found this time after this .267 Update

Code: Microsoft Windows [Version 10.0.18362.267] (c) 2019 Microsoft Corporation. All rights reserved. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. ************************************************************************************************ ********** Storage Sense Cleaned Default Checked Temporary Files Here ************ ************************************************************************************************ C:\Windows\system32>sfc /scannow 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. C:\Windows\system32>[/quote]
This is the first time I've seen anything significant to clean in Storage Sense since this Hash Corruption issue earlier in the month.

sfc /scannow failing after this latest Defender Platfom update.

I've never seen this behavior before with sfc /scannow finding and repairing corruption after an update that was subsequently cleaned by Storage Sense.

What it repaired is a mystery.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log finds only a page of these:

Code: 2019-07-26 17:40:01, Info CSI 00000008 [SR] Verifying 100 components 2019-07-26 17:40:01, Info CSI 00000009 [SR] Beginning Verify and Repair transaction 2019-07-26 17:40:02, Info CSI 0000000a [SR] Verify complete[/quote] However the CBS.log at the very beginning of this sfc /scanow that finds and repairs AFTER the clean does start out with this:

Code: 2019-07-28 08:32:14, Info CBS TiWorker: Client requests SFP repair object.[/quote]
Scans after this come back clean with "Windows Resource Protection did not find any integrity violations."



:)

 

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??

 

Cannot run sfc /scannow to completion despite being in safe mode and the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp

Following this guide https://support.microsoft.com/en-us...er-tool-to-repair-missing-or-corrupted-system I start Command Prompt as administrator.





I run this successfully

However on running

It fails at 68% complaining about

The original guide suggests trying in safe mode, which I have to no avail. 
I note that the PendingDeletes and PendingRenames folders exist
under %WinDir%\WinSxS\Temp do exist as the guide further suggests. 
The folders have many files in them.

I am on Windows 10.

I have also tried the steps in: How to Fix: 'sfc /scannow' Fails, Won't Complete my sfcdetails.txt file does not have any errors in it and after doing most of the steps I am have been recommended to try using a windows repair dvd, getting the files from a known good source or running a repair install (if I manage to try this and it also doesn't work I'll update this post)

 

sfc /scannow "Windows Resource Protection could not start the repair service"

Hi,

Windows Resource Protection could not start the repair service is an error which may occur if you are trying to run the System File Checker tool (SFC /SCANNOW) to scan and repair Windows system files. To resolve this error, we suggest that you follow the
steps below:

• Press the Windows + R keys to open run command box.
• In the run command box, type services.msc, and press
  Enter.
• In the list of services, double click the Windows Modules Installer service.
• Set the startup type to Auto, and click OK.
• Restart your computer.
• After the restart, you'll be able to run the sfc /scannow command without any problems.

We would appreciate it if you could get back to us and provide us your feedback.