The screenshot above is from the Microsoft Blog post mentioned above and shows the options. (Windows 10 V1803 Font-Install, Source: Microsoft) There it is mentioned that you can choose via context menu whether the font (from a font file) is to be installed per user or system-wide. I came across this approach at Spiceworks (thematizes Terminal Server). Context menu selection for font installation At TechRepublik I found this article on the topic, which explains this from the perspective of a normal user with store access. Therefore, no administrative actions are required when installing fonts purchased from the store. A font is now installed for a specific user and not system-wide. To make this possible, the developers had to make changes deep within Windows. Windows 10 version 1803 Microsoft therefore introduced the possibility to install fonts from the Microsoft Store with normal user rights. So the problem is the font installation for non-administrators, which was not available in earlier Windows versions – there an administrator authorization was required. If you're a non-admin user and often need to install (or uninstall) fonts, then that could be a big hassle. If you tried to install a font but didn't have admin privileges, then you would be presented with a User Account Control dialog, so that an admin could approve the change. For example, if you browse in File Explorer to a folder containing a font file and right-clicked on the file to bring up the context menu, then the 'Install' option would appear with the security badge, which means that it requires an admin. The need for an admin was reflected in the user interface. Because that is a system-wide change, it always required admin privilege. In the past, fonts in Windows have always been installed for all users. Have you ever wanted to use your own fonts from your account on a shared school or work PC, but couldn't because you didn't have the administrator privileges required to install the fonts? Well, we've heard your frustration about this and have made some changes. In the section Font installation for non-admin users it says: The explanation might be found in the Windows Blog in this article, talking about a Windows Insider Preview. He said, it's the case since Windows 10 version 1803. Then I received feedback from German blog reader Martin Feuerstein who suggested that he read this in a recent blog post. Took me some time to realize…īrought me to publish a short German blog post about this. I don't work with Windows Server, but by chance I came across a tweet from Julian Mooren – who is struggling with the fact, that fonts are installed on a per user-base.ĭid you know that Windows Server 2019 is installing windows fonts on a per-user basis? Your previous install scripts will not work even when executed in SYSTEM context! I guess Windows 10 (1809) is affected as well.

Install a geez font on windows