SFC found corrupt files on three 7 machines

E

ep0x73

2[H]4U
Joined
Sep 5, 2013
Messages
2,574
Never had any issues but now 3 different 7 machines show corrupt files.

All three work just fine except one that has suddenly liked to BSOD upon wake.

10 and XP machine, no problem on the SAME exact hardware.

WTF, how can 7 get corrupt without doing anything to it?

Last time I ran SFC there were no issues, could some KB have messed up something?
 
Malware could have spread to all three PCs, or a power spike hit all 3 PCs.

It would have been nice if you had logs of the files that were corrupted to see if they were all the same or all different.
 
I tried to pull up the logs but they are a mile long and huge.
All three are not on any network, no malware or viruses.

One machine had 7 installed just a few months ago, how can it be corrupt already?

All three have UPS backup as well.

It really makes no sense.

The 10 machine though is clean and it's been installed for about 8 months so I know it's not hardware related.
It's on the same machine that I have 7 on another drive.
memtest comes back error free.

Maybe 10 is just hardier.

I did a search and there are many hits so I am not the only one.

One thread suggested putting in a 7 disc and doing the "upgrade" which will fill in any corrupt files.
Another thread suggested the files that can't be fixed are not important and to ignore it.

I could try dism /online /cleanup-image /restorehealth like somebody did and it fixed their issues.
 
Last edited:
When I use SFC it always finds corrupt files too. I thought maybe it was due to WU replacing original files with new versions.
 
Seems to do with telemetry, all those KB's I did not install.
The recent ones are for the 10 upgrade.
Newest computer runs fine, no issues. It's my older 7 machine that still has the BSOD upon wake which it never did before.
POQ 144 ends.
2015-08-29 16:36:27, Info CSI 00000350 [SR] Verify complete
2015-08-29 16:36:27, Info CSI 00000351 [SR] Repairing 1 components
2015-08-29 16:36:27, Info CSI 00000352 [SR] Beginning Verify and Repair transaction
2015-08-29 16:36:27, Info CSI 00000353 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:sEcsp8j1bzQfL8GXBLDYa75XHO3O18nSN2IGD9HwDwg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-29 16:36:27, Info CSI 00000354 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-08-29 16:36:27, Info CSI 00000355 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:UhHRB+h2/7TJF0WETX9gJ+sQSdm5gyC4CZCks4nLxvw=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-29 16:36:27, Info CSI 00000356 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-08-29 16:36:27, Info CSI 00000357 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:sEcsp8j1bzQfL8GXBLDYa75XHO3O18nSN2IGD9HwDwg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-29 16:36:27, Info CSI 00000358 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-08-29 16:36:27, Info CSI 00000359 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-08-29 16:36:27, Info CSI 0000035a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:UhHRB+h2/7TJF0WETX9gJ+sQSdm5gyC4CZCks4nLxvw=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-29 16:36:27, Info CSI 0000035b [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-08-29 16:36:27, Info CSI 0000035c [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-08-29 16:36:27, Info CSI 0000035d Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:sEcsp8j1bzQfL8GXBLDYa75XHO3O18nSN2IGD9HwDwg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-29 16:36:27, Info CSI 0000035e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:sEcsp8j1bzQfL8GXBLDYa75XHO3O18nSN2IGD9HwDwg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-29 16:36:27, Info CSI 0000035f [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-08-29 16:36:27, Info CSI 00000360 Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:UhHRB+h2/7TJF0WETX9gJ+sQSdm5gyC4CZCks4nLxvw=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-29 16:36:27, Info CSI 00000361 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:UhHRB+h2/7TJF0WETX9gJ+sQSdm5gyC4CZCks4nLxvw=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-29 16:36:27, Info CSI 00000362 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
2015-08-29 16:36:27, Info CSI 00000363 Repair results created:




To note, running dism scanhealth works but checkhealth or restorehealth throws a 87 error.
Went online looking and no sure answer other then you missed a space which I did not.

dism under windows states it fully functions under 7.
 
Last edited:
Yes all the time.

This is odd, kb947821 showed up in updates, this KB is over a year old.

"Fix Windows corruption errors by using the DISM or System Update Readiness tool"

Installed, still can't do dism
 
I've never had DISM nor SFC completely fix corruption. My advice; save the time and run a repair installation nebulously labeled as the upgrade option when you boot the 7 disc after looking at SMART. If the HDDs show any signs of wear, replace and then image & repair/reformat.
 
I found how to do it on I think the 7 forum. I question how or why this even happened in the first place.
I'd bet it's one of the KB's within the past few months because all 3 machines were perfectly clean.
I just installed 7 on another machine just about 4 months ago and it shows corrupt files that can't be fixed so it has to be some KB after 5/15.
They are just browser computers, no gaming or anything even installed.

From all the threads I read 7 is supposed to be tough and some state they never had a BSOD ever.

Just to note the BSOD upon wake was something to do with directx even though dxdiag shows no issues.
Well I ran the updater for divx and then put it to sleep.
Upon wake a BSOD again, this time it was nvidia.

Using the latest driver just released for my legacy GPU, Guess I'll have to grab some older driver package since this computer is not used for gaming and see if it helps.
 
Update, appears the latest patch for IE 11 is the reason.


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-08-29 17:18

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 467
Found 2 errors
CBS MUM Corrupt Total count: 2

Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-08-30 05:24

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 596
No errors detected


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-08-30 05:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 704
Found 2 errors
CBS MUM Corrupt Total count: 2

Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

Then I find this:

CBS MUM package naming issue causing false coruption issues

chkdsk thinks there are no issues to fixed. running the windows update readiness tool does not resolve the issue. this is a naming mistake caused by Microsoft not by anything else.

this issue first appeared when KB2667402 was released. but the solution for that, no longer works, making me believe that other updates now include and are now propagating the error.

Tech on the MS forum asked if any registry cleaners are being used.

Possible CCleaner is the problem? I do run it to clean up odd and end stuff.
 
MVP's have been saying that forever but as noted in your link:

"So it seems that Registry junk is a Windows fact of life and that Registry cleaners will continue to have a place in the anal-sysadmin’s tool chest"
 
Oh, this is interesting. From the More Info link for KB3068708:

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.
Click to expand...

I notice that utc.app.json and telemetry.ASM-WindowsDefault.json are listed in the logfiles posted in post #5 of this thread.
 
Well, I uninstalled IE and it uninstalled 11 and apparently 10 as well.
Ran updater and installed 10 again with the patches and no BSOD with wake.
Pretty goofy, I never use IE, FF 90% of the time and I also have chrome for some sites
in which it just seems to work better.

I doubt MS at this point is really going to try and fix any issues with 7 unless it's a critical flaw
or security patch.

As for KB3068708 I do not have it installed on any computer. I don't want to give MS tracking and I could care less
to update said machines with 10 at this point.
 
Regarding KB3068708, here's a bit more info: that it's a re-issue of KB3022345, which also made SFC report corruption on those two .json files. Just saying in case you have the older version but not the newer version.

I don't think it's a coincidence that the two files mentioned in those KBs just happen to be the ones reported in your logs.
 
So, the moral of the story is don't pay any attention to what SFC reports. Junkware.
 
rezerekted said:
So, the moral of the story is don't pay any attention to what SFC reports. Junkware.
Click to expand...

I've learned this awhile ago. SFC is a joke when half the time an official windows update is the sole cause of half the problems with SFC failing to repair problems.
 
evilsofa said:
I don't think it's a coincidence that the two files mentioned in those KBs just happen to be the ones reported in your logs.
Click to expand...

Good catch, sure enough that KB is there on all 7 machines from May 2015.

I probably ran SFC after that and did not have any issues, why it shows up now I am not sure.

This does not appear to be the wake bsod issue I have with 1/3 7 machines though.

I rolled back nv drivers to earlier ones and will test it again.

all the blue screens are either nvidia related and divx.

What is most odd, same exact hardware with my drive attached with 10 has zero issues and it's running the most recent driver.

Not sure how the hell divx gets corrupted, dxdiag says all is good.

Update, after removing both KB's everything comes back clean.
On my other machine with the wake issue, did the same and went back to older nvidia drivers.

Not sure which one helped but no more wake issues either.
 
Last edited:
You must log in or register to reply here.
Back
Top