I have run into this exact issue this week; just passing along in case anyone else finds useful.
From LinkedIn:
From LinkedIn:
Windows 7 update (KB3022345) causing corrupt files
To all, Windows 7 update (KB3022345) causing corrupt files Sometimes, even us techies get frustrated when we can’t figure out how to fix a problem right away. I can be obstinate, and don’t want to give up on a problem, at least computer related. I was having a problem with corrupted system files and was researching a solution to my SFC (system file checker) utility reporting that it could not fix some of the errors, and found this website after searching for the following details in my error log: Microsoft-Windows-Unified-Telemetry-Client errors in sfc /scannow
And found these links: http://www.bleepingcomputer.com/forums/t/575721/some-files-cannot-be-repaired/
and then: http://thetechcookbook.com/windows-7-update-kb3022345-causing-corrupt-files/
I got this search term from the file I created named sfcdetails.txt by entering the command: findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt" in an elevated command prompt. I found this command at: https://support.microsoft.com/en-us/kb/929833#CBS log (yes, there is a space between CBS and log) Anyway, it blames “Windows 7 update (KB3022345) causing corrupt files”, and tells you to download a script and scripting tool and run it. I was wary at first, so I made a system restore point and backed up my registry, then threw caution to the wind and gave it a whirl. The script ran without errors, I rebooted, I did not notice any instability or anything worse for wear, and ran sfc /scannow again. It completed without any errors! I had a huge smile on my face, not only because it was fixed, but because I was able to find the answer through more thorough research efforts (and a little luck, I suppose). I just wanted to share this info about KB3022345 update and let you know that you don’t have to reload your OS and restore your backup, do updates, reinstall all your programs, secure and optimize your system to fix this problem. I have overwhelmed anyone with all this technical detail, I apologize. Suffice it to say that I am doomed to have to continue learning until the day I die, and I try and learn something new every day. Just wanted to let you all know I did not pull all my remaining hairs out of my head on this one, I still have a few left!
Update: The story at the following link indicates that Microsoft caused the problem from the beginning. It would not be the first time that a Microsoft update was faulty and/or needed to be pulled. Microsoft unfortunately has a bad history releasing updates before they are fully tested.
http://www.infoworld.com/article/29...le-corruption-which-sfc-is-unable-to-fix.html Also read this one:" http://www.infoworld.com/article/2930713/microsoft-windows/microsoft-re-re-releases-kb-2952664-kb-2976978-and-kb-2977759.html
To all, Windows 7 update (KB3022345) causing corrupt files Sometimes, even us techies get frustrated when we can’t figure out how to fix a problem right away. I can be obstinate, and don’t want to give up on a problem, at least computer related. I was having a problem with corrupted system files and was researching a solution to my SFC (system file checker) utility reporting that it could not fix some of the errors, and found this website after searching for the following details in my error log: Microsoft-Windows-Unified-Telemetry-Client errors in sfc /scannow
And found these links: http://www.bleepingcomputer.com/forums/t/575721/some-files-cannot-be-repaired/
and then: http://thetechcookbook.com/windows-7-update-kb3022345-causing-corrupt-files/
I got this search term from the file I created named sfcdetails.txt by entering the command: findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt" in an elevated command prompt. I found this command at: https://support.microsoft.com/en-us/kb/929833#CBS log (yes, there is a space between CBS and log) Anyway, it blames “Windows 7 update (KB3022345) causing corrupt files”, and tells you to download a script and scripting tool and run it. I was wary at first, so I made a system restore point and backed up my registry, then threw caution to the wind and gave it a whirl. The script ran without errors, I rebooted, I did not notice any instability or anything worse for wear, and ran sfc /scannow again. It completed without any errors! I had a huge smile on my face, not only because it was fixed, but because I was able to find the answer through more thorough research efforts (and a little luck, I suppose). I just wanted to share this info about KB3022345 update and let you know that you don’t have to reload your OS and restore your backup, do updates, reinstall all your programs, secure and optimize your system to fix this problem. I have overwhelmed anyone with all this technical detail, I apologize. Suffice it to say that I am doomed to have to continue learning until the day I die, and I try and learn something new every day. Just wanted to let you all know I did not pull all my remaining hairs out of my head on this one, I still have a few left!
Update: The story at the following link indicates that Microsoft caused the problem from the beginning. It would not be the first time that a Microsoft update was faulty and/or needed to be pulled. Microsoft unfortunately has a bad history releasing updates before they are fully tested.
http://www.infoworld.com/article/29...le-corruption-which-sfc-is-unable-to-fix.html Also read this one:" http://www.infoworld.com/article/2930713/microsoft-windows/microsoft-re-re-releases-kb-2952664-kb-2976978-and-kb-2977759.html
