Windows - System Preferences - Install Fonts

What the font installer does

This Automox Worklet™ detects and installs OpenType (OTF) and TrueType (TTF) fonts on Windows endpoints. The Worklet evaluates available fonts by checking the Windows registry for existing font entries, then downloads and installs missing fonts through either the Google Fonts API or attached custom payloads.

The Worklet supports three installation methods: retrieving fonts by name from Google Fonts, deploying individual font files as payloads, or extracting fonts from ZIP archives. This flexibility accommodates both public and proprietary font deployments.

Why standardize fonts across your organization

verifying consistent fonts across all endpoints maintains brand identity and document formatting integrity. When team members lack required fonts, design documents render incorrectly, causing version control issues, broken layouts, and unprofessional presentations.

Deploying fonts through Automox eliminates manual installation on individual endpoints. This approach scales to thousands of endpoints, reduces user friction, and keeps every endpoint has the fonts needed for proper document rendering and creative applications.

Custom or branded fonts often contain security considerations and licensing restrictions. The Worklet centralizes font management through Automox, providing clear audit trails and verifying compliance with font licensing agreements.

How font installation works

1. Evaluation phase: The Worklet queries the registry key at HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts to identify installed fonts. It cross-references desired font names against existing registry entries to determine which fonts require installation.

2. Remediation phase: The Worklet downloads missing fonts from Google Fonts API or extracts them from ZIP payloads, copies font files to C:\Windows\Fonts, and registers each font in the Windows registry with the appropriate suffix (TrueType) or (OpenType) based on file extension.

Font installation requirements

• Windows 7 or later (Windows 10, Windows 11, Windows Server 2016 and later)

• Administrator privileges required for registry write access and Fonts directory modification

• Internet connectivity if retrieving fonts from Google Fonts API

• Valid font names matching Google Fonts directory or OTF/TTF file names in payloads (without file extensions)

• Optional: Worklet payload configured with OTF, TTF files, or ZIP archives containing fonts

• Available disk space in C:\Windows\Fonts for font files

Expected font installation state

After remediation completes, specified fonts appear in C:\Windows\Fonts and register in the Windows registry. Applications relaunched after font installation access the newly installed fonts immediately without requiring an endpoint restart in most cases.

To verify installation, users can open the Fonts Control Panel (Settings > Personalization > Fonts on Windows 11, or C:\Windows\Fonts folder on earlier versions) and search for the newly installed font name. Subsequent Worklet evaluations return compliant status, indicating the font remains properly installed and registered.

How to validate install fonts changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install fonts.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Error, Get-ChildItem, Write-Warning.

4. Validate remediation effects from script operations such as Write-Error, Test-Path, Write-Warning, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install fonts. This supports repeatable system preferences workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Write-Error, Get-ChildItem, Write-Warning and remediation operations such as Write-Error, Test-Path, Write-Warning. Use these indicators to verify that endpoint changes match intended policy outcomes.