Windows 7 update (KB3022345) causing corrupt files

[ehasanov]

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]

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]

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]

kb 3022345

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]

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

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

 

[maxseven]

I failed to note the link reference to W8

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.

:shock:

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]

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,
View attachment 358505

 

[carwiz]

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]

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]

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?!

 

[Go The Power]

Hello,

I am author of this article.

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.

:shock:

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.

This is not quite correct, SFCFix will not automatically repair these files. The reason why SFCFix was able to repair your corrupt files along with ehasanov files is because both of you had already downloaded the SFCFix.zip file. SFCFix is very advanced when SFCFix scans the CBS log for any corruptions SFCFix will then find out what the file hash of the corrupt file is supposed to be (this is done with the SHA256-Base64 hash read from inside the associated manifest file).

I have just taken a look at the files within the Windows 7 version of this update and those two files have the same SHA256-Base64 hash as the ones from the Windows 8 version. This is why SFCFix was able to track down and repair these files for you.

At the time when I wrote this article I was not aware it was also causing issues on Windows 7 machines.

Could you please zip up the entire CBS folder and upload this OneDrive/Dropbox then share the link back here? I would like to be able to update my article to include a Windows 7 fix.

Thanks

 

[NoN]

Hello,

I am author of this article.

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.

:shock:

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.

This is not quite correct, SFCFix will not automatically repair these files. The reason why SFCFix was able to repair your corrupt files along with ehasanov files is because both of you had already downloaded the SFCFix.zip file. SFCFix is very advanced when SFCFix scans the CBS log for any corruptions SFCFix will then find out what the file hash of the corrupt file is supposed to be (this is done with the SHA256-Base64 hash read from inside the associated manifest file).

I have just taken a look at the files within the Windows 7 version of this update and those two files have the same SHA256-Base64 hash as the ones from the Windows 8 version. This is why SFCFix was able to track down and repair these files for you.

At the time when I wrote this article I was not aware it was also causing issues on Windows 7 machines.

Could you please zip up the entire CBS folder and upload this OneDrive/Dropbox then share the link back here? I would like to be able to update my article to include a Windows 7 fix.

Thanks

Welcome to SevenForums,

First, thanks for your SFCFix tool and explanation how it tracks the errors with the hash, in the CBS.log

I do not think they did mentioned there was a bug on Windows 7 but only with the article ID, also the tool was mentioned to be for Windows 8, thus it does run well from the .exe.

I have use it on mine just to check (without the Kb3022345 installed) because i wanted to know what the Fix tool report in the log and if it does works well, so indeed the tool ran fine on my Windows 7 x64, and as expected didn't report any errors repaired.

 

[Go The Power]

Hello NoN,

The tool itself work on Vista, Win7 and Windows 8, the fix in my article is only for Windows 8 machines

I should of been more clear in my previous post, the was a in issue with the Windows 7 install. If you take a look at ehasanov SFCFix report log:

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.

The reason why SFCFix noticed these above files needed fixing would of been from the CBS log, if there was no issue with the Windows 7 update install, then SFC /SCANNOW would not of detected an issue, which means SFCFix wouldn't have anything to repair

 

[NoN]

Thanks to correct me, i just read your article and realize quickly my mistake and saw the script you provided on the Tech Cookbook site for Windows 8.

Unfortunately i can't provide you a CBS.log as i haven't install the article ID mentioned here. Yes, the tool itself runs fine thats what i wanted to check on my side.

Edit: the forums member ehasanov looks like someone pretty discreet, hope you'll get a log soon to work on a special Windows 7 script.

 

[ehasanov]

Hi
Just to add.
I perform only sfcfix without using zip file (included for problems in W8).

"Quote from Go The Power
This is not quite correct, SFCFix will not automatically repair these files. The reason why SFCFix was able to repair your corrupt files along with ehasanov files is because both of you had already downloaded the SFCFix.zip file. SFCFix is very advanced when SFCFix scans the CBS log for any corruptions SFCFix will then find out what the file hash of the corrupt file is supposed to be (this is done with the SHA256-Base64 hash read from inside the associated manifest file)."

Thanks

Edin

 

[VXER]

@ehasanov
Using the sfcfix.exe fixed my issue,thanks !

 

[NoN]

Last added posts brings to confusion too. The tool seems to picks up the file hash errors whenever its 8 or 7 because they are similar based. Sorry for having mistaken.

 

[Cypherdude]

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.
...
----------------------EOF-----------------------

Everyone,
you may want to delay using SFCFix.exe. I uploaded SFCFix.exe to VirusTotal and it came up with 1 hit, TrendMicro-HouseCal: Suspicious_GEN.F47V021. Here is a report on Suspicious_GEN.F47V0219.

Besides, I don't think SFCFix.exe actually gives you a correct copy of "utc.app.json" and "telemetry.ASM-WindowsDefault.json". I think it just tricks SFC.exe to stop giving error messages. The whole purpose of using SFC.exe is to find corrupted files and replace them with good copies, not to trick SFC.exe to stop giving error messages.

Does anyone know where I can find good copies of "utc.app.json" and "telemetry.ASM-WindowsDefault.json" for Windows 7 Pro? My laptop has Windows 7 Home and it does not have these 2 files.

 

[Go The Power]

Last added posts brings to confusion too. The tool seems to picks up the file hash errors whenever its 8 or 7 because they are similar based. Sorry for having mistaken.

I had a look inside both the Window s7 and Window 8 version of this update, both contain the same files, this is why SFCFix was able to use the Windows 8 file to fix the Windows 7 files, because they are both the same

Everyone,
you may want to delay using SFCFix.exe. I uploaded SFCFix.exe to VirusTotal and it came up with 1 hit, TrendMicro-HouseCal: Suspicious_GEN.F47V021. Here is a report on Suspicious_GEN.F47V0219.

1 hit out of 56, no one pays that closely to one hit, that is just paranoia! I can assure everyone here that SFCFix is not a virus and does not contain any malware code.

Besides, I don't think SFCFix.exe actually gives you a correct copy of "utc.app.json" and "telemetry.ASM-WindowsDefault.json". I think it just tricks SFC.exe to stop giving error messages. The whole purpose of using SFC.exe is to find corrupted files and replace them with good copies, not to trick SFC.exe to stop giving error messages.

Does anyone know where I can find good copies of "utc.app.json" and "telemetry.ASM-WindowsDefault.json" for Windows 7 Pro? My laptop has Windows 7 Home and it does not have these 2 files.

This is totally wrong, there is no trick, SFCFix repairs the corrupt file, read my previous two posts.

If you dont want to trust SFCFix, download the update from the MS Download Center and extract the contents...

 

[Cypherdude]

If you dont want to trust SFCFix, download the update from the MS Download Center and extract the contents...

I just read The Tech Cookbook and it states you must download 2 files, SFCFix.exe and SFCFix (x64 fix) or SFCFix (x86 fix). The OP did not mention the second file:

How to fix this issue:

To repair these two corruptions is rather straight forward, it is important to know if you need the x86 or the x64 version of these files. If you are unsure please stop here and ask for help at Sysnative forums (free support) Windows Update Help Forum you will be able to find me there under the user name Go The Power

SFCFix Script

Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download SFCFix.zip from one of the below links, and save this to your Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
3. If you have a x64 machine download this version: SFCFix (x64 fix)
4. If you have a x86 machine download this version: SFCFix (x86 fix)
5. Save any open documents and close all open windows.
6. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
7. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
8. SFCFix will now process the script.
9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
10. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please – put tags around the log to break up the text.

What happens if you only run SFCFix.exe without the second file?