Windows 10: SFC Ends At One Percent

Windows 10 Enterprise x64 20H2 Build 19042.804
Intel DH67GD
Intel Core i7-3770
EVGA GeForce GTX 1060 6GB
Samsung SSD 860 PRO 512GB
32GB System RAM


Recently ran SFC to check on things, and it ended itself at 1%.

This has never happened to me, as SFC has always ran its course to 100%, and then reported any errors it may have found.

I have collected the CBS log, and a screen shot, and have attached those to this post.

To be honest, nothing was even wrong with my system, I just hadnt run SFC in a while, and took a stab at it. Glad I did, as this shows me something needs addressed.

Any help?

Thanks.

:)

 

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

 

How to fix SFC Scannow Corrupted files

Yes, it does. The sequence you describe is common.

If you want to see additional examples {written at the time of some widespread problems with SFC caused by a WD platform update} there is a list at the end of my consolidated ditty on SFC errors [WD update problem] - TenForums and my post also has some suggestions about useful extractions from the CBS log.

Denis

 

Moving Unallocated Disk Space to End of Disk

Was commenting on the pic in post #21. Not suggesting anything. It just looked like the step you were doing was incomplete.