sfc /scannow error

Kyhi said:

Wait til next update before considering corrupt

That's the part I found discouraging. I had gotten this corruption in the morning before .239 and specifically waited for the update hoping it would clear it up, but it didn't.

So I guess when in doubt, wait another cycle?

Ivghandi wrote in an earlier post:

I did all in first part.
Results are as below
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 3.69 GB

Actual Size of Component Store : 3.62 GB

Shared with Windows : 2.95 GB
Backups and Disabled Features : 673.41 MB
Cache and Temporary Data : 0 bytes

Date of Last Cleanup : 2019-07-10 11:40:09

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.
PS C:\WINDOWS\system32>

===========
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[=========== 20.0% ]
The operation completed successfully.
PS C:\WINDOWS\system32>

==========================
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
==============
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32>
==========
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>

But still I am in problem as follows.
PS 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.

Bastet said:

Then the next step (unless another member has a different solution) would be the repair install.

Isnt that exactly what you would expect to see after a successful restorehealth DISM repair? The next time you run sfc /scannow it just repairs the corrupted files?
Isn't the last SFC /scannow where it says "Windows Resource Protection found corrupt files and successfully repaired them" just informing you that the SFC has repaired the corrupted files after the successful DISM repair? I don't think its saying that there is still a problem

I got it fixed by running:

sfc /scannow
dism /online /cleanup-image /restorehealth
sfc /scannow
sfc /scannow -> This one should come up clean.

sportsfan148 said:

Ivghandi wrote in an earlier post:

I did all in first part.
Results are as below
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 3.69 GB

Actual Size of Component Store : 3.62 GB

Shared with Windows : 2.95 GB
Backups and Disabled Features : 673.41 MB
Cache and Temporary Data : 0 bytes

Date of Last Cleanup : 2019-07-10 11:40:09

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.
PS C:\WINDOWS\system32>

===========
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[=========== 20.0% ]
The operation completed successfully.
PS C:\WINDOWS\system32>

==========================
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
==============
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32>
==========
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>

But still I am in problem as follows.
PS 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.

Isnt that exactly what you would expect to see after a successful restorehealth DISM repair? The next time you run sfc /scannow it just repairs the corrupted files?
Isn't the last SFC /scannow where it says "Windows Resource Protection found corrupt files and successfully repaired them" just informing you that the SFC has repaired the corrupted files after the successful DISM repair? I don't think its saying that there is still a problem

If you read the last part of the post the it does say there was still a problem with sfc even though it says it completed successfully.
You usually do not see the instructions on running an online repair if the cmd worked so I assumed the successful was a mis-type 😀

eLPuSHeR said:

I got it fixed by running:

sfc /scannow
dism /online /cleanup-image /restorehealth
sfc /scannow
sfc /scannow -> This one should come up clean.

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?

Should everyone do this because of a bad Defender update of the past days? Did Defender corrupt system files? If so why is thisnt a pinned important post. Will MS push an update which does an auto scan maybe with next reboot?

I am pretty sure you can live with it. MS might fix it in some incoming update though. I prefer to leave things in a tidy manner before making a Macrium Reflect backup copy. I make one every cummulative update.

I did

sfc /scannow
dism /online /cleanup-image /restorehealth
sfc /scannow
sfc /scannow (why the 2nd times in a row?)

and the 2nd time it didnt find anything anymore, weird, the first one though did.

gorgor said:

I did
sfc /scannow
dism /online /cleanup-image /restorehealth
sfc /scannow
sfc /scannow (why the 2nd times in a row?)
and the 2nd time it didnt find anything anymore, weird, the first one though did.

thanks for this, just did same and yes, odd that second (third) sfc is clean. but thanks!

gorgor said:

I did

sfc /scannow
dism /online /cleanup-image /restorehealth
sfc /scannow
sfc /scannow (why the 2nd times in a row?)

and the 2nd time it didnt find anything anymore, weird, the first one though did.

That's just for confirming everything is okay.