Microsoft pulls botched patch KB 3114409 that triggered forced Safe Mode problems with Outlook 2010

Topic

New Reply

The easiest way to fix the problem is to uninstall the bad patch. InfoWorld Woody on Windows UPDATE: If you don’t see any problems with Outlook 2010 o
[See the full post at: Microsoft pulls botched patch KB 3114409 that triggered forced Safe Mode problems with Outlook 2010]

Reply | Quote

Replies

How did this patch get through QA at MS?

If the KB had produced a set of random problems that only a few users were experiencing I could accept that it had nothing to do with a questionable QA process, but that is not the case.

What I expect is that the set of test scenarios that they use covers a wide range of usage and maybe they encountered a few problems but decided that it would be minimal and therefore could be managed on an individual basis. It appears that whoever was tasked with that call is now regretting it.

This KB is doing the opposite to what it was intended to do and needs to be withdrawn. I expect we will eventually see this happen.

Reply | Quote

They finally pulled it around midnight last night. No word on if it’s been fixed and re-released.

Reply | Quote

Further evidence if any was needed as to why we shouldn’t use automatic installation of updates or install them manually the minute we are offered them!

It’s also further evidence if any was needed as to why forced updates with Windows 10 are a bad idea!

Reply | Quote

I’ve been looking around the Internet and you are the only one that picked up on this that I’ve seen. Good job!!! Keep on helping the rest of us.
I passed it on to my small “circle of responsibility” – hope it helped.
Seen lots of articles on the boat load of security patches/bulletins, though.

Reply | Quote

Spread the word – and encourage folks to watch here, subscribe to @askwoody on Twitter, or head to InfoWorld.com from time to time. I get a lot of email questions from people who haven’t been watching. Painful.

Reply | Quote

Hey everyone.

Don’t use the wusa command to remove the update as that doesn’t set it back to not safe mode.

My outlook is now stuck in safe mode and I have to wait for them to fix that as well.

Reply | Quote

I really don’t think it has been pulled though, it’s been forcing safe mode on our work machines and after uninstalling is still being offered. Pain in the ass.

Reply | Quote

It was taken down from WSUS (although it may be back again). I’ve seen multiple reports, though, that it’s being reinstalled. Odd.

Reply | Quote

Yup, was uninstalled on a lot of users yesterday and still getting calls today from people we fixed yesterday. Unbelievable.

Reply | Quote

Windows update feels completely broken since windows 10 rolled out. Whether it’s waiting an eternity for a new updates check to find anything or trying and failing to download updates on a new installation 2 days straight with it stuck on 0%. Whether it’s intentional or not, but i wouldn’t put it past microsoft to subtly cripple it to make 10 look a more attractive proposition.

Reply | Quote

Windows Update’s primary mission used to be security and stability improvements, with a few enhancements thrown in for lagniappe.

Now its primary mission is security patching and advertising for Microsoft.

Reply | Quote

Yikes. I used the wusa command on one machine and am in the exact same situation. Did you get a resolution yet?

Reply | Quote