Sfc detected damaged files during the latest Windows 10 setup.
Sfc detected damaged files during the latest Windows 10 setup.
I’m experiencing issues with Windows 10. Each time I install a fresh copy on a USB drive, the SFC scan detects corrupted files. After performing the SFC repair, the integrity violations disappear. I ran DISM /Online /Cleanup-Image /RestoreHealth and then reran the SFC scan, but it still finds no corrupted files. I’m puzzled as to why this keeps happening during fresh installs. I haven’t encountered these problems with Windows 10 for years; they only occur on Windows 10, not 11. I haven’t overclocked anything except my RAM. I’ve tried testing the RAM, using a different USB drive, and even using another PC with the creation media tool. Still nothing worked. Is it safe to skip addressing these issues?
I frequently encounter this during Windows 10 installations. Simply execute sfc scannow twice. Should the second scan reveal no issues, disregard the results.
I also tried running sfc twice, but it didn’t locate anything. After a while, I ran it again and it stopped showing any corrupted files.
It's still a good idea to test your RAM with Passmark Memtest86 and monitor your hard drive health using Hard Disk Sentinel.
Reviewing the Windows\logs\CBS\CBS.log provides details about any file repairs, including issues detected by SFC such as duplicate permissions. These errors usually don’t hinder Windows operation and are often linked to updates.
I ran the memory test on a hard drive and it completed successfully. Next, I plan to test with a hard disk sentinel.
It seems like you're confirming it's a duplicate. I'll review it again upon returning.