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

[aussiepride]

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.

 

[GokAy]

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)

 

[aussiepride]

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?

 

[GokAy]

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

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

 

[aussiepride]

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?

 

[AddRAM]

Did you remove both updates if you have them ?

 

[aussiepride]

Did you remove both updates if you have them ?

I just removed KB3068708

 

[AddRAM]

Do you have KB3022345 installed ?

Did you uninstall it ?

 

[aussiepride]

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?

 

[AddRAM]

Did you remove both updates if you have them ?

Once again.

 

[aussiepride]

Did you remove both updates if you have them ?

Once again.

Uninstalling both of those worked! Thanks for your help!

 

[LaurieD227]

I found the same problem when I ran SFC /SCANNOW.

When I went searching for information on this, I found the following information in the Microsoft article about KB3068708:

"The included service uses SSL (TCP Port 443) to download manifests and upload data to Microsoft when data is available for upload. The service uses the following DNS endpoints:

• vortex-win.data.microsoft.com
• settings-win.data.microsoft.com

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

• telemetry.ASM-WindowsDefault.json
• utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device that is running this update, and this issue will be fixed in a later service update."


Here's the link:
https://support.microsoft.com/en-us/kb/3068708

Of course, each of us is free to go ahead and uninstall the two updates discussed in earlier posts if we don't want to wait for the issue to be fixed

 

[LaurieD227]

One other interesting thing - I have an older Win7 Pro machine that has the KB3068708 and KB3022345 updates installed, and those SFC /SCANNOW results come back with no errors.

Hmmm .....

 

[GokAy]

Did you run sfcfix earlier for KB3022345 on that Win7 Pro machine? I used to have KB3022345 (later uninstalled but fixed with SFCFix), and now have KB3068708, no corruptions also.

 

[Layback Bear]

I remove both of those KB's and when they came back in Windows 7 Updated I hid them.
Then ran sfc /scannow a couple of times with reboots between and problem was solved.

Done it on my Pro and Home Premium systems.

KB3022345
KB3068708,

 

[LaurieD227]

Nope, I didn't run SFC for the KB3022345 install as far as I recall. I wasn't having any issues on that machine (an old Dell D630) back in May when I installed KB3022345. This past weekend, I installed KB3068708 along with some other updates, and had no issues.

After I found the issue on my ProStar Win7 Pro, I got curious, so I checked the D630 - yep, both updates were there - and ran SFC /SCANNOW - nope, no false corruption findings, just a clean bill of health.

If I had to guess, I'd think it may be tied to a combination of other characteristics of the two machines - maybe software, maybe hardware - where something about the newer set up triggers the false corrupt reading. The D630 is a 32-bit machine and the other one is 64-bit but I have no idea if that contributes to the fact that one has the problem and the other does not.

Regardless, I have uninstalled both KB3022345 and KB3068708 from my ProStar, and its SFC results are now clean. I may choose to experiment with re-installing one or both to see if I once again get the error. If I do that, I'll probably try your technique of running sfc after installing KB3022345 to see if that shows clean before installing KB3068708.

If I do run these experiments, I'll let you know what happens.

 

[LaurieD227]

I found a little bit more information on this whole situation.

--KB3022345 was released in multiple versions, so perhaps my D630 has a version that doesn't have the problem.
--KB3022345 is no longer offered; instead, people are referred to KB3068708
--There's no clear explanation of what either of these updates do, but other folks seem to think they pertain to the upcoming Windows 10 release

http://www.sevenforums.com/performa...c-exe-how-seriously-should-i-take-report.html

Microsoft confirms patch KB 3022345 breaks SFC /scannow | InfoWorld

The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files

Based on my additional reading, I think I'm going to just hide the KB3068708 Update for now instead of installing it. I want to wait and see if Microsoft issues a fix for it that works, and I'd really like to know what it does.