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

%3CLINGO-SUB%20id%3D%22lingo-sub-1823943%22%20slang%3D%22en-US%22%3E20H2%20system%20files%20corrupted%20on%20a%20clean%20Windows%20installation%20sfc%20%2Fscannow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1823943%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22%22%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20noticed%20that%20sfc%20%2Fscannow%20corrected%20system%20files.%20I%20wonder.%20So%20I%20tested%20again%20on%20a%20clean%20Windows%2010%2020H2%20installation%20and%20run%20directly%20after%20sfc%20%2Fscannow.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CU%3EPreparation%20for%20testing%20(using%20VMware%20is%20just%20an%20example%20for%20easy%20reproducing.%20You%20could%20also%20use%20a%20host%20system)%3A%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EI%20used%20VMware%20Workstation%2016.0.0%3C%2FLI%3E%3CLI%3EI%20created%20a%20new%20virtual%20machine%20with%20default%20Windows%2010%20profile%3C%2FLI%3E%3CLI%3EI%20%3CSTRONG%3E%3CSPAN%3Edisabled%3C%2FSPAN%3E%3C%2FSTRONG%3E%20the%20Network%20Adapter%2C%20the%20OS%20has%20%3CSPAN%3E%3CSTRONG%3Eno%20internet%3C%2FSTRONG%3E%3C%2FSPAN%3E%20the%20whole%20process%3C%2FLI%3E%3CLI%3EI%20used%20the%20latest%20official%20Windows%2010%20ISO%20file%20Win10_20H2_English_x64.iso%20(md5%3A%20e80f6ce987b2bba288469e7379129e12)%20Build%2019042.508%3C%2FLI%3E%3CLI%3EMounted%20the%20ISO%20in%20VMware%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CU%3EInstallation%3A%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ESo%20I%20started%20to%20install%20Windows%2010%3C%2FLI%3E%3CLI%3EInstall%20Now%2C%20No%20product%20key%2C%20Windows%2010%20Home%2C%20Language%20en-us%2C%20install%20on%20the%20unformatted%2060GB%20drive%20etc.%3C%2FLI%3E%3CLI%3EAfter%20reboot%2C%20I%20used%20%22no%20internet%22%20for%20local%20Account%2C%20name%3A%20admin%2C%20no%20password%2C%20disabled%20all%20the%20telemetry%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAfter%20successful%20start%2C%20I%20started%20%3CSPAN%3E%3CSTRONG%3Edirectly%3C%2FSTRONG%3E%3C%2FSPAN%3E%20cmd.exe%20with%20administrator%20privilegs%20and%20run%20sfc%20%2Fscannow.%3C%2FP%3E%3CP%3EIt%20will%20found%20corrupted%20systems%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20Log%20reporting%20and%20why%20a%20clean%20installation%20is%20doing%20so%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20repeated%20the%20steps%20with%20de_windows_10_business_editions_version_20h2_x64_dvd_ce126f3b.iso%20(md5%3A%2035df62707e53c2064641ccd5b91acb8d)%3C%2FP%3E%3CP%3EType%20license%3A%20Enterprise%3C%2FP%3E%3CP%3EAfter%20repeating%20the%20steps%20above%2C%20the%20result%20is%20the%20same.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

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 (using VMware is just an example for easy reproducing. You could also use a host system):

 

  • 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

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

It will found corrupted systems files.

 

What is the Log reporting and why a clean installation is doing so?

 

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.

 

Regards

3 Replies
Highlighted

Hello @Morku,

 

I really appreciate your investigation on this issue. I recommend you to report the problem via Feedback hub, so that it gets addressed by the correct team.

 

Regards.

Highlighted

Hi@Kapil Arya 

thank you for the advise. So I created now: https://aka.ms/AAa48go

But was unsure about the correct categorie.

I thought reporting in this community will be enough, because I don't like the way over Feedback Hub, since I have to enable Diagnostic data. There is even a character limit?

 

Hope it will help.

 

Regards

Highlighted

@Morku, yes, I believe there is character limit of 1000 but you can attach log files or more characters in .txt file.  

 

Regards.