M$ Update Screws the Pooch...again. Uninstall KB3004394 RIGHT FU@%ING NOW!!!!

[Earth Bound Misfit]

Read 'em and weep:

https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/windows-update-kb3004394-issues/ace25277-7f65-4486-bc44-c1b106907a18
http://www.allwebsolutions.net/science-technology/operating-systems/botched-kb-3004394-triggers-error-messages-but-no-response-from-microsoft/
http://www.infoworld.com/article/2858014/operating-systems/botched-kb-3004394-triggers-uacs-diagnostic-tool-error-0x8000706f7-amd-catalyst-driver-fail-defende.html
http://www.sevenforums.com/performance-maintenance/354850-sfc-found-corrupt-files-after-windows-update-never-had-any-before-2.html
http://www.sevenforums.com/general-discussion/354776-windows-diagnostic-tool-error-0x800706f7.html
http://www.wincert.net/forum/topic/12103-update-list-gdr-pour-windows-7-sp1-x86x64-fr-en-de-es-it-30-novembre-2014/?p=113069

SMH...

[hobbit709]

1. One of the reasons I set update to "Notify but don't download automatically"

[Earth Bound Misfit]

2. Same here.

I installed the update but as is my custom after each patch Tuesday I ran sfc /scannow to make sure WinDOZE Update didn't break shit. Sure enough I found that WinDOZE Update broke shit.



After some Googling found KB3004394 was the culprit. Solution? Uninstall the fu*ker & hide it.

[ManiacJoe]

4. I get the notifications on Tue/Wed. Wait until Sat to do the installs.

For just such an event....

After waiting, as of now the offending update is no longer available for installation.

[Earth Bound Misfit]

3. FUBAR update applies to Win 7 only, Win 8/8.1/Server 2012 OK

Micro$lop has pulled the update for Win 7 from it's servers, apparently some genius @ M$ forgot to provide for the inclusion of a catalog file-- kinda important to include, ya think?

https://www.virtualbox.org/ticket/13677

From what I can tell, the KB3004394 update does not install a catalog file on 64-bit windows 7. It does on Windows 8.1 (C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1_for_KB3004394~31bf3856ad364e35~amd64~~6.3.1.0.cat), so VBox works fine there.

The result of the missing .cat file is that VBox (nor SysInternal's SigCheck.exe for that matter) is not able to verify the authenticity of c:\windows\system32\crypt32.dll and wintrust.dll. If we cannot find any valid signature for the files, we have to assume that they have been tampered with and are forced to abort application loading. These two dlls are important for validating other components, so there is absolutely no way we can ignore this.

Until Microsoft fixes the KB3004394 update on Windows 7, the only solution is to revert/uninstall it.

[mythology]

5. Every OS will sometimes have an update that goes wrong

Apple has had several recently that turn iPhones into bricks. Ubuntu has been known to crash while updating. It's nothing to run around like your hair is on fire.

[hobbit709]

6. But Micro$haft seems to have more than its share.

[Earth Bound Misfit]

7. M$ updates problems recently...

This is not a comprehensive list:

May: http://www.infoworld.com/article/2608134/microsoft-windows/the-new-kb-2919355-windows-8-1-update-causes-more-problems-than-it-fixes.html

August: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/ms-august-update-fubaruninstall-bad-patches/4e59be50-1936-4b40-90f4-742d90acabf3

October http://www.infoworld.com/article/2834535/security/four-more-botched-black-tuesday-patches-kb-3000061-kb-2984972-kb-2949927-and-kb-2995388.html

November: http://www.securityweek.com/microsoft-warns-issues-recent-schannel-update-patch-away

December: http://arstechnica.com/information-technology/2014/12/microsoft-withdraws-bad-windows-7-update-that-broke-future-windows-7-updates/

[Denzil_DC]

8. Upgrade to Windows XP!

No more glitchy/disastrous updates ...