Microsoft Pulls KB2982791 After 4 Days of Blue Screens

Reports of blue-screening systems started almost immediately after Microsoft released its updates for August. Though some were not affected by the issue, those that were spent a lot of time this past week trying to source the exact problem and come up with workarounds.

Late on Friday, Microsoft finally acknowledged the problem, updated the security bulletin to confirm, and removed update KB2982791.

Microsoft recommends that customers uninstall this update.

http://windowsitpro.com/windows/microsoft-pulls-kb298271-after-4-days-blue-screens

Hello hazelnut - Thank you for finding this. I did experience a BSOD on my HP laptop about an hour after applying the last round of updates. Something to do with "IRQL_NOT_LESS_OR_EQUAL". Since it was the very first BSOD I have had with this machine, I had a feeling that the updates had something to do with it. I did do several Google searches trying to figure what happened, but I guess it was too soon to find any results. The next time I boot that machine, I'll uninstall update KB2982791. Thanks again - Derek.

thanks for the heads-up, it made me look at my updates, saw it there and although no blue screens, I pulled it anyway.

I just checked and I do have it downloaded. I haven't had any BSODs or any weirdness. I'll uninstall it anyway just to be safe (after a Sys Restore).

You might need to uninstall more updates as Microsoft has removed the download links to these updates while these issues are being investigated.

http://support.microsoft.com/kb/2982791

Microsoft is investigating behavior in which fonts do not render correctly after any of the following updates are installed:

2982791 MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014

2970228 Update to support the new currency symbol for the Russian ruble in Windows

2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

2975331 August 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012

Microsoft is investigating behavior in which systems may crash with a 0x50 Stop error message (bugcheck) after any of the following updates are installed:

2982791 MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014

2970228 Update to support the new currency symbol for the Russian ruble in Windows

2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

2975331 August 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012

I got a BSOD a half hour ago, so I just also uninstalled 2970228 (after creating yet another Sys Restore point). :blink:

Never had a problem with this update on my Win 7 system. But I removed it anyway. Just in case. Did the BSODs show up in Win 8 only ?

Now I understand why some (security) updates aren't available (anymore) on the MS website. I have downloaded every Win 7 update and I intend to slipstream all the updates. (Haven't found the time to actually do it yet).

I have Win 7. None of the Win 8 updates downloaded into my PC.

I read the MS Support page and I have a question - after the "Known Issues" section, there is a 12-step "Mitigations" section. Is it necessary to go through those steps in addition to uninstalling the listed updates? If yes, does it matter which is done 1st - uninstall then mitigation, or, mitigation then uninstall?

(thank you MS) :angry:

Neither of my Win7 PCs have had a BSOD since installing the updates, but still...

I don't think it's necessary Nikki to do the 12 steps unless you have the 'real issues'' in starting the machine due to the updates.

Uninstalling should be enough for most folk.

Uninstalling should be enough for most folk.

It should do a rollback to the previous version. Hopefully it uninstalls correctly for those affected, I've read about horror stories in the past about some rollbacks failing from botched updates.

OK, thanks. I've got 2 Win7Pro x64 PCs, both with KB2982791 & KB2970228 installed. I'll uninstall both updates on both machines and see what happens. [crossed fingers] ;)

Done. No problems uninstalling both updates from both PCs. Now I'll just watch & wait.

I guess most of us are playing safe, but really, if we weren't getting any BSoD's we could have just left everything as it was.

I'm leaving mine at just pulling the original KB update and see how it goes.

I guess most of us are playing safe, but really, if we weren't getting any BSoD's we could have just left everything as it was.

I'm leaving mine at just pulling the original KB update and see how it goes.

That's right mta, uninstalling is enough for the majority of us. Those other measures are only required if you have problems with those updates after installing them.

So, I have two Win 7 64 bit machines, desktop and laptop with these updates and no problems. Should I leave as is or remove the update?

theoretically you could argue - no problems now, no problems later.

like most of us here, I only pulled the update to be on the overly-cautious side.

if it ain't broke, don't touch it.

you can always pull it at any time down the track if you do start getting BSoD's.

the decision is yours...

If the update is defective and causes instant BSOD's etc on some systems,

can you be confident that this defective update is PERFECTLY providing the intended benefits on the the systems which still APPEAR to work ?

QUESTION :-

If this defective update is retained, and after subsequent Patch Tuesday updates a problem does arise,

will it be more difficult to uninstall this defective update.

I was only one of many XP user victims of the Microsoft Fiasco called Net Framework,

which is effectively a high rise tower of wooden sheds built on-top of one another,

and an "urgently needed security update" could not be installed in Net Framework 2.0 because of problems in the foundations of either 1.1 or 1.0.

Unfortunately the only solution for was was to total uninstall 2.0 then 1.1 then 1.0.

Many of us were even more unfortunate - the operating system had lost the manifests which told it the precise stages of un-installation,

and my only solution was to restore the partition image backup which I had created before the failed attempt of that "urgently needed security update".

An ingrowing toenail does not hurt you until it gets established and cause inflammation to grow over it.

Do not wait for gangrene to set in and then have a surgeon remove the leg :o

Thanks for the advice, I think I'll uninstall these and see what happens.

It's been 2 days since I uninstalled both updates from 2 Win7 machines and so far, no problems.

I hadn't experienced any BSOD's or other problems after initially installing the updates, so I was just being overly cautious by removing them.