Windows 10: Windows 10 giving configuration corrupted message but /sfc scannow said nothing amiss.

Have been having issue where computer fails to boot since installing brand new ram. Ran sfc /scannow in August and issue fixed itself. New Windows 10 update reignites issue of computer failing to boot properly. Blue screens and prompts me to F1 recovery mode to where just exiting fixes the issue. Sometimes will not detect second monitor as screen 2 and display two screen 1s, crashes immediately after. Ran sfc scannow, nothing was detected. Ran /cleanmgr, pc ran smoother. Now displays corrupted configuration message a day later. What do i do beyond this point?

:)

 

sfc -scannow failure

I've been having occasional slowdowns on my laptop and it was suggested I run sfc- scannow to check to see if there was anything amiss in Windows files but when I try to run it the scan fails in the verification phase at 25% every time. I was wondering if
anyone knew what could be causing this and how to fix the issue.

Thanks.

 

SFC /SCANNOW Errors After Update

I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with Error: 0x800f081f "The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature."
4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."

Please advise:

1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?

 

SFC /scannow ?? corrupt files? I'm lost...

Try sfc /scannow a couple of times and do a full restart. If that doesn't work try Dism /Online /Cleanup-Image /RestoreHealth from an admin command prompt. Then try sfc /scannow again. Come back for more advice if that Dism command fails or wants a source file. See also DISM - Repair Windows 10 Image