You add fonts from the Microsoft Store by opening Settings > Personalization > Fonts, clicking Get more fonts in Microsoft Store, picking a font family, and pressing Get. Windows 10 and 11 download and install it automatically for the signed-in account, and the font appears in Word, Photoshop, and other apps after a restart. Availability varies by region and Windows edition, so not every font you find online is in the Store.

How Windows Routes Store Fonts Through the Settings App

Microsoft closed the old Control Panel font-installation loop for Store packages. The Fonts page at Settings > Personalization > Fonts is the front door, and the Get more fonts in Microsoft Store link hands off to the Store app's font category rather than a generic search.

This matters because the Store installs fonts as per-user packages, not machine-wide files dropped into C:\Windows\Fonts. A font you install from the Store is licensed to your Microsoft account and tied to the device, so it typically won't follow you to a second PC unless you install it there too.

The version boundary is Windows 10 version 1809, released in October 2018, which is when Microsoft added Store font support to Settings. Windows 11 carries the same path forward. Older builds (1709 and earlier) lack the Get more fonts link entirely, which is a common reason readers can't find it.

A worked time estimate: locating the Fonts page takes roughly 30 seconds from a cold Start menu, browsing the Store font category takes 1–3 minutes, and the download itself runs from a few seconds for a single weight to a couple of minutes for a family with a dozen styles. Budget under five minutes total for one family on a normal broadband connection.

Confirm Your Windows Version and Region Before You Start

Two conditions determine whether the Store path works at all: your Windows build and your Store region. Check the build first by pressing Windows key + R, typing winver, and reading the version line. You need Windows 10 1809 or later, or any Windows 11 release.

Region matters because the Microsoft Store exposes different catalogs per market. A font family licensed for the US storefront may not appear in a smaller regional catalog. You can see your Store region in the Store app under Settings > App settings > Country or region; changing it requires a matching payment region and isn't a casual fix.

Also confirm you're signed in with a Microsoft account. Store font installs are account-bound, and a device using only a local account can hit sign-in prompts mid-install. Signing in once at the Store level avoids that loop.

If your organization manages the device through Group Policy or Intune, the Store may be blocked outright. In that case the Get more fonts link either does nothing or opens a page with a "This app has been blocked by your system administrator" message. That's a policy boundary, not a bug, and only your IT admin can lift it.

The Exact 6-Step Install Sequence, Start to Finish

Here's the real order of operations, with the on-screen labels you'll actually see.

1: Open Settings (Windows key + I), then click Personalization in the left sidebar. 2: Click Fonts at the top of the Personalization list. On Windows 11 you may need to scroll; the entry sits below Background and Colors. 3: On the Fonts page, click the Get more fonts in Microsoft Store link near the top. The Store app opens directly to its font category. 4: Browse or use the Store search box and click a font family card to open its product page. 5: Press the Get button (it reads Install on some builds). The button changes to Launch or Open when the download finishes. 6: Return to Settings > Personalization > Fonts and confirm the family appears in the "Available fonts" list. Then restart any open app that should see it.

If the Get button is greyed out, you're usually not signed in to the Store, or the family is already installed on the account. If the Store opens to a blank page, close it fully from Task Manager and reopen the link. If the font installs but doesn't appear in an app, close and relaunch that app before troubleshooting further; most Adobe and Office apps cache the font list at startup.

Which Store Font Families Are Worth Installing First

The Store font catalog leans heavily on display and script families rather than workhorse text faces, so the practical question is what each family is for. Here's the comparison most guides skip.

Font family Style type Best use Practical limitation
Ink Free Casual handwriting Notes, annotations, informal headings Poor legibility below 12pt
Segoe UI Variable Variable sans-serif UI mockups, modern documents Already default on Windows 11
Bahnschrift Variable condensed sans Posters, technical labels Limited weights on older builds
Cascadia Code Monospace with ligatures Code editors, terminal display Ligatures can confuse beginners
Sitka Optical-size serif Long-form reading, print drafts Large family size, slower download
Comic Neue Rounded informal sans Children's materials, friendly branding Not suited to formal documents

The catalog rotates, and specific families may not appear in every region, so confirm availability in your own Store rather than assuming a list stays fixed. Segoe UI Variable is the one family most Windows 11 users already have: it replaced Segoe UI as the system default, so installing it from the Store is redundant on that OS.

Bahnschrift is the notable exception for design work. It ships with Windows 10 and 11 as a variable font, so you can adjust weight and width continuously in apps that support variable axes, something most Store display fonts don't offer. Sitka, designed by Microsoft for screen and print reading, carries multiple optical sizes, which is rare among free fonts.

For code work, Cascadia Code is the one Store font with a clear professional use case outside design. It ships with ligatures for character pairs like -> and !=, and terminal apps can use it directly. If you write code daily, install it before any display family.

Fix the Five Failures That Block Store Font Installs

Store font problems cluster into five recognizable cases. Handle them in this order.

The missing Get more fonts link case means your build predates 1809 or the Fonts page is loading a legacy view. Run winver to confirm, then update Windows through Settings > Windows Update.

The Store opens but shows no fonts case usually means a stale Store cache. Run wsreset.exe from the Run dialog (Windows key + R), wait for the Store to relaunch, and try again.

The download stalls at 0% case points to a network or proxy issue. Disconnect any VPN, then check Settings > Network & internet for a metered connection flag; Store downloads pause on metered links unless you allow them.

The font installs but apps don't see it case is a caching problem. Fully quit and reopen the app. For Office, close all windows including background processes before relaunching.

The "This app has been blocked" message case is a Group Policy or Intune restriction. You cannot override it locally; contact your administrator with the exact error text so they can allowlist the Store font category.

Per-User Licensing Limits You Should Know Before Relying on Store Fonts

Store fonts are licensed per Microsoft account, and Microsoft's Store terms treat font purchases and free acquisitions as tied to the purchasing account. That has two practical consequences.

First, a Store font installed on a shared family PC is available to the account that installed it, not automatically to every user profile on that machine. If a colleague signs in on the same device, the font may not appear for them.

Second, moving to a new PC means reinstalling each Store font under the same account. There's no migration wizard that carries Store fonts across devices. Document which families you rely on for client work so a hardware refresh doesn't break a template.

The upside: Store fonts don't carry the same embedding restrictions as some retail licenses in the same way, but check each font's license page in the Store before embedding it in a PDF or design file you distribute. Microsoft's font licensing page remains the authority for redistribution questions, and the Store product page links to it per family.

How to Remove a Store Font Without Breaking Documents

Uninstalling a Store font happens in Settings > Personalization > Fonts. Click the family, then click Uninstall on its detail page. The font is removed for the signed-in account immediately.

Documents that used the font don't crash; they substitute a fallback face. In Word that's typically Calibri or Aptos depending on your Office version, and in Adobe apps it's usually Myriad Pro or a system sans. Layouts shift when substitution happens, so check client deliverables before uninstalling.

If you uninstall a font that a template depended on, the fix is reinstalling from the Store under the same account, which restores the original font mapping. There's no need to rebuild the document.

One edge case: fonts installed through the old Control Panel method (right-click an .ttf file > Install) aren't managed by the Fonts settings page the same way. If a family doesn't show an Uninstall button, it came through the file-based route and needs removing from Control Panel > Appearance and Personalization > Fonts instead.

Install Fonts Outside the Store When the Catalog Falls Short

The Store catalog is thin compared with what's available elsewhere, and some families you need simply won't be there. In that case you install font files directly.

Download the .ttf or .otf file from the foundry or a reputable free-font source, then right-click it and choose Install for the current user or Install for all users if you have admin rights. Files land in the per-user or system font folders accordingly.

Large families often arrive as .zip archives. Extract first, select all the font files, right-click, and install in one action rather than one file at a time; Windows queues them.

The trade-off is that file-based fonts aren't tracked by the Store, so there's no account record of what you installed. Keep your own list of file-based fonts and their sources if you work across multiple machines, because reinstalling after a PC refresh is manual.

Match the Install Route to How You Work

The right route depends on whether you need a font once or repeatedly, and whether you share a machine.

Situation Recommended route Reason
Solo user, single PC, display font Microsoft Store One click, account-tracked, easy uninstall
Team template used on shared PC Install for all users via file Available to every profile on the device
Code editor font Store (Cascadia Code) Ships with terminal support built in
Client project with embedded fonts Foundry download with license check Redistribution rights confirmed at source
Managed corporate laptop IT-approved deployment Store often blocked by policy

For a solo designer on one PC, the Store path is simplest. For a shared studio machine with multiple profiles, file-based installation for all users avoids the per-account gap. In managed environments, the answer is whatever your admin deploys.

The one drawback of the Store route worth repeating: fonts don't follow you automatically to a new device. If you build templates that depend on a specific Store family, budget 10–15 minutes per new PC to reinstall your list.

FAQ

Does adding fonts from the Microsoft Store require a Microsoft account?

Yes. Store font installs are bound to the signed-in Microsoft account, and a device running only a local account will prompt for sign-in during the process. Sign in once at the Store level before clicking Get to avoid the mid-install prompt.

That link appeared with Windows 10 version 1809, released in October 2018. On earlier builds the Fonts page is a read-only list. Run winver to check your build, then update through Settings > Windows Update.

Do Store fonts work in every app?

Most apps see them after a restart, but apps that cache the font list at launch (Office, Adobe Creative Cloud) need a full quit and relaunch. Some legacy apps that only read the system font folder may never see per-user Store fonts, which is a known limitation of the per-account install model.

Can I install Store fonts on more than one PC?

You can, but not automatically. Each Store font must be reinstalled on each device under the same Microsoft account. There's no migration tool that carries Store fonts across machines, so keep a list of your essential families.

What happens to my documents if I uninstall a Store font?

Documents don't break. The missing font gets substituted with a fallback face (usually Calibri or Aptos in Office), which changes layout. Reinstalling the same font under the same account restores the original appearance without rebuilding the file.

Are Store fonts free?

Many are free to acquire, but free and licensed aren't the same thing. Each family carries its own license terms shown on its Store product page, and embedding a Store font in a distributed PDF or design file may have restrictions. Check the license page before distributing.

Is Cascadia Code in the Microsoft Store the same as the GitHub release?

The Store version installs as a managed package and updates through the Store. The GitHub release from Microsoft's repository is the same typeface but updates manually and includes preview builds. For terminal use, either works; the Store route is simpler to maintain.

Can I install fonts from the Store if my laptop is managed by work?

Usually no. Group Policy or Intune frequently blocks the Store, and the font category may show a "blocked by your system administrator" page. Only your IT admin can allow it, so send them the exact error text rather than trying workarounds.