

What’s more, Word was suspiciously trying to open this file over and over while I was waiting for the font drop-down to open: Of course, the server path wasn’t actually called old-serv, but it was the name of a server I’d retired over the summer that used to hold user data such as their redirected AppData directory. Specifically, Process Monitor.Īfter logging the incident a couple of times, something immediately leapt out at me. This time, I discovered that the problem followed the user around to different machines, something I hadn’t checked with the first user since they always used the same machine. Since the user was not overly troubled by the problem (and has one of the few workstations in the school with applications that are tricky to reinstall), I resolved to rebuild the machine when I had time.īefore that happened, I got another report. No joy there, so I chalked it up to either sunspot activity or voodoo. When that turned up nothing, I tried a reinstall of Office. Having recently dealt with a case involving a corrupt copy of Helvetica, I checked the machine for rogue or corrupt font files in the %WinDir%\Fonts directory. Initially only a single user reported the problem. (This is a technical article, so try to keep up.) It seemed like Word was having a really hard time enumerating all the fonts on the system and creating the previews that are shown in the dropdown. Whenever they tried to open the font drop-down to pick a new font, there was a frustrating delay of about 5-10 seconds between clicking on the drop-down and the drop-down opening, during which time Word would not respond to any user input.ĭuring this time, the drop-down itself would either be invisible apart from the Aero shadow effect, or appear as a filled black rectangle: A couple of staff recently reported that they were experiencing an odd problem in Microsoft Word 2010.
