PDA

View Full Version : KB3097877 warning warning



1101
12-11-2015, 04:04 PM
KB3097877 , via winupdate .

Warning, danger danger

I just had 1 PC Ive had to use system restore to fix issues after KB3097877
There are many reports on the interwebs of KB3097877 causing Outlook issues, Publisher crashes, all-in-1's wont load win .
make sure you untick it if doing manual winupdates

A well tested patch for sure :banana

wainuitech
12-11-2015, 05:51 PM
Looks like its mostly to do with Windows 7, thats causing the problems.

http://myonlinesecurity.co.uk/kb3097877-causing-severe-difficulties-for-some-windows-7-users-november-2015-windows-updates/

AND one of the suggestions is to run a certain DISM command -- Oh yeah that will work great for an average user ;)

Guess making Patches that break W7 is one way for MS to kill it off :devil Bit like they did with XP.

paulw
12-11-2015, 06:29 PM
Thanx for the tip. I just saw it waiting and have hidden it..

mzee
12-11-2015, 10:21 PM
Turn off your updates. Seven years of updates should be ample.

Tony
13-11-2015, 10:29 AM
I got caught by this update, with Outlook crashing when opening HTML formatted emails. Fixed it by uninstalling the update. I was nervous for a while though as the uninstall required a restart and it was a looong time in the close down phase where it says "do not turn off your computer". It must have taken 20 mins to get through that bit. I actually walked away and left it to stop me succumbing to the temptation to hit rest anyway.

Speedy Gonzales
13-11-2015, 02:14 PM
This is on the flatmates PC atm. Saw it this morning. Havent hidden it yet tho

Think I'll hide it soon tho !

CYaBro
13-11-2015, 02:27 PM
Microsoft have re-released a fixed version of that update now so no need to hide it anymore, just check for updates again so your machine picks up the new version.
https://support.microsoft.com/en-us/kb/3097877

Speedy Gonzales
14-11-2015, 09:58 PM
It did install on the other PC here. Dont know how because I didnt install it. And its not on auto

I thought it was going to stuff up, because while it was booting after it said something about the registry. But it did boot into windows finally