Some fonts are missing after upgrade

Symptom

Some users have found that certain fonts they use are missing after upgrading to Windows 10.

For example, if the English (or German, Spanish...) version of Windows 10 was installed, then the Gautami, Meiryo, Narkism... font is missing.

Cause

Many fonts that shipped in prior versions of Windows have been moved into optional features in Windows 10. After upgrading to Windows 10, these optional features may not be installed on your system. The result is that the fonts in those optional features will not be present.

If you need to use a font in one of these optional features, any of them can be installed on any Windows 10 system, as explained below.

Background

Since Windows Vista, every Windows system has included all Windows fonts. Windows supports many languages, and many of the fonts are intended primarily for use with particular languages.

For example, the Meiryo or Raavi font can be used for English, but they were added to Windows to support other languges: Meiryo was created to support Japanese; Raavi was created to support Panjabi or other languages written in Gurmukhi script. Most English (or German, Arabic, Ukrainian...) speakers don't use Gurmukhi or Japanese writing, but they still would all have these fonts on their system, and many others intended for particular languages.

Having fonts that aren't needed or being used provides no benefit, but they take up system resources and clutter up font lists with options that have no relevance. In order to optimize system resources and user experience using fonts, many fonts that were included in Windows 8.1 were moved into optional features in Windows 10. A comprehensive list of the font families in each of the optional features is provided below.

All of these fonts are organized into optional features that are associated with particular languages. For example, the DaunPenh, Khmer UI and MoolBoran fonts were all designed primarily to support Khmer, and are now in the Khmer Supplemental Fonts feature.

While all these international fonts have been moved into optional features, every Windows 10 system still includes fonts that provide comprehensive coverage of international languages and the Unicode character encoding standard. So, you don't need any of these optional features installed if, for instance, you occasionally browse in Edge to sites that have Chinese, Hebrew or Tamil text.

In addition to these fonts from previous versions of Windows, there are also some new fonts added in Windows 10 intended for use with English and other European languages that are included in an optional feature, Pan-European Supplemental Fonts. (See below for details on the fonts provided with this feature.) This optional feature does not have any language associations. If you'd like to use these fonts, you'll need to manually install this optional feature, as described below.

Automatic installation of optional font features based on language associations

As described above, most of the optional font features have particular language associations. These are automatically installed if you installed the associated language version of Windows. For example, if you do a clean install or upgrade using the Thai version of Windows 10, then the Thai Supplemental Fonts feature will be automatically included during the setup.

The language-associated font features are also installed automatically based on other language settings. In particular, if you add a language into your user profile (which is the same as enabling a keyboard for the language), then any association optional font feature will be installed automatically at that time.

When upgrading from Windows 8 or Windows 8.1, language settings that were configured prior to the upgrade will also be detected during the upgrade, and any associated optional font feature will be installed during the upgrade. Similarly, if you add a user with an existing Microsoft Account that has roamed settings that were originally configured on a Windows 8 or Windows 8.1 system, when the language roam into the Windows 10 system, any associated optional font features will be automatically installed.

If upgrading from Windows 7, keyboards for additional languages that were enabled on the Windows 7 system will be detected and used to configure language settings in Windows 10. At this time, associated optional font features will not be automatically installed during the upgrade process. However, some time after the upgrade is complete, a maintenance task will detect the language settings and install the associated optional font features. It may take a few days before this happens. Until then, you can always install any optional font feature manually using the steps described below.

Installing optional language-associated features by adding a language to your settings

If you want to use some of the fonts in an optional feature and you know that you will want to view Web pages, edit documents or use apps in the language associated with that feature, then you should add that language into your user profile. This is done in Settings; here are the steps, using Hebrew as an example:

  • Click the Start button.
  • Click Settings.
  • In Settings, click Time & language.
  • Click Region & language.
  • If Hebrew is not included in the list of languages, click the "+" icon next to Add a language.
  • Scroll to find Hebrew, then click on it to add it to your language list.

Once you have added Hebrew to your language list, then the optional Hebrew font feature and other optional features for Hebrew language support will be installed. This should only take a few minutes.

Note: The optional features are installed by Windows Update. You need to be online for the Windows Update service to work.

Also note: If you are on a work machine, some businesses manage updates separately, in which case the optional features might not install. If that's your situation, please get help from your system administrator.

Installing optional features independent of language settings

Any or all of the optional font features can be installed manually without needing to change language settings.

If you want to install all of the optional font packages and are running version 1607 (build 14393) or later, there's a link in the Fonts control panel to allow you to do that. (In earlier Windows 10 versions, you'll need to add each of the optional features separately, as described below.) Here are the steps:

  • Open the Fonts control panel:
    • Method 1: Click the Start button and type "fonts"; a link to the Fonts control panel should appear in the Start menu.
    • Method 2: Open the Run dialog: press Win+R, or right-click on the Start button and select Run. Then enter "fonts" and enter.
  • In the left pane of the Fonts control panel, click the link "Download fonts for all languages":

You can also install individual font features. Here's how—I'll use the Hebrew Supplemental Fonts feature as an example:

  • Click the Start button.
  • In Settings, click System.
  • Click Apps & features.
  • Click on the link, Manage optional features.
  • If "Hebrew Supplemental Fonts" is not listed among the installed features, click on the "+" icon next to Add a feature.
  • Scroll to find "Hebrew Supplemental Fonts". Click on that item, then click on Install.
  • Click on the back arrow in the upper corner of the window.

You should see the Hebrew feature in the list as installed or in the process of being installed.

After installing optional font features, the fonts should appear in the Fonts control panel and in font-picker lists. Some apps might not detect the change until the app is re-started. If you still don't see some of the fonts, sign out and sign back in. A reboot should not be required.

Note: The optional features are installed by Windows Update. You need to be online for the Windows Update service to work.

Also note: If you are on a work machine, some businesses manage updates separately, in which case the optional features might not even be visible to you—when you go into Add a feature, you might not see the optional features listed. If that's your situation, please get help from your system administrator.

Fonts included in optional font features

Here's a comprehensive listing of which font families are included with each of the optional font features. Some font families may include multiple fonts for different weights and styles.

Arabic Script Supplemental Fonts: Aldhabi, Andalus, Arabic Typesetting, Microsoft Uighur, Sakkal Majalla, Simplified Arabic, Traditional Arabic, Urdu Typesetting
Bangla Script Supplemental Fonts: Shonar Bangla, Vrinda
Canadian Aboriginal Syllabics Supplemental Fonts: Euphemia
Cherokee Supplemental Fonts: Plantagenet Cherokee
Chinese (Simplified) Supplemental Fonts: DengXian, FangSong, KaiTi, SimHei
Chinese (Traditional) Supplemental Fonts: DFKai-SB, MingLiU, MingLiU_HKSCS, PMingLiU
Devanagari Supplemental Fonts: Aparajita, Kokila, Mangal, Sanskrit Text, Utsaah
Ethiopic Supplemental Fonts: Nyala
Gujarati Supplemental Fonts: Shruti
Gurmukhi Supplemental Fonts: Raavi
Hebrew Supplemental Fonts: Aharoni Bold, David, FrankRuehl, Gisha, Levanim MT, Miriam, Miriam Fixed, Narkism, Rod
Japanese Supplemental Fonts: Meiryo, Meiryo UI, MS Gothic, MS PGothic, MS UI Gothic, MS Mincho, MS PMincho, Yu Mincho
Kannada Supplemental Fonts: Tunga
Khmer Supplemental Fonts: DaunPenh, Khmer UI, MoolBoran
Korean Supplemental Fonts: Batang, BatangChe, Dotum, DotumChe, Gulim, GulimChe, Gungsuh, GungsuhChe
Lao Supplemental Fonts: DokChampa, Lao UI
Malayalam Supplemental Fonts: Karthika
Odia Supplemental Fonts: Kalinga
Pan-European Supplemental Fonts: Arial Nova, Georgia Pro, Gill Sans Nova, Neue Haas Grotesk, Rockwell Nova, Verdana Pro
Sinhala Supplemental Fonts: Iskoola Pota
Syriac Supplemental Fonts: Estrangelo Edessa
Tamil Supplemental Fonts: Latha, Vijaya
Telugu Supplemental Fonts: Gautami, Vani
Thai Supplemental Fonts: Angsana New, AngsanaUPC, Browallia New, BrowalliaUPC, Cordia New, CordiaUPC, DilleniaUPC, EucrosiaUPC, FreesiaUPC, IrisUPC, JasmineUPC, KodchiangUPC, Leelawadee, LilyUPC

 

Discussion Info


Last updated October 22, 2018 Views 100,840 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

My font losses after Windows 10 Creators Update have nothing to do with languages, but were fonts installed over years, mostly through Corel Draw products.  I am a designer. Some of these fonts were hard to find. Without a pre-Creators list, I don't know where to begin restore these other than searching old CD's and thousands of fonts....but then I don't have the names in front of me with which to search.  I deal with brands, trademarks, advertising layouts, corporate identity matters AND MY FONTS ARE GONE!

This is a HUGE mess for me with dozens, if not hundreds of restoration hours. I do not know I'm missing a font until I get a client project update and I cannot see the font to match. Today I have an important trademark submission to US Patent and Trademark Office and the necessary font is GONE. I do have a name but searching it to reload...., a headache. These were included in my versions of Corel since 1990, downloaded as needed. Granted many have not been accessed for months or years but they belong to important font families.

What are you all doing about this and WHEN???

We're aware of this issue and working on a fix for it. Meanwhile for a workaround, you can add a DWORD value named "DisableFontBootCache" under registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize, and set its data to 1. Though this will disable font cache and slows down system boot, you should delete this value once a fix for the issue is released.

The issue is that corrections to missing fonts in Creators Edition do not survive system re-boots.

Installed some missing fonts in Win 10 Creators Edition. Rebooted. Everything worked fine. Then, sadly, rebooted again and once again the reinstalled fonts were not detected by any application. Same symptom - changes to the font cache/directory, what ever it is called, do not survive a second reboot. Something in the boot-up code restores the font configuration of the machine to some initial installation state. Even though new fonts are present in the fonts directory and the registry, they are somehow not activated/recognized for use by applications. When a new font is installed and the machine rebooted, that font is initially activated/recognized for use. A subsequent reboot then erases/deletes that activation/recognition and returns the machine's available font configuration to some predetermined state defined at the installation of Win 10 Update to version 1703, the so called Creators edition. This is the problem Microsoft has to fix. Missing avionics instrument fonts in Flight Simulator FSX and Prepar3D are just one consequence of this overall boot-up bug. BTW, when a Microsoft issued Cumulative Update such as 2017-06 (KB 4022725) is installed and the machine rebooted to initiate the Update the font problem goes away. But it is back as soon as a second re-boot is executed. Also, when the "Download Fonts for all Languages" option is executed in the Font Settings directory, those downloaded fonts vanish after a second re-boot. 

Is Microsoft EVER going to acknowledge and correct this problem? 

This isn't just a case of missing fonts it is a case of the whole font system being broken in Win 10 Creators update.

Installing new fonts and having them be retained in Windows is a nightmare.

Installing multiple font styles i.e Font A Regular/Font A Bold/font A italic etc will see each next font installed overwrite the previous from the same family so as only the last font installed from that name show. I have read numerous posts regarding this all over the net from Techs to Graphic Designers. it is not isolated.

How long have you been doing this, Microsoft?

This information about foreign language fonts does not begin to address the "Creators Update" repeated mangling of my fonts when restarting the computer. The problems include the involuntary deleting of the Arial family (except for Arial black) and deleting font shortcuts for fonts from outside of the Windows\Fonts folder that had been installed using the shortcut reference to the font's location. Creators Update indeed!

My reply, which I have deleted, was to the author of one specific message that I took issue with. I apologize if anyone interpreted my reply as challenge or an attempt to fuel any fire with the group of users who are seeking answers and challenging Microsoft in a respectful manner. I have no problem with challenging and harsh feedback. However, I do have a problem with someone wishing harm to myself and my coworkers. I understand folks getting frustrated, but I don't believe these kinds of sentiments are ever warranted. 

Hi, MargaretWalter_943

Yes, you are right: others receiving Word documents you've sent that use the David font may not have that font present on their system and see the document displayed with some other font. There's a sense in which this isn't really a new issue. Let me explain what I mean.

When you send documents to others as Word files, there has always been an issue that they may not have the fonts you used. This is kind of obvious if you were using custom fonts from a third-party source, of course. But even when using Windows fonts, some people uninstall fonts they don't use to clear away clutter from their font lists or thinking that it will speed up their system to have fewer fonts.

So, in general, this issue isn't new in Windows 10, though it's true that we've increased the chance someone would encounter this for particular fonts such as David.

There are ways you can avoid any uncertainty about what fonts will be present on the other person's system, even when using custom fonts. First, if your situation is one in which others need to be able to read the documents you send, but they don't need to be able to edit them, then you can save documents in Word to either PDF or XPS format. When saving to these formats, any necessary font data gets stored in the file itself, ensuring that it can be displayed correctly on any system. You'll find these options in the "Save as type" portion of Word's Save As dialog:

Or, you can also save Word files with the fonts embedded. This allows the file to be viewed in Word on another device using the font you used, even if that wasn't installed on the other device; and it also allows the other user to edit the document using that font. This option is also found in Word's Save As dialog, though it's a little harder to discover. First, click on "Tools" next to the Save button and select "Save Options...":

You can also go into Word options another way and then select the Save tab. At the bottom of the Save settings, you'll find a section, "Preserve fidelity when sharing this document":

By default, this is disabled. If you check the "Embed fonts in the file" option, then the next to options become enabled. Clearing the second checkbox would be good if others need to be able to edit the document.

Note in particular the third checkbox: it's set by default. If you clear it, as shown here, then the David font will be present when opened in Word even if the other person has Windows 10 and doesn't have the Hebrew Supplemental Fonts feature installed. Moreover, it would ensure that David or any other font such as Arial would be present in case the other person (using Windows 10, Windows 8.1, Windows 7 or whatever) has uninstalled those fonts from their system.

If you're using third-party fonts, there is one small issue you might encounter when using either of the approaches I've mentioned: some font licenses do not permit embedding, and so can't be saved within a Word, PDF or XPS file. This doesn't apply to any of the Windows fonts, however. You can discover the embedding permissions of any of your fonts using the Details view of the Fonts control panel: it has a "Font embeddability" column.

We're interested in your feedback on these changes, and on use of alternate methods that I've described here. We want to find ways to improve user experiences, and that includes not putting a lot of fonts on people's devices that they'll never use, but also making sure that someone like you still gets fonts that they have used and want to continue using. Submitting feedback via the Windows Feedback app would be appreciated.

I hope the additional information I've provided here is helpful.

David ZhuMS  gave the workaround on July 31 that solved the problem for me. It should work for you too.

This is all fine and good... except the fonts that EVERY time Windows has a major update are ones I have purchased and installed. How about this, keep your GD paws off my files!!!

As a graphic designer these fonts are part of my work and livelihood. I don't have time to install them over and over again because an update decided to remove them or make them inaccessible. You have no valid reason to do so and you need to stop doing this. If I installed a font I expect it to be there like every other piece of software I install and you need to treat it the same way as everything else - my photos, my music, my documents. Stunts like this is why people have flocked away from Microsoft and Windows machines... keep going and see how much more market share you lose.

All, ALL of my custom fonts, which I've amassed over the years, are gone. I have no way of replacing them all because I keep no master list of fonts, since I -- naively, as it turns out -- never thought that Windows would just delete them all without a trace. None of the solutions mentioned above do anything to resolve the issue. Thanks, Microsoft: it's a very special moment as a working graphic designer when I see that the only fonts available to me are default system fonts.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.