Windows 10: 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 hasno 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.


Result will be in next post


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.

:)

 

Need a file from Windows 7

Have you tried sfc /scannow? It is supposed to find and repair corrupted operating system files.

 

sfc /scannow error

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?

 

icons dissapearing

Hey there, @cookiemonster!

Since you've already scanned for malware and viruses, I have to ask if you've installed any new software or Windows Updates prior to the BSOD accident?
What I can suggest you to do is run the sfc /scannow command from the Command prompt.
This command scans the integrity of all Windows system files and replaces corrupted or damaged versions of the files with their correct ones. Here's a tutorial that can show you how to do the scan: SFC /SCANNOW Command - System File Checker - Windows 7 Help Forums

You can give it a try, before doing a clean install as a last resort! *Smile
I hope it helps!
SuperSoph_WD