Executive Summary:
| Windows automatically registers fonts you drag and drop into the Fonts folder. If you use a VBScript or Windows PowerShell script rather than Windows Explorer to copy fonts into that folder, you don't get the automatic registration unless you use the Shell.Application object. Here are the three steps you need to follow when using the Shell.Application object to install fonts through a VBScript or Windows PowerShell script. |
Windows automatically recognizes fonts you drag and drop into the Fonts folder. However, if you try to install fonts by copying the file at a command prompt or through a script, you can't see them in the Fonts folder or in the Windows font listings. The problem is that fonts need to be registered. When you drag and drop them into the Fonts folder, the Windows Explorer shell copy operation triggers the registration process. If you don't use Windows Explorer, you don't get the automatic registration. . . .
Register
Thanks for writing that -- I wish I'd seen it last week. I had three machines that I needed to install about 250 fonts. I copied the fonts to the machines, but the fonts didn't show in their list boxes (all of the users run as standard users, not admins). When I logged on as an admin and opened up systemroot\Fonts in an Explorer window, the fonts then populated. (I'm glad it was only three machines.)
I'm going to use your technique the next time I need to install fonts on several machines -- then I can do it without needing to log onto each machine.
Thanks!
Bill
AbqBill March 04, 2008 (Article Rating: