Windows 7 update (KB3022345) causing corrupt files

ehasanov · 07 May 2015

Hi
Could somebody check this, but it looks like this update causes corruption.
I run sfc /scannow and I get :

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-05-06 21:16:07, Info CSI 000001b9 [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

I searched a little bit and found this:

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

It looks similar but I'm not sure that solution on that page is applicable to W7 64 bit.

Thanks

Edin

P.S. Update. sfc /scannow was performed without errors before update with optional updates. Tried on my laptop. After update corruption

ehasanov · 07 May 2015

Ok Guys.
Update 2.
I downloaded sfcfix.exe from this link: http://www.sysnative.com/niemiro/apps/SFCFix.exe
After running fix and after that perform again sfc /scannow everything back to normal.

This is report after fixing:

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-07 15:00:07.345
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\utc.app.json.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\telemetry.ASM-WindowsDefault.json.

SUMMARY: All detected corruptions were successfully repaired.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-05-07 15:03:39.443
----------------------EOF-----------------------

NoelDP · 07 May 2015

Let's check that there are no more files needing work.

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

torchwood · 07 May 2015

Hi Ehasanov,
This KB is part of the W10 readiness package, and is a optional/recommended update.

if you search this forum for that KB you will find that a number of users have uninstalled and hidden myself included.
(News subforum Microsoft silently preparing your PC for Win 10)
Roy

NoelDP · 07 May 2015

...and what does that have to do with anything?

Paranoia has its place - but it's not here!

maxseven · 07 May 2015

ehasanov said:

Hi
Could somebody check this, but it looks like this update causes corruption... I searched a little bit and found this:

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

It looks similar but I'm not sure that solution on that page is applicable to W7 64 bit.

Yikes I followed the link and the exact procedure described there (with x64 script) before realizing it REFERS TO WINDOWS 8 and I of course have W7.

Oh well--did it work? Well firstly thanks ehasanov for bringing this to my attention because yes indeed I just did the updates today which included the subject one, and so I ran sfc /scannow and sure enough "unable to fix corrupted files". Gotta nip this one in the bud or much later when I notice the sfc failure I'll forget what the cause was.

But my late-afternoon weariness rendered me unable to notice that link's W8 reference, so after running exactly as they'd recommended with the x64 script, while it SAID the corruptions were successfully repaired they were not according to another run of sfc /scannow.

Then I ran SFCFix.exe alone as you had and ran sfc /scannow again. Well, I got the exact same SUCCESS! report as you, and thankfully my sfc /scannow result does this time report-back as good.

Whew, I'd rather be lucky than smart!

Bottom line: run SFCFix.exe by itself and that works for W7, or at least it did for my system.

ThrashZone · 07 May 2015

That update is just 1 of many Optional updates I've hidden,
These are most of the recent preparation updates for win-10 and 6 I suppose,
Attachment 358505

carwiz · 08 May 2015

It wouldn't be the first time WU has produced corrupt files. Remember the fiasco not too long ago with an update producing non-booting PCs? All that just to update some country's monetary symbol. (How soon we forget.)

The WUs are a real threat. The recent W10 readiness updates are no different. They have produced their own share of system errors and corrupt files. The paranoia, as it's been called, is nothing more than "fear" or a perceived threat and justified based on real-life experience with the updates. People that call this paranoia have their head... in the sand.

NoN · 08 May 2015

Does those that have it installed knows if this "tracking service collects data about functional issues in Windows"
had recorded this corrupted files issue, in case.

Kidding...:)

This update is optional and only for those that wish to upgrade.

maxseven · 08 May 2015

NoN said:

This update is optional and only for those that wish to upgrade.

FWIW it was not listed as Optional but rather Important on my system. I do wonder what, if anything, MS is going to do (or CAN do) to repair the damage this has done to everyone who has installed it re the sfc "corrupt files" issue.

I also wonder if anyone here knows exactly what SFCFix.exe actually does. If it simply restores older files to ones system, would that not create other problems for the future?!

Windows 7 update (KB3022345) causing corrupt files

Windows 7 update (KB3022345) causing corrupt files

kb 3022345

I failed to note the link reference to W8