KB2982791, KB2970228, KB2975719, and KB2975331 updates, which were all released last week as part of Patch Tuesday, are causing a number of issues on Windows 7 computers, including BSODs at first boot.While Microsoft has already confirmed that it’s working on a fix, the company has also rolled out a workaround to help users deal with issues caused by the aforementioned updates.
This workaround is aimed at computers running Windows 7, Windows 8, and 8.1 and must be completed in the exact same ordered as mentioned below.
Step 1: Boot from a Windows installation disc or access the Recovery Mode if that’s possible.
Accessing Safe Mode also helps, but keep in mind that administrator privileges are needed.
Step 2: Delete the fntcache.dat file that’s included in the system32 folder in root Windows folder. Since it's located in the main Windows folder, administrator rights are mandatory. Otherwise, you won't be able to delete the file.
If you use the Recovery Mode console, here’s the command that you need to use:
Step 3: Reboot your computer and everything should be working just fine (but you’re not done yet)/
Step 4: Access the registry editor by typing “regedit” in the run dialog or on the Start screen and navigate to the following path:
Step 5: Right click the “Fonts” subkey and hit “Export.” Save the file on the desktop with any name you want.
Step 6: Search the registry and remove all values under the “Fonts” subkey that end in an .oft extension and contain a full file path.
Step 7: Delete the fntcache.dat one more time (you don’t need to boot to Safe Mode to do this and the location is the same as mentioned above). The same command can be used when launching a Command Prompt window with administrator privileges.
Step 8: Go over to Control Panel, open Programs and Features, and click on “View installed updates.” Find and uninstall the following entries: KB2982791, KB2970228, KB2975719, and KB2975331.
Step 9: Restore the registry key that you exported earlier to the desktop.
Step 10: Reboot your computer and you should be ready to go.
Remember that this is just a temporary workaround until Microsoft releases a fix, but at least it’s a way to get back into Windows when experiencing BSODs at first boot.
The company has already confirmed that a fix is being developed right now, but it could obviously take a while until it’s being released to users. Of course, if you’re getting BSODs at boot this is pretty much your only option, so give it a try and let us know if it works in the comment box after the jump.