InDesign 2019 doesn't recognize installed fonts after upgrading to Windows 10

[neogeni77904840]

Im having issues with Adobe Indesign CC 2019 after upgrading to win 10 pro 1809. I have 5 fonts that arent recognized by ID even though other programs are seeing them.

{Renamed by MOD}

[Srishti Bali]

Hi there,

Thanks for reaching out. I understand that there are few fonts which are working on other applications but not on InDesign. Let us help make this right. Could you please confirm what type of fonts they are, for example, system fonts/ licensed fonts(paid)/ Adobe Fonts?

If they are system fonts and are installed on the system then we can start with copy-pasting the font files from system fonts folder to the InDesign fonts folder.

• Please open the Windows Font folder (C:\Windows\Fonts) and copy those fonts and paste it to this location C:\Program Files\Adobe\Adobe InDesign CC 2019\Fonts

 

Let us know if that helps. If not, you can try the steps shared here: Troubleshoot fonts in Adobe applications | Mac OS X.

Regards,

Srishti

[neogeni77904840]

I have already done that as well.

I have also tried installing ID 2018 as I saw that was a possible solution but that didnt work either.

[Srishti Bali]

In that scenario, my recommendation would be to fully remove those fonts from your system and reinstall them from scratch. Install the fonts from your source by right-clicking on the font file and selecting Install for All Users.

Do Not use the Install option, a new feature of a recent Windows 10 versions which only makes the font visible to the user installing the font.

Let us know if that helps, or if you need any further assistance.

[Mike Witherell]

It might be those particular fonts. What are they? What type?

[neogeni77904840]

Will just reinstalling and selecting Install for all users do the same as uninstalling/reinstalling? Listed below is the 5 fonts missing in ID but working in other programs like Microsoft Word.

[russellj257374]

Thank you, worked perfectly. Who knew there was a new Adobe 2019 folder which didn't auto import things like fonts - I have wasted an hour trying to fix what should have been done automatically!

[Srishti Bali]

Glad to hear that you are all set. Please feel free to let us know if you have any further query.

Thanks!

[wildkitty]

It's pretty self-expanatory why I'm here. I don't have this path. There's no Adobe InDesign CC 2019 folder in my Adobe folder. Has this changed in 2020?!

[BobLevine]

Everything here has been asked and answered. Please start a new discussion with full details and never assume what you need is self-explanatory...it's not.

[Mike Witherell]

I recommend NOT reinstalling any type 1 PostScript font. They should all have been retired about 18 years ago. If any TrueType fonts are also aging, retire them, too. That would help your system run better and would account for 3 of your 5 fonts. Replace them with newer OpenType fonts.

[neogeni77904840]

Where do I find the replacements for these and are they the exact same because the Helvetica font is a corporate standard for all of our graphic's.

[Laubender]

The best chance to install old PostScript Type 1 fonts is the Fonts folder of your InDesign installation.

Note: You cannot run PostScript Type 1 fonts from a Mac OS X system with Windows.

Regards,
Uwe

[neogeni77904840]

Let me also say that I have copied the entire Fonts folder from a different machine running Windows 7 and installed them using the all user method and also putting them in the ID font folder and it still doesn't work. Let me also note that this was working from a win 7 box and started after I upgraded it to win10.

[Nikhil R Gupta]

Helloneogeni77904840

If you create a new file on InDesign. Are you able to use these fonts on the new files? Are you able to use these fonts on another Adobe or non Adobe application on this windows 10 machine?

Thanks,

Nikhil Gupta

[neogeni77904840]

They dont work in ID at all but I can use them in other programs such as word.

[Nikhil R Gupta]

Hello neogeni77904840

If you create a new file on InDesign, do you see that font under fonts list? Do you have any other adobe application to test? Sometimes there is a version mismatch and InDesign gives an error for missing fonts if there is another version of the same font present on the file. You can also try to use the font on Word and then copy and paste the text on InDesign and check if you see the font.

Thanks,

Nikhil Gupta

[Bevi Chagnon - PubCom.com · Accepted solution]

Your fonts listed in your screen capture are outdated and incorrect.

RE: Outdated

Microsoft is removing all older versions of TrueType (TT) and PostScript (T1) fonts when new editions of Windows 10 are installed.

The entire computer industry converted to OpenType/Unicode fonts in 2000 (19 years ago) and Microsoft is finally ditching the old technologies completely. (Sad, but we're all required to use this century's technologies!)

As Mike Witherell mentioned above, replace those outdated fonts with OpenType versions. See below for details.

RE: Incorrect

Looking at your screen capture above, I noticed your Minion Pro fonts have odd names that include the weight number (47 Light Condensed, 57 Condensed).

Minion Pro is an Adobe font available for free through your Creative Cloud subscription. And it doesn't contain those fonts anywhere in the entire 65 font family. See the font family at Minion | Adobe Fonts

Solution:

Get the correct fonts installed with the following tasks:

1. Download OpenType (OTF) versions of the PostScript (T1) fonts:
   1. Helvetica Neue is available from Monotype at https://www.monotype.com/  In fact, they just updated Helvetica Neue to Helvetica Now and you might go with that version. Helvetica is not free from any vendor.
2. Swap out Times Roman (TT) for the OpenType version of Times New Roman that came with your Windows operating system.
3. Keep Calibri: it's fine as is.
4. Get legitimate copies of the Minion Pro family from your Creative Cloud app (see screen capture below) or directly from Search results for minion+pro | Adobe Fonts   These will be free with your Creative Cloud subscription.
   1. Swap the Minion Pro 47 Light Condense with something else. There is no "light" version of Minion!
   2. Swap the Minion Pro 57 Condensed with Minion Pro Condensed.

[Dov Isaacs]

https://forums.adobe.com/people/Bevi+Chagnon+%7C+PubCom  wrote

Your fonts listed in your screen capture are outdated and incorrect.

RE: Outdated

Microsoft is removing all older versions of TrueType (TT) and PostScript (T1) fonts when new editions of Windows 10 are installed.

The entire computer industry converted to OpenType/Unicode fonts in 2000 (19 years ago) and Microsoft is finally ditching the old technologies completely. (Sad, but we're all required to use this century's technologies!) …

Just so that there is absolutely no misunderstanding about the response above, Microsoft does not, repeat does not uninstall any user-installed fonts, whether they are Type 1, TrueType, or OpenType formats when updating operating system versions (either Windows 7/8.x to Windows 10 or from one Windows 10 version to the next half-yearly Windows 10 version.

Microsoft does update versions of their own system fonts (such as Times New Roman, Arial, Calibri, et.al.) when updating OS and/or Office versions. And the updates may be quite dramatic. Arial and Times New Roman as TrueType fonts in early Windows versions each had less than 256 glyph definitions and in the latest version of Windows 10 as OpenType TrueType fonts have 4503 and 4685 glyph definitions respectively. Calibri, the default font in Microsoft Office currently has 6780 glyph definitions!

That having been said, although Microsoft allows Type 1 fonts dating all the way back to the 1980s to be installed on Windows, Microsoft has dropped all support for those fonts in Microsoft Office applications. They are supported in PostScript drivers and in all Adobe applications. Pre-OpenType TrueType fonts continue to be fully-supported in all applications on Windows; they are essentially treated as crippled OpenType TrueType fonts.

With regards to the Minion Pro with the Light weights and numbers, no such fonts were ever licensed by Adobe. I suspect that someone may have hacked around with a copy of Minion and made their own variations, giving them the names shown.

          - Dov

[Bevi Chagnon - PubCom.com]

https://forums.adobe.com/people/Dov+Isaacs  wrote

... Microsoft does not, repeat does not uninstall any user-installed fonts, whether they are Type 1, TrueType, or OpenType formats when updating operating system versions (either Windows 7/8.x to Windows 10 or from one Windows 10 version to the next half-yearly Windows 10 version. ...

Dov, you know I know you're always right about these things.

But...

We do have documented cases of MS removing user-purchased fonts, specifically various versions of Arial Unicode. The original Arial MS Unicode (installed with most versions of Windows for many years) was removed during a Windows update 18-24 months ago due to a licensing change between Microsof, Ascender, and Monotype.

After Arial Unicode MS was removed by Microsoft, we had to purchase the font from Monotype in order to complete a client's job. It has never worked reliably ever since. And every once in a while, it completely disappears from our Windows systems (we suspect after a Windows update) or suddenly shows a byte size of 0 bytes when viewed in Windows explorer. Neither of the 2 companies have been able to tell us why a font, purchased separately from Monotype, would be "changed" by Microsoft's operating system.

When we do need to use Arial Unicode in a document, we use a Mac with the OpenType versions, and everything goes smoothly.

(And Monotype has now released so many versions of Arial that complicate this problem. Don't mention the Arial font to me!)

https://forums.adobe.com/people/Dov+Isaacs  wrote

... although Microsoft allows Type 1 fonts dating all the way back to the 1980s to be installed on Windows, Microsoft has dropped all support for those fonts in Microsoft Office applications. They are supported in PostScript drivers and in all Adobe applications. Pre-OpenType TrueType fonts continue to be fully-supported in all applications on Windows; they are essentially treated as crippled OpenType TrueType fonts.

We've had problems with PostScript fonts in InDesign/Windows. Constant missing font errors, even when they're installed correctly. Has become worse in the last couple of updates to Windows 10, and we haven't seen comparable problems on our Macs. In fact, when a client's Windows job requires a PostScript font, we migrate the project to our Macs.

I can't calculate the amount of time my firm has lost dealing with these font problems on Windows systems. And our clients' loss of time, too. The industry is being burned on this.

Out of utter frustration, our office has adopted these practical solutions that work:

1. Don't use PostScript or old TrueType fonts for projects on Windows systems. The experience will be unstable. Move the project to Mac or switch fonts on Windows.
2. Use opensource OpenType/Unicode fonts for projects on Windows systems.
3. Use Adobe Type OpenType/Unicode (formerly called TypeKit) fonts for InDesign documents, but note that there are frequent user rights, licensing, and embedding problems when used in other Windows apps.

I think the final solution will be developed among the lawyers of the companies involved in this mess of intellectual property rights. I also think that solution is a few years away. Would appreciate any muscle you can exert to speed up the solution!

— Your colleague,

Bevi the Font Fairy

[Dov Isaacs]

Bevi,

I know that we both agree that Font is a four letter word beginning with an F!

The case of Arial MS Unicode that you cite is very interesting. Microsoft had every legal right to remove Arial MS Unicode if in fact there was some “issue” with its licensing from Monotype. They didn't have the right to remove a font that you separately licensed.

That having been said, if you installed a copy of your privately-licensed copy of Arial MS Unicode from your system backups, that should have restored the font functionality that you had.

In addition, I would recommend that other than so-called “system fonts” that you store fonts anyplace on Windows anyplace other than the Windows fonts directory (i.e., C:\Windows\Fonts). Install fonts by right-clicking and using the Install as shortcut for all users option which essentially links to the font file. All my non-system font files are installed that way (and from a directory structure that is organized by font source and family) – works like a charm. And it is where I store my copy of Arial MS Unicode!

Quite frankly, I haven't used Type 1 fonts, either on Windows or MacOS, to any large degree for years. However, for those I still have installed, as long as I don't try using them with Microsoft Office applications, I have had no problems (other than missing OpenType features I am very addicted to) and that especially is true for the Adobe applications. There is no difference in Adobe's Type 1 support for Windows versus MacOS other than that under MacOS, these applications can use either the MacOS-only resource fork versions of Type 1 fonts or the Windows-based .pfb+.pfm file versions of Type 1 fonts.

I most strongly endorse using only OpenType fonts for any and all new projects either with Adobe or other products! OpenType CFF or OpenType TrueType should not be an issue as long as the fonts are sourced from reliable font foundries.

I most strongly endorse migrating from Type 1 fonts or very old pre-OpenType TrueType fonts for any and all existing projects with Adobe or other products as needs dictate or as convenient (although finding extra time for this is always problematic, right?)! The same recommendations apply as to font formats.

In no case should any content remain formatted with the older Type 1 Multiple Master fonts. The only Adobe application that provides support for them is Acrobat which must support them for long term compatibility and for substitution fonts.

And for the time being, I would advise against use of so-called Variable OpenType fonts or SVG OpenType fonts for production purposes. Support for these fonts is not consistent in workflows!

          - Dov

[Bevi Chagnon - PubCom.com]

Agree 100% with above.

Yeowza!

[neogeni77904840]

I would like to thank everyone for their help I will pass this information along!