This involves copying the font to: C:\Windows\FontsĪnd registering an entry inside: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Fonts To overcome this, we now use an alternative way of installing fonts to the per-machine location. What this means is that instead of the font being registered inside c:\windows\fonts, you will now find the font in: C:\Users\USERNAME\AppData\Local\Microsoft\Windows\FontsĪnd a corresponding registry entry in: HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts Previously we could use this one-liner: (New-Object -ComObject Shell.Application).Namespace(0x14).CopyHere("C:\Build\Font\A39WB_.TTF",0x14) īut since 1809 this installs the font to the per-user location as opposed to the per-machine location! We discussed previously how registering fonts in a per-user context doesn’t work well with App-V and this is the reason why. The mechanism of installing fonts with PowerShell works slightly differently since the Windfeature update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |