PC World reports that Microsoft has identified three key problems with the update:
“First, fonts that are installed in a location other than the default fonts directory (%windir%fonts) cannot be changed when they are loaded into any active session, essentially locking them in. Second, fonts don’t render correctly. The third issue is the most critical, however… that systems may crash with a ‘0x50 Stop error message’ after the updates are installed.” It appears the problem will apply to the following programs: Windows 7, Windows 8, and Windows 8.1, plus Windows Vista and Windows Server 2003.
If you’re one of the unfortunates who has downloaded the updates already, don’t panic. There is a solution, which is detailed in the security bulletin by Microsoft. You’ll need to fiddle with the registry files, then enter the recovery environment to delete the .dat file, reboot and then export the file. This will then need to be repeated before you uninstall the update and reimport the font file. It may sound complex but follow Microsoft’s bulletin and you’ll be on the right track.
It’s not the first lot of issues Microsoft has had to deal with this month. On Friday they had to issue a hotfix for Internet Explorer after multiple dialog windows began causing halts and delays. This applied to all versions of Explorer and garnered many user complaints.
The problem with the latest update is yet to be found, but it has notably coincided with Microsoft’s move towards using Patch Tuesday to combine small feature updates into the Windows monthly security update package. This is instead waiting awhile (until a bundle of new features are ready) and then releasing them together in one major update like Windows 8.1.
Whatever the cause, users aren’t happy and Microsoft may need to rethink their update protocol before impatient users start to rethink their loyalty to the brand.
(Photo courtesy of wolfram_schmied)