Windows 10: sfc /scannow found corrupt files after fresh win10 install

There is another discussion with this name but its locked. The first thing an answer states is that if partitions etc are not deleted and formatted then its not a fresh install, yet I have done that, and I have this issue....

:)

 

sfc /scannow found corrupt files after fresh win10 install

I had the exact same problem in each of my Windows 10 fresh installations, whether it was 1809, 1903. Every time after a fresh installation SFC /Scannow found corruptions, but it managed to repair the corruptions on all of these cases. And after that there were no longer any integrity violations.

This is weird because when I previously had Windows 8.1 never did SFC /Scannow find any corruptions. In fact even when I had problems with Windows 8.1 after 4 years, SFC failed to find integrity violation.

Sometimes when you have real problems SFC reports as no integrity violation, next time you feel you don't have any problems and this system reports that it has problems, lol.

 

20H2 system files corrupted on a clean Windows installation sfc /scannow

Hi,

I have noticed that sfc /scannow corrected system files. I wonder. So I tested again on a clean Windows 10 20H2 installation and run directly after sfc /scannow.

Preparation for testing:

• I used VMware Workstation 16.0.0
• I created a new virtual machine with default Windows 10 profile
• I disabled the Network Adapter, the OS has
  no internet the whole process
• I used the latest official Windows 10 ISO file Win10_20H2_English_x64.iso (md5: e80f6ce987b2bba288469e7379129e12) Build 19042.508
  
• Mounted the ISO in VMware

Installation:

• So I started to install Windows 10
• Install Now, No product key, Windows 10 Home, Language en-us, install on the unformatted 60GB drive etc.
• After reboot, I used "no internet" for local Account, name: admin, no password, disabled all the telemetry trash

After successful start, I started directly cmd.exe with administrator privilegs and run sfc /scannow.

It will found corrupted systems files.





It didn't let me post the log here, so I made a Screenshot.

What is going on here?

I repeated the steps with de_windows_10_business_editions_version_20h2_x64_dvd_ce126f3b.iso (md5: 35df62707e53c2064641ccd5b91acb8d)

Type license: Enterprise

After repeating the steps above, the result is the same.

 

sfc/scannow corrupt file

sfc/scannow keeps finding corrupt files and fixing them