Bad Update: KB3114409 - breaks Outlook
-
Spent this morning chasing around removing this. It causes outlook to start in safemode and screws with your view prefs.
Recommended action: blacklist it on your WSUS.
MS has already pulled it.
-
Thanks
Toasted it before it could spread. -
Just got my first call about it
Looks like someone's PC was pretty keen to update. -
Damnit... Hope it gets pulled from my wsus...
-
At least I know about it for tomorrow.
-
Don't worry there is a patch for that... it's called OWA.
-
-
@scottalanmiller said:
Don't worry there is a patch for that... it's called OWA.
That's a work around
-
Welp, no luck... the update was pushed out.. and while Outlook is 'working' it's in safe mode as mentioned.
-
@nadnerB said:
@scottalanmiller said:
Don't worry there is a patch for that... it's called OWA.
That's a work around
That's like saying a bridge over a river is a work around.
-
@scottalanmiller said:
@nadnerB said:
@scottalanmiller said:
Don't worry there is a patch for that... it's called OWA.
That's a work around
That's like saying a bridge over a river is a work around.
Well... Tehcnically it is. It's a workaround for you having to wade across the river, or go 50 miles upriver to find a place that is shallow enough to cross.
-
Technically OWA isn't the workaround, that's the river itself. Outlook is actually the workaround.
-
@scottalanmiller said:
@nadnerB said:
@scottalanmiller said:
Don't worry there is a patch for that... it's called OWA.
That's a work around
That's like saying a bridge over a river is a work around.
I disagree with your example.
In that frame of mind, anything that assists you in crossing the river is a work around (as opposed to a walk around :P)
The suggestion of OWA, in this case, instead of fixing Outlook is the work around. Not OWA itself.
However, if your suggestion was to remove Outlook from ALL PC's, and use OWA, then it becomes an alternative solution.
I'm not exactly sure which one you meant, so I won't go poking holes in ideas
-
This doesn't appear to have affected Outlook 2013 / 2016.
-
@DustinB3403 said:
This doesn't appear to have affected Outlook 2013 / 2016.
Because it's specifically for Outlook 2010...
-
@DustinB3403 said:
@DustinB3403 said:
This doesn't appear to have affected Outlook 2013 / 2016.
Because it's specifically for Outlook 2010...
yeah that was the first thing I noticed - my machine, 2016, wasn't affected.
-
@nadnerB said:
@scottalanmiller said:
@nadnerB said:
@scottalanmiller said:
Don't worry there is a patch for that... it's called OWA.
That's a work around
That's like saying a bridge over a river is a work around.
I disagree with your example.
In that frame of mind, anything that assists you in crossing the river is a work around (as opposed to a walk around :P)
The suggestion of OWA, in this case, instead of fixing Outlook is the work around. Not OWA itself.
However, if your suggestion was to remove Outlook from ALL PC's, and use OWA, then it becomes an alternative solution.
I'm not exactly sure which one you meant, so I won't go poking holes in ideas
Outlook is a workaround to just crossing the river - using Exchange as is. OWA isn't an alternative add on, it's the native solution. It's like a river you can just walk through. Outlook is a workaround to the provided, intrinsic option. OWA and Outlook are not peers. One is part of the product, one is an additional, extra work around. Unlike most workarounds, though, it isn't superior to the actual use case.
-
@DustinB3403 said:
@DustinB3403 said:
This doesn't appear to have affected Outlook 2013 / 2016.
Because it's specifically for Outlook 2010...
No serious environments affected then
That's six years old! -
@scottalanmiller said:
@DustinB3403 said:
@DustinB3403 said:
This doesn't appear to have affected Outlook 2013 / 2016.
Because it's specifically for Outlook 2010...
No serious environments affected then
That's six years old!I love statements like this. Are you telling me that no fortune 500 is running Windows 7 with Office 2010?
-
@Dashrender said:
@scottalanmiller said:
@DustinB3403 said:
@DustinB3403 said:
This doesn't appear to have affected Outlook 2013 / 2016.
Because it's specifically for Outlook 2010...
No serious environments affected then
That's six years old!I love statements like this. Are you telling me that no fortune 500 is running Windows 7 with Office 2010?
No, I'm telling you none that are taking it seriously.
