Update KB3022345 Renamed KB3068708 ??

[jds63]

Anti Virus is sometimes interfered with Windows/Apps installation and the reason I ask if any body had Office 2013 is some of its updates might conflict with these 2 Windows Updates.

@topgun,

I had disabled KIS while updating, but couldn't change anything with MS Office - SFC scan still errors out.

Should I try uninstalling it and then try installing KB3022345? This would take me to carry out

MS has clearly and repeatedly acknowledged the problems KB3022345 has caused in numerous articles including their own Data Sheet for the update so I think you can rule out conflicts with Office as well as anti-virus at least as it pertains to this particular update. Uninstalling KB3022345 if you can clearly resolves the SFC/DISM issues for most if not all although it has been reported that some have had difficulty uninstalling KB3022345. If Update Cleanup or similar cleanup tools have been applied since the installation it may not be possible to uninstall the update with traditional means without reverting to a previous restore point or earlier image.

I had no issues uninstalling it ever, it just came back as an updated important update and i did not realize it and installed it again, but removed it now along with not installing KB3068708 and all is fine with SFC and DISM. Deal with this when Windows 10 comes out, for now it is staying off as it is something i do not need anyway, being tracked and no issues without it.

 

[gator2013]

As I stated when I started this thread, I had not installed update KB3068708 because of it's similarity to KB3022345 although I kept it in my update bin just in case. Well, in preparation for Patch Tuesday (today) I manually checked for updates knowing well that any Patch Tuesday Updates will not be released for several hours and was not really surprised to see that KB3068708 is gone. I wonder if it will resurface later today in another form.
I have never been opposed to the Diagnostic Tracking just the file corruptions both KB3022345 and KB3068708 caused, or should I say false/positive file corruptions.??

 

[jds63]

As I stated when I started this thread, I had not installed update KB3068708 because of it's similarity to KB3022345 although I kept it in my update bin just in case. Well, in preparation for Patch Tuesday (today) I manually checked for updates knowing well that any Patch Tuesday Updates will not be released for several hours and was not really surprised to see that KB3068708 is gone. I wonder if it will resurface later today in another form.
I have never been opposed to the Diagnostic Tracking just the file corruptions both KB3022345 and KB3068708 caused, or should I say false/positive file corruptions.??

Yes KB3068708 resurfaced as recommended today. I was about to go over all the new updates and read about them before installing, but i was involved in something else beforehand and then later realized all important and recommended were installed asking me to restart, because i am set to install important and recommended updates automatically. So KB3068708 went in, but still do not have KB3022345 because i uninstalled it awhile ago, now they could of changed it's KB number today for all i know, because now the Diagnostics Tracking service is set to Automatic. Those who do not want this service running, set it to manual.

Well, good news is, SFC shows no integrity violations as before.Possible something was fixed through these other updates or not having other did it, i do not know for sure.

 

[rassilon]

I had previously removed KB3022345 due to SFC corruption. Unfortunately, the same errors resurfaced after installing KB3068708 yesterday. I applied the fix from The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files and SFC is now clean.

I hope I haven't caused additional problems by doing this. According to Microsoft, the two patches do the same thing, and their version of those two files is clearly broken. To quote from https://support.microsoft.com/en-us/kb/3022345

This update has been replaced by the latest update for customer experience and diagnostic telemetry that was first released on June 2, 2015. To obtain the update, see 3068708 Update for customer experience and diagnostic telemetry.​

 

[jds63]

I had previously removed KB3022345 due to SFC corruption. Unfortunately, the same errors resurfaced after installing KB3068708 yesterday. I applied the fix from The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files and SFC is now clean.

I hope I haven't caused additional problems by doing this. According to Microsoft, the two patches do the same thing, and their version of those two files is clearly broken. To quote from https://support.microsoft.com/en-us/kb/3022345

This update has been replaced by the latest update for customer experience and diagnostic telemetry that was first released on June 2, 2015. To obtain the update, see 3068708 Update for customer experience and diagnostic telemetry.​

As you know KB3022345 became a recommended update, so chances you may have reinstalled it again, after Tuesdays June 9th updates i have no issues without KB3022345 and have KB3068708 installed from June 9th also believe became recommended. Truthfully this all may get fixed if take Windows 10 in future and seems to be not tragic to have these integrity violations for now in SFC.

 

[kmdavisjr]

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

 

[jds63]

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

Your guess is as good as mine. sure be cure for it just too busy with Windows 10 maybe.

 

[popeye]

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

Your guess is as good as mine. sure be cure for it just too busy with Windows 10 maybe.

SFC and DISM are kind of for us nerds, most users don't even know about these tools. Probably low on MS list of things to fix. My opinion.

 

[gator2013]

I initially installed KB3022345 when it was first released in a batch of about 30 optional updates. About a week later I realized that SFC showed corrupted files and the DISM function was broken. At that moment I was not certain if the problem was caused by an update or something else and I did not have a restore point that corresponded well with the updates so I reverted to an image (Macrium) that was done a week or so before the large batch of optional updates and all was fine. I then proceeded to install all the optional updates again and when the next version of KB3022345 was released as Important I installed it as well. Again SFC showed corrupted files but DISM could repair but I uninstalled it again with no intention to reinstall and all was well again. When KB3068708 was released I realized it was KB3022345 repackaged and started this thread. Knowing there were at leased 4 versions of KB3022345 released and now KB3068708, 3 days ago I decided to give KB3068708 a try and after running SFC /Scannow at least twice a day for the last 3 days SFC has come back with no corrupted files. Can't explain why except maybe MS finally fixed the issue with KB3068708 at least for some systems. I am still running a SFC scan at least once daily and if it starts showing corrupted files I an ready to uninstall KB3068708 again but for now all is well.

 

[jds63]

I initially installed KB3022345 when it was first released in a batch of about 30 optional updates. About a week later I realized that SFC showed corrupted files and the DISM function was broken. At that moment I was not certain if the problem was caused by an update or something else and I did not have a restore point that corresponded well with the updates so I reverted to an image (Macrium) that was done a week or so before the large batch of optional updates and all was fine. I then proceeded to install all the optional updates again and when the next version of KB3022345 was released as Important I installed it as well. Again SFC showed corrupted files but DISM could repair but I uninstalled it again with no intention to reinstall and all was well again. When KB3068708 was released I realized it was KB3022345 repackaged and started this thread. Knowing there were at leased 4 versions of KB3022345 released and now KB3068708, 3 days ago I decided to give KB3068708 a try and after running SFC /Scannow at least twice a day for the last 3 days SFC has come back with no corrupted files. Can't explain why except maybe MS finally fixed the issue with KB3068708 at least for some systems. I am still running a SFC scan at least once daily and if it starts showing corrupted files I an ready to uninstall KB3068708 again but for now all is well.

True it seems as since i uninstalled KB3022345 it has not come back as important or recommended or even optional, you maybe right about replacing it, done same as you and all is fine with SFC and DISM. Because since installing KB3068708 Diagnostic Tracking was enabled again.

 

[jds63]

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

I uninstalled both, and hid both updates KB3022345 and KB3068708 . SFC no longer errors out. Can someone tell me what MS is thinking?

Your guess is as good as mine. sure be cure for it just too busy with Windows 10 maybe.

SFC and DISM are kind of for us nerds, most users don't even know about these tools. Probably low on MS list of things to fix. My opinion.

Calling yourself a Nerd, sir ? They didn't at first, but all of you here showed them how to use it.

 

[NourinE]

SFC error shows up and I removed KB3022345 to fix the probelem
today, I had to do the same with KB3068708 .

 

[jds63]

SFC error shows up and I removed KB3022345 to fix the probelem
today, I had to do the same with KB3068708 .

I did not have to remove KB3068708 since was redistributed on June 9th, no problems with it installed.

 

[NourinE]

today, I ran SFC and couldn't fix the corrupted files, until I removed KB3068708 !!!!!!
it's weird

 

[jds63]

today, I ran SFC and couldn't fix the corrupted files, until I removed KB3068708 !!!!!!
it's weird

Just as weird as this issue does not seem to effect everybody.......

 

[Ronster]

Here's my story...

On one computer (both Windows 8.1) I had to remove KB3022345 and KB3068708 then re-install KB3068708 and sfc was error free. On the other computer I did the same thing except I had to remove KB3068708 again and re-install it one more time.

 

[jds63]

Believe either some updates were updated again, one is a fix over the other what i felt. Seen went from optional to Recommended.

 

[glnz]

DennisCPA has a great post on this at
System Restore doesn't work Solved - Windows 7 Help Forums
Really helpful.

 

[Muttley]

This is odd. I had a problem with my laptop using 20% CPU (I did open a thread but nobody replied...maybe I chose the wrong title ). I checked my installed updates and KB3022345 was not there. Frustrated with the CPU usage I did a system restore and the CPU usage went back to around 3% - great. I checked the windows installed updates and KB3022345 was there :huh:. I uninstalled it. Maybe it had been renamed KB3068708 which was why I couldn't find it before. Anyway, everything is working fine now.