New
#770
Hello Somuch2learn, and welcome to Seven Forums.
From you log file, it's the KB3068708 update for the same false mismatch issue. Nothing needs to be done. :)
Hello Somuch2learn, and welcome to Seven Forums.
From you log file, it's the KB3068708 update for the same false mismatch issue. Nothing needs to be done. :)
Brink, that's reassuring. Thanks for your reply
I noticed that today you addressed the upgrade to Windows 10 in a separate message. Will the W10 OS installation have the effect of debugging my OS, only making even better? I've had some errors (Windows can't update... code: 80070003) while trying to install "optional" updates to W9.
You have a gift for clear and concise communication. Thanks again.
Despite Brink's suggestion that I didn't need to do anything about Update KB3068708, I uninstalled it along with KB3022345 (based on a tip from another WSF thread). I then ran sfc /scannow and got a clean bill of health. This morning Windows Update automatically re-installed KB3068708. Just for grins I re-ran sfc /scannow and got the dreaded "Windows Resource Protection found corrupt files but was unable to fix some of them." This time I will follows Brink's suggestion and do nothing abut Windows 7. After all, later this month we can all start a new learning curve with Windows 10. Good luck out there.
According to MS, these errors are perfectly normal, and can be ignored...
They are the result of MS not actually following their own rules, and tagging the relevant files in the update as 'static' rather than 'variable'.Code:2015-07-03 16:36:01, Info CSI 00000511 [SR] Repairing 1 components 2015-07-03 16:36:01, Info CSI 00000512 [SR] Beginning Verify and Repair transaction 2015-07-03 16:36:01, Info CSI 00000514 [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-07-03 16:36:01, Info CSI 00000516 [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 2
You can either:
1) Uninstall the related update(s) KB3068708 and KB3022345 - and then hide them to prevent reinstall before MS produce a fixed version
or
2) ignore them.
There are no other significant errors in the uploaded file.
Noel, I think your option one is the best course of action. If someone merely ignores the updates, runs SFC and gets the "Windows Resource Protection found corrupt files but was unable to fix some of them" notice, there's no easy way to know if the corrupted files are due to the updates or some other system files being corrupted.
I think Microsoft owes it to consumers who are running Windows 7 to correct this issue.
How do I find out which files are corrupt, and how to fix them?