Correct. You can uninstall the update. There is no way to permanently resolve the corruption until Microsoft fixes. It only resolves temporarily by following the instructions you pointed out above. I've never heard of this update messing with File Explorer so if you find that it does I would love to hear.
Thanks.
Hi BrianDrab,
Maybe it was too much to hope for but at
Page not found I read:
“After installation of the updated patch [May 6,
KB 3022345], I experienced explorer.exe crashes (once after installing the patch and once today) which I had never experienced before.
.......I also know that this patch may not uninstall properly (at least on Windows 8).......”
“Had explorer crash again today so I decided to take a chance and uninstall KB3022345 on one of my other Win 7 Ultimate machines (this machine also manifested unrepairable SFC errors due to the May 5 issued KB3022345).
Uninstall results in the following:
1) Removes "Diagnostics Tracking Service."
2) Cold boots without issue. No errors/warnings in the event viewer.
3) SFC now reports "Windows Resource Protection did not find any integrity violations."
4) KB 3022345 reappears in the update chute.
It appears the uninstall was successful and resolved SFC corruption errors.
I've since received independent confirmation about this behavior from many sources, including reader Canadiantech, who apparently is working with version 4.”
Well, I uninstalled KB3022345 as planned and when I hid KB3022345 from the “update chute”, it went one better and immediately disappeared. Even checking for updates has not located it. Given the way MS has tried to foist the Windows 10 Upgrade upon users, I suspect the disappearance has to do with what I suspect is their strong intent to load literal tracking software onto all Windows machines. As far as productivity is concerned, “updating” from XP to 8.1 this year has been a right royal disaster. Never again will I accept anything on face value that is issued under the MS brand, but I digress....
I then found that my File explorer folder behavior errors were still there. However, re-running sfc.exe detects the same 8 errors relating to KB3022345 so it appears not to have uninstalled properly. In case you should want to check, the latest CBS.txt file is attached.
From what I can see, short of a system refresh or worse, a reset, the remaining options are to:
- Fully uninstall update KB3022345 (and never install it again) or,
- Find and fix the cause of the file explorer error or,
- Roll the registery back to a point prior to both the start file explorer error and the KB3022345 install.
Given the scarcity of material on the internet for fixing the Error 0x80004005, unless you have some thoughts on either options 1 or 2, is option 3 a goer? I presume that if it fixes the explorer issue, it will necessitate running sfc.exe again just to be sure.
Sorry to be a pain.
Ronnz
