Windows 10: sfc /scannow Found errors, but couldn't fix all of them

Hi, everyone.


As the title says, when I ran sfc /scannow just now, it reported that it found errors but was unable to fix all of them. Here's the full output:


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection found corrupt files but was unable to fix some of 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.


The CBS log file is on my OneDrive. Here is a link.


The reason I ran the scan is because recently, I noticed that my right arrow key and some number keys on my numpad have stopped working. I don't know why it happened, but it seems to have started happening after a recent Windows Update. It's downloading and installing the update to version 1903 now, by the way. So I think I got all of the updates up to that point. Thanks in advance for any help for the problem.


Please note: I'm not sure if "Performance & system failures" is the right place to post this. Please move it if it isn't.

:)

 

sfc /scannow errors


Important thing to remember is that the SFC / SCANNOW cannot always fix all errors at once. It is quite often required to run SFC /SCANNOW several times.

I have often had a situation that only a third, fourth or fifth run has finally reported "No more errors".

This is how it should be done:

• SFC / SCANNOW
• If SFC reports not all errors were fixed, reboot and run it again
• SFC / SCANNOW
• If SFC again reports not all errors were fixed, reboot and run it again
• And so on

Screenshot from the TenForums SFC tutorial:

 

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 Error-Overlapuplicate ownership for directory


Win 10 Pro (64 bit) on Intel DP-43TF motherboard on an Q9650 core2 quad at 3GHz with 8GB memory.
sfc /scannow fails at 66% completion with multiple "Error - Overlap: Duplicate ownership for directory" errors with different directories being listed.
What needs to be done to resolve this issue to fix the issue?

I cannot upload the CBS.log file - the error is "Your file of 9.03 MB bytes exceeds the forum's limit of 2.00 MB for this filetype."

Any suggestions?