What’s up with botched security patch fixes KB 3186987 and 3187022?

Topic

New Reply

If this is the way we’re going to get cumulative update fixes, we’re in a world of hurt. InfoWorld Woody on Windows  
[See the full post at: What’s up with botched security patch fixes KB 3186987 and 3187022?]

Reply | Quote

Replies

This is WHY I turned off the update function on my computer. I no longer want Microsoft screwing up my computer.

Reply | Quote

This has gone way beyond a joke now. Allow a few months grace to work out some bugs maybe, but its now almost a year, and Win 10 [and Microsoft too] is still dysfunctional.
Very surprised that some enterprising law firm isn’t actively promoting a class action against MS forcing this YUGO on people.

Reply | Quote

MS has certainly turned itself into a real patching/updating “drama queen” over the last year. It makes me wonder how long it will take for personnel changes to occur in Redmond?

Reply | Quote

+1

Reply | Quote

Ran the Canadian Tech’s cure and it worked. Made my whole system faster with updates taking 3 min. to get. I put most in my tube file. If they meet muster I fire them into the system, if not I fire them into the toilet. I did the prescribed , windows control module “stop” but it stayed in automatic. The windows update module was also put on “stop” but it stayed on manual: then I did the rest by the book. I guess it is the difference in windows builds. Thanks Woody

Reply | Quote

Our WU for Windows 7 machines has been switched off since MS announced the roll-up patches.
BIG thanks to AskWoody and Infoworld on the heads-up.

Reply | Quote

Interesting that KB3187022 is only available via the Microsoft Update Catalog even though it was released five days ago on August 29. It makes me think it’s a BETA patch and M$ wants a few guinea pigs to download and test it before they release it to the masses.

As for the two Microsoft employees disagreeing with each other over a post by Kristan G on the answers.microsoft.com site – I read your Infoworld article Woody – I think the first one belongs to the bunch of copy/paste artists who work for Microsoft’s call center in Bangalore, India since the ones who contribute regularly on that forum all have Indian names.

The second one, DanMattson is someone higher up the food chain and even though he’s been a forum member since 2012 according to his stats, he’s only ever posted 10 times on two threads both of which relate to this printing issue.

It becomes even more bizarre on the other thread he contributed to where another Microsoft forum moderator called Jamille Nar recommended that the user skip installing KB3177725 if it caused printing problems. Since 72 users marked that answer as helpful I guess a few people are exposing their systems to attack now.

Reply | Quote

Fascinating. Ya gotta wonder what’s going on in Redmond…

Reply | Quote

Conway’s Law?

https://en.wikipedia.org/wiki/Conway%27s_law

JF

Reply | Quote

Win10 version 1511 and 1607 did not get the printing fix yet
Win10 RTM version took precedence this time 😀

Reply | Quote

It’s strange. Version “1507” got the fix – a cumulative update, no less – but the cumulative update hasn’t been rolled out.

14393 has a new Preview build 14393.103, but it’s been out for four days, and I haven’t seen any mention of it sliding down the Windows Update shoot.

Reply | Quote

Interesting!

Reply | Quote

The cumulative update took KB3187022 route, catalog only
maybe because the fix is not broadly verified/tested, thus not convenient for mass release

according to Powershell issue blog post, we should see public cumulative for 1607 tomorrow

Reply | Quote

I’m sure there’s a Rube Goldberg machine which captures M$FT internal communications perfectly.

Reply | Quote

I hope the personnel changes happen soon and start with SatNad.

Such incompetence do you s’pose he’s “Shorting” the stock?

Reply | Quote

I think Nadella’s doing an excellent job, at his primary jobs.

Reply | Quote

Just to let you know Woody, you’ve popped down MS16-089 at the start of the article but I think you might mean MS16-098 as you’ve linked to it!

Reply | Quote

Ooops. Thanks!

Reply | Quote

KB3177725 still on WU as of yesterday 8/29

Reply | Quote

I’m guessing MS will release KB3187022 to Windows Update today, and probably give us a new 14393.103 for Win10 Anniversary Update, both of which fix the bug in the earlier security patch.

But it’s only a guess.

Reply | Quote

The MS patches on patches methodology always strikes me as an inelegant approach to fixing known issues. I think it would be preferable to reissue an updated KB3177725 with the printing issue resolved. But alas no, let’s install a patch with issues and then patch over it.

Reply | Quote

It would be a step up from the carrier pigeons they use now.

Reply | Quote

Dear Woody,

First, thank you for being here for so many of us with basic to advanced levels of computer knowledge. I, like many, read your articles and Ask Woody just to know how to proceed and survive the MS terrorism.

I have said before I am just a user. Not a computer expert, but I, like many depend on my only computer to work.

I feel terrorized at least once a month by MS updates. I don’t appreciate being a beta tester at my expense for them. There is never a good time to be without a computer, or to be down for a day or more. The issues with last month’s Anniversary Update just seem a gamble if one moves forward with it, and we are now fast approaching another black Tuesday.

It would be nice if MS would just give us a breather, instead of creating more problems for us.

Will you be giving us a go-ahead to install the dreaded Anniversary Update before next Tuesday, or can we just do the previous build updates and continue to put the AU update off?

I did not have my Win 10 (Home)when the fall update rolled out. How long does the AU take to download, and if necessary is it easy to rollback if one is a mere person?

Tuesday the 6th is a week away and I am already stressing-out again.

Thank you!

Reply | Quote

No need to stress out. I’m going to look hard at what comes out today (if anything) and try to give an update on the MS-DEFCON rating later this week.

It’s highly unlikely that MS will solve enough of the Anniversary Update problems in the next few days to warrant a go-ahead. If you’re waiting for your Win10 Fall Update machine to move itself to the Anniversary Update, you may have quite a while to wait. I have a feeling Microsoft’s slowed down the marched upgrade. There’s a reason why, no doubt. They can roll out bits at a furious pace, but they’re taking this one easy.

Reply | Quote

Win10 version 1511 fix is up KB3186988
seems catalog-only as well

Reply | Quote

Vista & Server 2008 got KB3187022 too
catalog-only

Reply | Quote

This does fix the problem for 1511. Any idea on a fix for 1607? KB3176936 released 8/30 did not contain a fix.

Reply | Quote

Was KB3176936 – the Servicing Stack update for 1607 – re-released on Aug 30? I see the initial release on Aug 23, but nothing since then.

Reply | Quote

And for people running WSUS, there still is no post-KB3177725 fix… So time to hold off this one yet further. THIS is what causes fragmentation, Microsoft!

Reply | Quote

KB3187022 article is updated to explicitly state that the printing fix is indeed included in KB3185911
https://support.microsoft.com/en-us/kb/3187022

Note: This problem is resolved in Microsoft Security Bulletin MS16-106

Reply | Quote

Just saw that on your patchmanagement message. I’ve relayed it to the folks at Seagull Scientific. Thanks!

Reply | Quote

What happens if you were not offered KB3185911 on September 13?

In addition, we looked at the MS16-106 and from what we can tell it indicates it is KB3185848 is the Kb for that MS16-106. We are confused.

The only Win 10 build 1511 updates offered to us on Sept. 13 were KB3185614, KB3161102 and KB3181403.

We don’t know if we have the print problem because we only print single documents.

We did install all the August updates for Win 10 version 1511 recommended by you. Isn’t it likely that we have the bug?

Is the bug Win 10 version specific, or is it also related to the printer installed?

Reply | Quote