How to Deploy Fonts with MEMCM

I have been releasing a lot of “Quick Tips” on Twitter recently. This post falls into that category. It isn’t necessarily a deep dive but something that has been requested a few times. In this post I will show you how to deploy SYSTEM Fonts using MEMCM (ConfigMgr)

  1. Prerequisites
  2. Scripts
  3. MEMCM Application
  4. Observe the Deployment

1 . Background

From time to time we may be asked to deploy Fonts to devices. This can be done manually via the Fonts Control Panel applet Start > Settings > Personalization > Fonts

or downloaded by the user from the Microsoft Store. But we like automation and we like MEMCM, so lets create a script and deploy the Font using an application.

2 . Prerequisites

The Font will need to be of file type:-

  • TTF
  • OTF
  • FON
  • FNT

If you have downloaded a Font from one of the many free sites, make sure you have permissions to distribute it in your organization. Not all Fonts are free for commercial use.

In this example, we are only installing a single Font – Switzerland.ttf

3 . Scripts

We will be using PowerShell to install the Font and will require two scripts. One for installation and another for uninstallation.

Script 1: Install a Font

Script 2: Uninstall a Font

4 . MEMCM Application

1 . Put the following files into your source content directory.


2 . Navigate to Software Library > Application Management > Applications > Create Application

3 . Select Manually specify the application information and click Next

4 . Fill in the Application information and click Next

5 . Specify how the Application will appear in the Software Centre and click Next

6 . Click Add to add a Deployment Type

7 . Select Script Installer from the drop down box and click Next

8 . Specify a Name and click Next

9 . Specify the following information and click Next

  1. Content Location = We identified the source files in Step 1
  2. Installation Program = Powershell.exe -ExecutionPolicy Bypass -File “Install_Font.ps1”
  3. Uninstallation Program = Powershell.exe -ExecutionPolicy Bypass -File “Uninstall_Font.ps1”

10 . Click Add Clause to specify a detection method

11 . Add the Path and File Name of the font and click OK

12 . Click Next

13 . Set the following information and click Next

  1. Installation Behaviour = Install for System
  2. Logon Requirement = Whether or not a user is logged on
  3. Installation Program Visibility = Hidden
  4. Maximum Allowed Run Time = 15
  5. Estimated Installation Run Time = 2

14 . Click Add to add a Requirement

15 . Set the Condition to Operating System and select All Windows 10 (64bit) and click OK

16 . Click Next three times and then click Close

17 . Click Next twice

18 . Review the Application Summary and click Close

19 . Right clikc the application and choose Deploy

20 . Choose a Collection to deploy the new application to and click Next

21 . Click Add and choose a Distribution Point or Distribution Point Group and click Next

22 . Choose a Purpose for the deployment, in this example we have chosen to make the application Available in the Software Centre. Click Next

22 . Click Next on the Specify the schedule for this deployment step or set a time/day when this application will be available from

23 . Set the User notifications to something suitable for your environment and click Next

23 . Click Next on the Alerts step or specify a setting suitable for your environment

24 . Click Next, review the deployment and click Close

5 . Observe the Deployment

If we allow adequate time or force a machine policy refresh on a Windows 10 client targeted for deployment we will see our new app in the Software Centre

Click Install

Launch the Fonts control panel applet to verify the Font has been installed


In this post we used two fairly simple PowerShell scripts to deploy a single Font to Windows 10 devices. The same scripts can be used to deploy the Font from Intune as a Win32App. See my previous post for an example of how to deploy a Win32App from Intune

23 thoughts on “How to Deploy Fonts with MEMCM”

  1. Thank you for this! it was extremely helpful since all the other solutions I researched are out of date. One quick note if you copy and paste the install and uninstall commands retype the double quotes, they don’t copy over properly from the clipboard and you will get an 0xfffd0000(-196608) error when installing via software center

    1. Can you elaborate on what you had to do to get this to work? I have retyped the double quotes and am getting the same error code.

          1. Same error here with this script, copied or typed. I tried 6 different Powershell scripts found around web to install 2 fonts via MEMCM, none of the solutions worked. I tested with Win10 versions 1903,1909 an 2004. Finally, I created MSI installer using Master Packager and that solution worked. It’s strange how something so simple as copying files to predefined folder and adding registry key can be near impossible to do for multiple computers.

          2. I faced the same issue during the installation with error 0xfffd0000(-196608). I am still testing it, but I have manually added the set-executionpolicy bypass cmdlet on the script and ran it locally and it worked but not through MEMCM software deployment…

  2. I got it to work now. When creating the app deployment package under the content section I copied the command (Powershell.exe -ExecutionPolicy Bypass -File “script.ps1”) from your post and somehow when I pasted it on MEMCM it copied some unidentified text format which caused this error. What I did is just removed the double quotes and retyped it, and it worked! I had issues with the detection method since I am using multiple fonts, but I fixed it.

    Thank you Ben for the amazing post, I was searching everywhere to find a solution and all the other solutions did not work.

      1. When you copy and paste the install command from my WordPress page check you have ASCII 34 and not 148 for your double quotes – that normally throws the error you got 🙂

    1. When you copy and paste the install command from my WordPress page check you have ASCII 34 and not 148 for your double quotes – that normally throws the error you got 🙂

  3. If you are installing multiple fonts, do you have to do this for each font? Or is there a way of adding multiple fonts in one go?

    1. The scripts will install/uninstall all the fonts in the source directory. If you are placing multiple fonts in the source dir then ensure you specify each one on your application detection method.

  4. Thanks Ben for this.

    I had to make a small change to your SCCM installation code to get it to work. Otherwise my SCCM couldn’t find the fonts and gave some odd errors.

    Here is the code I used:
    powershell.exe -ExecutionPolicy Bypass -File .\Install_Fonts.ps1
    powershell.exe -ExecutionPolicy Bypass -File .\Uninstall_Fonts.ps1

  5. Thanks for this great script! Installing works reliably in every case I’ve tested so far, but uninstalling, not so much. With installing, I’m getting access denied errors like this:

    Remove-Item : Cannot remove item C:\WINDOWS\Fonts\.ttf: Access to the path ‘C:\WINDOWS\Fonts\.ttf’ is denied.

    Did you run across this in your testing at all? I find that if I wait a few minutes and try running it again, it’ll work and uninstall the fonts, but it’s hit and miss, and often takes several tries.

    1. Hi Scott – it looks like the uninstall script could not find any Fonts in the source folder. Can you run this script and tell me the output?

      $ScriptPath = $MyInvocation.MyCommand.Path
      $CurrentDir = Split-Path $ScriptPath
      foreach ($File in $(Get-ChildItem -Path $CurrentDir -Include *.ttf, *.otf, *.fon, *.fnt -Recurse)) {Write-Output $File.Name}

      1. Sorry, I realized after I submitted that comment that the website stripped out the characters I had. I had the greaterthan/lessthan tags around the text “FontName”. So the path IS going to the correct font names and trying to remove the right ones, but uninstall doesn’t always work. It seems to work fine if I restart the computer and then immediately run the uninstall script. But otherwise, there seems to be processes locking the fonts, making uninstallation unreliable if, say, Microsoft Word was opened by the user some time before uninstall, and the user had either clicked the fonts dropdown (thereby loading the font trying to be removed), or actually used the font in the document. If Word is then closed, the font is still active in the system, and attempting to remove it, even as an elevated command prompt under the system context, throws Access Denied because the font is locked by a process. Again, restarting the computer and then running the uninstall script before anything can load the font seems to work, but unreliable. Wondering if you’ve come across this or have any other way to say, check for a the process that’s using the font, and killing it.

Leave a Comment

Your email address will not be published.

Time limit is exhausted. Please reload CAPTCHA.


This site uses Akismet to reduce spam. Learn how your comment data is processed.