installed font missing InDesign 17.2 macOS 12.3 (Monterey) and macOS Catalina
Different clients have the same problem. Installed fonts on the system are not recognised by InDesign 17.2. Other Adobe applications recognise the font and it can be used in those applications. I can recreate the problem, my colleague not. After downgrading InDesign to version 17.01 everything works fine.

We've just released InDesign 17.2.1 version which addresses this issue.
Please update to this latest version using Creative Cloud Desktop application.
In case the fix does not work immediately for you, please try the following:
1) Quit InDesign.
2) Delete the following:
on Mac:
/Users/[yourname]/Library/Caches/Adobe InDesign
/Users/[yourname]/Library/Preferences/Adobe InDesign
on Win:
C:\Users\[yourname]\AppData\Roaming\Adobe\InDesign
C:\Users\[yourname]\AppData\Local\Adobe\InDesign
Relaunch InDesign & see if it works properly now.
--
InDesign team
-
Aaron commented
Same problem here too.
-
Kai Howells commented
Same issue. One font we use is only showing the Italic version in InDesign 17.2 and other Adobe 2022 apps show all the variations just fine.
The font also works perfectly in InDesign 16.x, no problems accessing all the different weights and versions there. -
Kai Howells commented
I've got the same issue, with a different font however. Font is an OpenType font and InDesign 17.2 only shows the Italic variant of the font, whereas InDesign 16.x shows all the variants in the family. Other 2022 apps (e.g. Illustrator) also show all of the different options..
-
Erika commented
In my case it was the font FF Marselis Slab family that wasn't working. Although there may be a lot more fonts that may have the same problem.
-
Almir V Santos commented
I'm having the same issue. Font shows up in Illustrator and Photoshop, but not in InDesign.
I had to downgrade InDesign to version 17.0.1. -
Raimund commented
Me too - macOS Big Sur 11.6.5.. Of the following fonts Inter-Thin and Inter-Light work OK, the other ones appear in Indesign's font list but cannot be used. Have rolled back to Indesign 17.1 and all work OK.
Inter-Black.ttf
Inter-Bold.ttf
Inter-ExtraBold.ttf
Inter-ExtraLight.ttf
Inter-Light.ttf
Inter-Medium.ttf
Inter-Regular.ttf
Inter-SemiBold.ttf
Inter-Thin.ttf -
Fred commented
Same as my fellow users. Issue with 17.2 release. Rolling back to 17.01 solves the problem so far.
-
Ronan McDonnell commented
Having this issue on mac os 10.15.7 and only in Indesign. On rolling back to Indesign 17.0 some fonts still not being recognised, while are fine in other apps, including Adobe apps
-
Haz Olivera commented
I'm having this issue as well. Font shows up in Photoshop & Illustrator, but NOT in InDesingn. SUPER frustrating.
-
Pete Jeffrey commented
Having the same issue with a font installed and added on Creative Cloud. Shows up fine in Illustrator and Photoshop but it's unavailable in InDesign.
-
Hardy commented
Got same Problem!
-
Amber Blakeney commented
I'm having the same issue.
-
Jes Vang commented
I have the same issue! And I've only solved it - temporarily - by downgrading to v16.4. I've tried all suggested solutions. Here is my initial report. I hope the issue will get upvoted and fixed shortly!
-----
Originally posted here: https://community.adobe.com/t5/indesign-discussions/fonts-quot-missing-quot-in-indesign-version-17-2...
I run Windows 10. Today I updated my Creative Cloud (Photoshop, Indesign, Illustrator, Premiere Pro) to the latest versions and found that in InDesign - and only in InDesign - one* of my installed fonts were listed as "missing" when I tried to load the documents I had been working on previously.The font is not in the Typekit or the Adobe cloud font library. It's a bespoke font bought directly from the designers: https://vj-type.com/12-sud
The font is obviously installed in the Windows Font folder, so I tried re-installing it. No difference. Then I started troubleshooting. I copied the font to the Common --> Adobe --> Font folder. I tried clearing the Adobe font cache by deleting ALL instances of "adobefnt*.lst"-files. I uninstalled and re-installed InDesign. I downloaded the Adobe Cleaner Tool and scrubbed InDesign from my computer. I manually deleted all folders and files that had to do with InDesign in the Program Files and App Data folders, and I used CCleaner to remove all junk and clean up the registry between each (and there were many) reboots of the computer.
Nothing helped. The font was still missing in InDesign, but present in all other programs (e.g. Illustrator, Photoshop, Microsoft Word). I downgraded to version 17.1. Didn't help.
Then I downgraded to InDesign version 16.4 (i.e. the 2021 version), and NOW the font is no longer missing and I can use it like previously. WTF!
So this is me submitting this a bug for version 17.2 of InDesign for Windows (well, mine at least).
*I found out later that it was more than one font that went missing, but I didn't check all the fonts in the Windows Font folder. Suffice to say, since it was more than one font - e.g. this bespoke one: https://vj-type.com/11-nord - it seems that it's a program / coding error, possibly connected to TypeKit or cloud font sync? All the fonts are .OTF
-
Joseph Caserto commented
Yes, I had this problem, too. I resolved it by downgrading to 17.1 and toggling Adobe Fonts on and off in Creative Cloud Desktop > Preferences > Settings.
-
Bill Kersey commented
The font "Bazinga-Regular" does not work in my version of ID (17.2) but does work in Illustrator and Photoshop. A colleague created an InDesign document using the font successfully in his version (17.1.0.50) and shared the collected folder yet still does not show as available when opening the original ID file or the IDML.
-
Anonymous commented
Same problem here with ID 17.2 with Monterey 12.3.1. Font works fine with previous versions of ID.
-
After updating from Indesign 16.4.1 to 17.2 I have a disturbing issue: Indesign cannot see the fonts I am using for the company anymore (MetaOT-Book.otf). What a nightmare!
This happens with every Indesign document. Have tried everything (restart, new installation fonts etc.), but so far the only solution is to go back to version 16.4.1.
Patch required! -
Nvard Yerkanian commented
Had to revert to 16.4 to solve the problem.
Reverting back to 17.01 didn't work for me. -
Ryan Thompson commented
Had this issue too … caused a few headaches!
-
Aurora Penticton commented
Same here. Reverted back to 17.1