Windows 10: Sfc showing integrity violations when system has no issues - False reporting?

This seems to happen after windows updates/driver updates or when I install a number of programs. I do the standard procedure for everything and have not done anything unsafe to corrupt my system files. Even on a freshly installed windows on a NVMe SSD it shows integrity violations, but is fixed after scanning.However, I found more integrity violations today when I ran sfc /verifyonly and my system seems to be just fine.Do I still need to do sfc /scannow to fix these violations anyways or can I ignore them because they're likely just cleaning up old drivers/leftovers in general?

:)

 

10240 sfc finds integrity violations and cannot fix


I just restored 10166 from backup, verified it has no sfc integrity violations, ran the 10240 update again and sfc gives integrity violations. Also my machine hung coming out of sleep this morning. Sig, hope this isn't the final - 10166 was more stable for me.

 

Running sfc /scannow more than once question

I've run across the suggestion that when running sfc /scannow it should be run two or three times, even if you received the message Windows Resource Protection did not find any integrity violations. My understanding has been that if no integrity violation are found you shouldn't need to run further scans. True of false?

 

Disconnecting external monitor : preview refresh issue and full size border

Hi Pawan

Thanks for your suggestions. I ran

• sfc /verifyonly : no integrity violation found
• Dism /Online /Cleanup-Image /ScanHealth : no damage detected

So my system's clean.

Do you have another suggestion ? Or can you elevate the issue to next level support ?

Regards

Thomas