Microsoft pulls security patch after reports of BSOD and system crashes

A recent Patch Tuesday security update has been pulled by Microsoft after receiving reports from users getting the Blue Screen of Death, after installing the update.

According to Microsoft's support website, the security update had various issues and it could cause Windows not to boot in some cases; the company has stopped distributing the update through Windows Update as well as its website.

The kernel-mode security update KB2982791 has a total of three known issues according to Microsoft's security bulletin which includes the locking down of the fonts folder in Windows, incorrect rendering of system fonts on Windows 8, 8.1, 8.1 RT and Server 2012 R2 with August update and system crashes which have been reported by users.

Microsoft has provided the steps to remove the update from the computer over at their support website and affected users should follow them if they are unable to boot to Windows successfully. The company has also provided the steps to gain access to the fonts folder which will be left locked even after removing the update manually.

Source: Microsoft Support via WindowsITPro

Report a problem with article
Previous Story

Steve Ballmer completes Microsoft CEO triumvirate's ALS Ice Bucket Challenge

Next Story

TechSpot: SanDisk Extreme Pro 480GB SSD Review

34 Comments

Commenting is disabled on this article.

Article says nothing about Windows 7.
No issues here either on 5 Windows 7 machines.

Still have this one to update and 1 other one also though.

All are some version of Windows 7. 1 Windows 7 Pro, 2 Windows 7 Ultimates, and 2 Windows 7 Home Premiums. 3 of them are 32 bit and 2 are 64bit.

@ http://support.microsoft.com/kb/2982791:
Mitigation 1b: 'If you do not have media, you should use the power button to restart your computer during the startup process three times. This should start the Windows Recovery Environment.'

Huh? What about hitting F8? Do PCs even come with recovery media these days?

How can locking down the fonts folder cause a BSOD? A serious problem there; an app crashing from not being able to access/read fonts would have made more sense.

There was recently an update that affected both my housemate's and my own computer.
Both of our systems were running 8 (He held back from 8, I was refreshing my PC).
Caused our systems to fail a system update, then just bootloop.

Problem was that if we wanted to download 8.1, we needed windows updates to get to it ^_^;

warwagon said,
Actually you just need a single prerequisite KB

Actually two.
Since when we tried auto update after a system refresh, we ended up having to refresh again.

Took a while to find the KB and download them from the website, but that's how we ended up getting it

My 2009-era 64-bit laptop had massive library conflicts with existing programs to the point of repeatedly crashing. Fortunately, I managed to uninstall about two-dozen random applications between 8 reboots over an 8-hour period... then, suddenly, the system became responsive again.

I have since removed every application that I don't use literally every day (in an "unwinding" sort of repair process) and now it's finally acting with proper stability.

(Relatedly, patching Adobe Reader and updating Adblock Plus between reboots proved to provide the stability I needed. Zero-day anybody?)

This did happen to me. No system restore, no Windows repair... nothing. It never got out of the BSOD window. I had to reformat from Windows 7, so I just went to Windows 8.1 since I was at a crossroads. I was really ######.....

That's where having a bootable USB stick with some sort of OS on it that lets you access NTFS would have saved the day. In this case, deleting the font-related file mentioned above.

Yeah, unfortunately my computer was hosed. I do have many Linux live CDs also, but I just decided to install 8.1 instead of spending hours creating a work around and fixing the problem (that wasn't known at the time of the crash). And, yeah, I was running Windows 7 Pro.

Infoworld reported that many users solved the issue by doing the following:
1) boot from an install or repair DVD
2) remove the following file c:\Windows\System32\FNTCACHE.DAT
3) reboot normally.

Good luck.

Yup, this is what worked at my workplace on various machines. It only seemed to affect machines with certain language packs installed.

My machine suffered from the BSOD problem. Luckily I was able to use system restore to revert back via the boot repair mode that automatically kicked in.

I had the same in a VM, but after backing out via a System Restore the updates took the second time. It's possible there was some other system file update that happened at the same time that it didn't like.

My brother was one of the unlucky few it appears. His computer just blue screened and he can't boot the OS now. He's a graphics designer and uses a lot of fonts so I guess the latest update didn't play nice with some of the fonts he had on his system.

Using a ton of fonts without a font manager app is asking for trouble anyway ;-P
But BSOD are no laughing matter on a work machine :-\

No issues here on 2 pc's and a tablet. Must also be in the 'safe group'.
I wonder what triggers this?

The issue is that some fonts may have a shortcut path instead of an actual file in the fonts location.

The file that needs to be delete is this one: del %windir%\system32\fntcache.dat

After that I would remove the KB2982791

The patching system needs to be completely overhauled for Windows 9. Only point updates every month instead of bits and pieces.

d5aqoëp said,
The patching system needs to be completely overhauled for Windows 9. Only point updates every month instead of bits and pieces.

Not really. Microsoft's ability to push security updates fast, realibly and selectively is one of it's strong points. If a single update causes issues in an enterprise context you're able to hold back that single update across an entire enterprise network right now.

d5aqoëp said,
The patching system needs to be completely overhauled for Windows 9. Only point updates every month instead of bits and pieces.

ever thought about this patch day stuff is causing a one month window for zero-day exploits? big business I guess

lightserver.at said,

ever thought about this patch day stuff is causing a one month window for zero-day exploits? big business I guess

They have been known to break cycle and have released patches out of cycle before.

Same, no issues but *shrug* with a gazillion possible hardware/software combinations stuff like this doesn't surprise me, impossible to cover all scenarios.