sfc /scannow found corrupt files but was unable to fix them

Page 1 of 2 12 LastLast

  1. Posts : 26
    Windows 7 Home Premium 64-bit
       #1

    sfc /scannow found corrupt files but was unable to fix them


    Hi everyone,
    I'm new here so please forgive me if I have explained this badly or if I haven't provided enough information. I ran sfc /scannow, and received the following error:

    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

    I checked the CBS.log and I found these lines which could point to the problem:
    2015-06-23 15:44:41, Info CSI 00000349 [SR] Beginning Verify and Repair transaction
    2015-06-23 15:44:41, Info CSI 0000034b [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-06-23 15:44:41, Info CSI 0000034d [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-06-23 15:44:41, Info CSI 0000034f [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-06-23 15:44:41, Info CSI 00000350 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
    2015-06-23 15:44:41, Info CSI 00000352 [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-06-23 15:44:41, Info CSI 00000353 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
    2015-06-23 15:44:41, Info CSI 00000356 [SR] Repair complete
    2015-06-23 15:44:41, Info CSI 00000357 [SR] Committing transaction
    2015-06-23 15:44:41, Info CSI 0000035b [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

    My question is, what do I do to resolve the problem from here? Feel free to let me know if your require any more info or if there is anything I can do to assist in resolving the problem. Thanks so much for your help.
      My Computer


  2. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #2

    Those are false warnings, the 2 files are not corrupt and this issue is known.

    You can try to run SFCfix The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files

    or if that fails uninstall KB3068708. (It may also be that you still have KB3022345, which was replaced with KB3068708 later)
      My Computer


  3. Posts : 26
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    GokAy said:
    Those are false warnings, the 2 files are not corrupt and this issue is known.

    You can try to run SFCfix The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files

    or if that fails uninstall KB3068708. (It may also be that you still have KB3022345, which was replaced with KB3068708 later)
    Thanks for your help! I do have KB3068708 installed. However, wasn't KB3068708 supposed to fix the problem?
      My Computer


  4. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #4

    Yes, but you are not alone in still getting corruption after installing KB3068708.

    Try uninstall (check SFC /scannow) and reinstall KB3068708 (check again).
      My Computer


  5. Posts : 26
    Windows 7 Home Premium 64-bit
    Thread Starter
       #5

    GokAy said:
    Yes, but you are not alone in still getting corruption after installing KB3068708.

    Try uninstall (check SFC /scannow) and reinstall KB3068708 (check again).
    Just did you said about and got the same "Windows Resource Protection protection found corrupt files but was unable to fix them" both times. Any ideas?
      My Computer


  6. Posts : 13,576
    Windows 10 Pro x64
       #6

    Did you remove both updates if you have them ?
      My Computer


  7. Posts : 26
    Windows 7 Home Premium 64-bit
    Thread Starter
       #7

    AddRAM said:
    Did you remove both updates if you have them ?
    I just removed KB3068708
      My Computer


  8. Posts : 13,576
    Windows 10 Pro x64
       #8

    Do you have KB3022345 installed ?

    Did you uninstall it ?
      My Computer


  9. Posts : 26
    Windows 7 Home Premium 64-bit
    Thread Starter
       #9

    AddRAM said:
    Do you have KB3022345 installed ?

    Did you uninstall it ?
    I do have KB3022345 installed but I didn't uninstall it; I only uninstalled KB3068708 and reinstalled it. Which one would you like me to uninstall or should I uninstall both?
      My Computer


  10. Posts : 13,576
    Windows 10 Pro x64
       #10

    AddRAM said:
    Did you remove both updates if you have them ?
    Once again.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:47.
Find Us