SFC reveals errors that cannot be fixed

gil · 24 Apr 2016

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.

I've attached the log file in ZIP.
What can I do to fix this?

Attachment 76487

dalchina · 24 Apr 2016

Hi, at the end it says
"Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired"

Have you tried running SFC again after a restart?

If SFC continues to fail, the next procedure is this:
If SFC /Scannow reports a failure, then the following downloads new files:

Open a Powershell window and at the prompt type (or copy and paste)
DISM /Online /Cleanup-Image /RestoreHealth and press <Return>.

gil · 25 Apr 2016

the dism command worked but from CMD.
I then ran sfc and it fixed everything.

I know what it was.
there's a bug in gpedit.msc when opening it. fixing the bug involved altering a file which then is picked up as sfc error.

dalchina · 25 Apr 2016

Hi, good that you identified it - just come across this. MS knows about it..

http://www.winhelponline.com/blog/gp...dmx-kb3147458/

After installing the April Cumulative Update KB3147458, the following error may pop up when opening the Group Policy Editor.

Resource ‘$(string.RequirePrivateStoreOnly)’ referenced in attribute displayName could not be found.

Detailed fix in the above,

else

Uninstall the update
Hide it
https://support.microsoft.com/en-us/kb/3073930

else
live with it for a while

gil · 25 Apr 2016

yes that's exactly it. I'll live with it :)