Windows 10: Upgrade to 20H2 bumpiness & SFC Report

Greetings,

This time I wanted to verify that cumulative or feature updates GENERATE issues. So I did an SFC before updating my PCs, and on one of them CBS.log stuff appeared. In my gut I knew this was happening but I finally proved it. One pass of a DISM fixed it -- so it probably wasn't something major. (I remember when a few passes and reboots were required.)

ALSO two of my three PCs refused the 20H2 update. To be clear each PC saw the update, recommended the update, downloaded the update -- and upon reboot -- I was still at 2004.

I used the Windows Update assistant to force it. Hopefully all is well.

:)

 

HELP with SFC after DVD upgrade to 10 please

Messing around with the component store is tricky.

After you restore I suggest using Windows to correct the issue
Do NOT run SFC until we're sure - that just puts you in a loop or worse

1. Programs and Features: Uninstall Avast
   
   
2. Run the Avast cleaner
   
   
3. Programs and Features: Make a note of what C++ redists are installed
   Uninstall all C++ redists (both x86 and x64 versions)
   Restart the machine
   Re-install the C++ redists (both x86 and x64 versions) from the MS link I gave you above that were installed
   
4. Cleanup the image
   See: DISM - Repair Windows 10 Image - Windows 10 Forums
   
   Use step 6. To Use DISM /RestoreHealth /Source:wim Command if you downloaded the ISO from Techbench
   
   Use step 7. To Use DISM /RestoreHealth /Source:esd Command if you used the Media Creation Tool
   Report back if DISM reported any errors - I'll need to look at the CBS log

That's enough for now - those steps should clean up your machine. Remember, the only thing SFC reported was the reference to AVAST C runtime. Reinstalling MS C runtime should make them the SxS winners.

After you complete those steps, I'll ask you to look at a few other things before proceeding.
Do NOT run SFC until asked ... you might have to divert from the path to fix something else

 

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 reports corrupt files that cannot be repaired

Hi Jay,

For to better assist you with the SFC reports issue, we'd like to know the following:

• Have you installed any Windows updates prior to this issue?
  
• Please provide us a CBS logs for us to determine what is the file that cannot be repaired.
  

To get the logs, please follow the steps below:

• Open a Command Prompt (Admin).
  
• Copy and paste findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfclogs.txt”, then hit
  Enter. (This will create a sfclogs.txt file on your desktop).
  
• Open the sfclogs.txt and check the result of SFC scan.
  

Note: SFC cannot always fix corrupted files.

We're looking forward to your reply.