0

I am trying to scan for corrupted files in Windows 7 using sfc/ scannnow from cmd, but the scan stops at 73% and I get the message:

  Windows Resource Protection could not perform the requested operation. 

Here is how it looks:

enter image description here

Questions:

  1. What could be the problem?

  2. How can I solve it?

Edit:

Here is the result from sfc /verifyonly: sfcdetails.txt. Accompanied by the following message:

Windows Resource Protection found integrity violations.     
  • What does sfc /verifyonly result in? Export your current and the later results with command findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt to dropbox/onedrive/google drive/pastebin and post the link here. – Nikhil_CV Sep 21 '15 at 11:53
  • 1
    Also, do you have installation disc of Windows7 with you? Try running a disk check by chkdsk /r – Nikhil_CV Sep 21 '15 at 11:55
  • 1
    The log file will contain more information. Furthermore I have only ever had this happen due to a system disk that was starting to fail. – Ramhound Sep 21 '15 at 11:56
  • @Nikhil_CV I'm running sfc /verifyonly now. Regarding the installation disc, I'm not sure if I have it. As far as I remember I bought it online and it was with some codes to download a copy or something like that – Ziezi Sep 21 '15 at 12:08
  • Okay, try the check disk command afterwards. If it asks to schedule the scan for running after a restart, allow it. – Nikhil_CV Sep 21 '15 at 12:11
1

What could be the problem?
Since disk check (chkdsk) has attempted/fixed some errors, there was some problem/error with your storage media (hard disk) which corrupted the Windows OS related files. Since the files which were corrupted belong to a non important Windows update, its your choice to fix it or ignore it. But to solve System File Checker from failing, we should fix the error brought up by the scan, related to the files.

sfc /scannow will attempt to fix the file related corruptions, which got stuck in this case.

sfc /verifyonly will check for file corruptions, but will not attempt to fix.

If sfc command fails to fix the corruption, your next option is to extract the file from original media (or do DISM) after eliminating storage media related problems/errors.

How can I solve it?
Here, running the disk check fixed the hard disk related problem and uninstallation or re-installation of the corrupted update will fix the file corruption. Following is the analysis:

Here is what your log tells:

2015-09-21 14:01:53, Info                  CSI    000001bf [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-21 14:01:53, Info                  CSI    000001c1 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-21 14:01:55, Info                  CSI    000001c3 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-21 14:01:55, Info                  CSI    000001c4 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-09-21 14:01:55, Info                  CSI    000001c6 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-21 14:01:55, Info                  CSI    000001c7 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"

This refers to a corruption to a Windows update: KB3068708 (its an update, black listed by some users and writers as one of the 'spy patch', simply because it gathers data from your system and sends to MSFT)

By applying this service, you can add benefits from the latest version of Windows to systems that have not yet been upgraded.

You can see if this update is listed in your Control Panel > All Programs and Features > Installed Updates. If you find it, you should right-click it and select uninstall. It will be uninstalled and installed if you choose to install it next time you check for Windows updates. If not listed in 'Installed updates', try this:

wusa /uninstall /kb:3068708 /quiet /norestart

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.