SFC Finds Corrupt Files but is Unable to Fix

I ran sfc /scannow in an admin command prompt, however when it completes I receive this message:

"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios."

Anybody know what this means, and how to fix it? I think that it may be somehow related to a few errors happening on my laptop--such as live tiles not working, and the inability to use some apps without crashes.

Thanks in advance!

CV

CosmicVibe said:

I ran sfc /scannow in an admin command prompt, however when it completes I receive this message:

"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios."

Anybody know what this means, and how to fix it? I think that it may be somehow related to a few errors happening on my laptop--such as live tiles not working, and the inability to use some apps without crashes.

Thanks in advance!

CV

Open Command Prompt Admin and copy paste the following.
dism /online /cleanup-image /restorehealth

axe0 said:

When you get this error it means that the System File Check a.k.a. Windows Resource Protection simply could add/repair missing or corrupted files or other problems with these files.

If you get this error you should try the following a few times:

• sfc/scannow
• reboot
• sfc/scannow

Only when after a few times sfc/scannow still hasn't solved it, then you could try DISM /Online /Cleanup-Image /RestoreHealth.

A reboot is necessary for sfc in order to try to fix the problems, it usually takes a few tries for sfc to solve the problems.

I tried your aforementioned method, rebooting 3 times, and running sfc /scannow 3 times, but with no luck I've decided to try the DISM method.

Thanks y'all!
CV

axe0 said:

When you get this error it means that the System File Check a.k.a. Windows Resource Protection simply could add/repair missing or corrupted files or other problems with these files.

If you get this error you should try the following a few times:

• sfc/scannow
• reboot
• sfc/scannow

Only when after a few times sfc/scannow still hasn't solved it, then you could try DISM /Online /Cleanup-Image /RestoreHealth.

A reboot is necessary for sfc in order to try to fix the problems, it usually takes a few tries for sfc to solve the problems.

I have tried that method, the DISM, and received the following message:

"Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

[==========================100.0%==========================]

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. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>"


While great at operating other Windows features, the Command Prompt is a land I've yet to explore. Thanks for the help again.

CV

So basically I'm going to Start>Settings>Update & Security>Recovery>Reset This PC

Right?

Hi everyone!

My laptop also shows the message "Windows Resource Protection found corrupt files but was unable to fix some of them"when I run sfc /scannow in an administrator command prompt. In addition to that, the home button, cortana, and the audio system don't work. Nothing happens if you click on them. And connecting to the internet is impossible, due to problems the troubleshooter could not identify. These problems started soon after I downloaded windows 10.

Thanks in advance!

Really starting to regret going to windows 10... So many issues with corruption... Just doesn't seem to hold up like 7 did when there was an issue. I'm having this issue now... Windows 10 is nowhere near stable yet.