Microsoft surreptitiously reissues botched patch KB 3097877 for Window

[Borg 386]

As best I can tell, around 1:30 a.m. Redmond time on Thursday, Nov. 12, Microsoft re-released KB 3097877 -- the horribly messed-up security patch I talked about yesterday that freezes Outlook, blocks network logons, crashes the Asus DX Xonar driver, and kills Win7 sidebar gadgets and SolidWorks, among others.

I've seen no other official description of the problem or its solution. The master list of Windows updates doesn't list a re-release. Several TechNet threads mention a second version of KB 3097877, but I haven't seen any official confirmation or description. It's mushroom patch management time.

It's also not clear why Microsoft re-released the patch with the same KB number as the bad patch. That's going to make life difficult for some admins. For those who hang their tails out in the breeze and turn on Windows Automatic Update, though, it means that a run through Windows Update will solve the old problems, and you're not likely to notice that anything's been updated.

Microsoft surreptitiously reissues botched patch KB 3097877 for Windows 7 | InfoWorld

 

[UsernameIssues]

The re-issued patch actually came out on the 11th of Nov. (See this post). I was offered the patch around 9pm Redmond time on the 11th. The Windows Update interface showed that it was published on 12 Nov (which had not even happened yet for me or Redmond). Not that any of that really matters - it was just an observation.

 

[Borg 386]

I thought it must have come out overnight as some of the PC's at my Wife's work were in chaos Wed & on Thurs some of them were doing installations of patches.

So this little debacle is yet another perfect example of why MS should NOT force updates on people & give users a choice of when/what to apply.

 

[DavidE]

I've seen no other official description of the problem or its solution. The master list of Windows updates doesn't list a re-release. Several TechNet threads mention a second version of KB 3097877, but I haven't seen any official confirmation or description. It's mushroom patch management time.

When i click on the "More Info" link for this KB, i get to a MS page with the screen print below.
It does mention a re-release, but it's buried and might not be seen with a quick glance.

Source for screen print: https://support.microsoft.com/en-us/kb/3097877

 

[UsernameIssues]

If MS gets all of the W10 telemetry that they seem to want, then perhaps they could issue patches for W10 that won't brick it. I could see how it would be helpful to know every app that is installed on every computer that is to be patched.

 

[UsernameIssues]

I've seen no other official description of the problem or its solution. The master list of Windows updates doesn't list a re-release. Several TechNet threads mention a second version of KB 3097877, but I haven't seen any official confirmation or description. It's mushroom patch management time.

When i click on the "More Info" link for this KB, i get to a MS page with the screen print below.
It does mention a re-release, but it's buried and might not be seen with a quick glance.

Source for screen print: https://support.microsoft.com/en-us/kb/3097877

View attachment 375865

There have been 8 versions of the info in that link. There is no telling what the article looked like when the InfoWorld article was published. But technet had the info pretty early. See replies in this thread: http://www.sevenforums.com/windows-updates-activation/385548-kb3097877-re-issued.html

 

[DavidE]

Does that mean there are/were 8 versions/releases of KB 30897877 ?

I only posted to show the "More Info" MS link did state this KB was re-released.

 

[jonnyhillow]

I have this update installed so i guess not all systems suffer from the issues others are experiencing , knock wood.

 

[Brds7t7]

I have this update installed so i guess not all systems suffer from the issues others are experiencing , knock wood.

I didn't have any issues with the first update, I then received the same update reissued the next day.
Luckily none of my PC's seemed affected by the first one. Seems to have caused a lot of different issues for others though.