Windows 10: Clean install W10 20H2 showed up sfc errors?

Probably not the best time of year to be posting, so I'll keep it short*Wink

Is it possible to carry out a clean install of W10 (ver. 20H2) on a PC and run SFC without it finding faults to fix / repair?
I have tried doing so twice now, but have not been successful. The first time this happened I was rather surprised to say the least. I was expecting no errors to be found from a clean install. I followed the very helpful instructions on this forum, many thanks for the advice there.

It's a brand new PC, I added my own OS.
Motherboard: Asus Prime B450M-A
CPU: AMD Ryzen 5 3400g
RAM: 16GB (2 x 8 sticks) Gammix D10 3200Hz

Thanks in advance.
Merry Christmas.

:)

 

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.

 

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

Hi Jediael,

the Thread is not about to fix an issue for myself. I created it to report a general issue with the current Windows 10 20H2 build.

All your links are about to fix issues users may have.

And yes, the ISO I used is downloaded by Microsoft and as you can see I verified the ISO with md5. It's the correct and original ISO.

And yes, "sfc /scannow" will correct corrupted systems files. When I run it a second time, no more errors are found.

The issue is, this is on a clean, fresh install.

I don't need help, the developers need to analyze and verify the issue. Thats why I desribe my steps in detail in inital post.

And sure, I would like to know what is broken out of the box in Windows this time. Maybe you can see in the Log? I can't.

Regards,

 

'SFC /scannow' errors on clean install


I decided to run 'SFC /scannow' on my recent clean install of Windows 10 and was surprised that it reported so many errors that cannot be repaired. I installed on a 256GB Samsung Pro SSD. After trying a few recommended fixes that all failed I decided to do clean install on a second SSD which I just finished doing. The only thing I've done is install Win10 Pro from a USB flash drive, install the motherboard drivers and then let Windows do an update. The update also downloaded and installed the NVidia graphics driver. Then when I ran 'SFC /scannow' the errors were there. Many seem related to the openCL.dll as well as other files that seem related to the Nvidia driver.

I have 4 other PCs running Win10 and they all pass 'SFC /scannow' without any problems.

Have any other folks noticed anything strange about Nvidia drivers?

Next step is to do a refresh install and run 'SFC /scannow' before the video driver installs...