New
#11
Corrupted files reported after sfc/scannow
Yes, corrupt files were found but Windows Resource Protection unable to repair.
Yes, corrupt files were found but Windows Resource Protection unable to repair.
I copied and pasted the results of the Sfcdetails.txt file but I have only included the results of damaged files that cannot be repaired.
Part 2 of this message seems to show that the files in question were repaired.
I am looking forward to your response.
2015-06-22 06:57:53, Info CSI 000001bb [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-22 06:57:54, Info CSI 000001bd [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-22 06:57:55, Info CSI 000001bf [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-22 06:57:55, Info CSI 000001c0 [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-22 06:57:55, Info CSI 000001c2 [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-22 06:57:55, Info CSI 000001c3 [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-22 07:06:01, Info CSI 00000353 [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
- Part two: files that were repaired
2015-06-22 07:06:01, Info CSI 00000355 [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-22 07:06:01, Info CSI 00000357 [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-22 07:06:01, Info CSI 00000358 [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-22 07:06:01, Info CSI 0000035a [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-22 07:06:01, Info CSI 0000035b [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-22 07:06:01, Info CSI 0000035e [SR] Repair complete
2015-06-22 07:06:01, Info CSI 0000035f [SR] Committing transaction
2015-06-22 07:06:02, Info CSI 00000363 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
The PC is infected. And after dealing with the infection, there are a lot of corrupted files.
A clean reinstall will be the right for you.
Backup any necessary data, and do a clean reinstall.
The 'corrupted' files are to be expected - these are the result of a coding error by MS, and supposedly don't matter.
The errant update is KB3068708 - you can either ignore the 'errors' and MS will eventually get around to fixing them, or you can uninstall th update and hide it to prevent it reinstalling. When MS produce a fixed update it will then install in the normal way.
Can I respectfully suggest the OP run this? How to record Kaspersky Rescue Disk 10 to a USB device and boot a computer from it have found it good on account of it being bootable and doesn't involve Windows.
From my experience with Toshiba you can get rid of all the bloat of which there is a mile of it but even with a clean install some will return with Windows updates - don't ask me why but it does.
This issue is not new.
If you wish to get rid of it, please do the following:
Open the Control Panel and click on Programs and Features.
When open, click View Installed Updates in the upper left portion of the page.
Click on it and see if you have KB3022345 Windows Update installed.
WUs are listed in numerical order.<<---Looked too fast, they are not! Sorry!
If you find it, right click on it and uninstall it.
Here is more info with a different approach. It also shows some examples:
The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files
Last edited by cottonball; 24 Jun 2015 at 13:12.
BTW, KB3022345 telemetry.ASM-WindowsDefault.json and utc.app.json also show for KB3068708.
They the same issues!
Cottonball I was excited to see the instruction you posted because I have always fouind looking for certain updates very tedious and usually end up system restoring to find a culprit.
But I tried this and they are all over the hogshop?? - is there any way of getting them into numerical order then??When open, click View Installed Updates in the upper left portion of the page.
Click on it and see if you have KB3022345 Windows Update installed.
WUs are listed in numerical order.
Sorry webgal a bit OT
Simply use the Search box in the top right of the window, and enter the full KB number (KBxxxxxxx) - it finds it for you