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.

Change default font windows 10 1803