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
-
Tom Moulaert commented
I just had a chat with Viplove Dhar and cleaning the InDesign Caches from ~/Library/Caches (on my Apple Mac) solved the problem.
-
Laura Graf commented
Hi all! I am also joining in having the same problem on my new Macbook pro M1 Pro, Monterey 12.3. Font is visible in all applications beside Indesign which doesn't show it at all .
-
Chris commented
We are having the same issue as everyone else. We have one font that works on all other programs except 17.2.1. Using an older version does work. Adobe keeps forcing the updates but obviously isn't vetting them very well.
-
sgrhill commented
In ID version 17.2.1 occurred this problem. Downgraded to version 17.0.1 gave me back some missing fonts, but the problem isn’t solved.
macOS 10.15.7 + Extensis Suitcase Fusion 22.0.4. -
Steve commented
Updated to 17.2.1 (which fixed my Place Gun Unloaded problem thank you) but some of my fonts are still not visible in Indesign (Lucida Sans TrueType for one). They work on our other designers computer (which wasn't upgraded to 17.2 thank god). They are visible in Suitcase Fusion but missing in Indesign v 17.2.1. Please fix this ASAP.
-
Tom Moulaert commented
UPDATE: it works when I activate the fonts using Suitcase Fusion. However it won't work when it is loaded in Apple Font Book or using a "Document fonts" Folder.
-
Logan commented
The font I have an issue with is Symbol. Need it desperately. I still have 17.2. How can I update to 17.2.1? Update button won't show it.
-
Jürg commented
Thanks for the Upadate Adobe. Unfortunatly, the problem still occurs and we are not able to do our jobs for our customers when needing these fonts. Nothing changed … Try again please, and try it harder and asap.
-
Veikko commented
17.2.1 and still not working... Apple M1 Max, Monterey 12.3.1, Suitcase 22.0.4.
Restarted, cleaned font caches but still doesn't recognise certain fonts. Illustrator and Photoshop does fine. -
Rebecca King commented
Please Fix this, using 17.0.1 is getting really annoying :(
-
KoehlGraphic commented
Same here: Indesign 17.2.0.20 MacOS BigSur 11.6.5 Fontexplorer 7.3.0
Problem-Font (so far) FF Fago Pro OT. Works fine in Photoshop or Illustrator. -
Uwe Laubender commented
Seems a fix is under way with version 17.2.1:
https://helpx.adobe.com/indesign/kb/fixed-issues.htmlInDesign 2022 (version 17.2.1)
Core feature and workflow
Unable to use some random fonts in InDesign.
Place gun is unloaded after first page of a multi-page PDF is placed in frame.@Ayanna: version 17.2.1 is rolled out in a phased manner to different regions of the world.
I'm in Germany and hope that it will be available by the end of April 2022.Thanks,
Uwe Laubender
( ACP ) -
Ayanna Luney commented
When will InDesign 17.2.1 be available?
I'm having the same issues and it is about affect our magazine production. The body copy font has stopped working for one of my artist. We can't just up and change the font.
-
Tom Moulaert commented
Hello Pradeep,
I read that the issue should be fixed with InDesign v17.2.1 (https://helpx.adobe.com/indesign/kb/fixed-issues.html). However if I test it over here, the issue still exists. Attached you'll find 2 screenshots. You can contact me! -
Lee Bullett commented
Upgraded my old iMac last week to M1 Mac Mini and have been pulling my hair out about this dam issue. DINOT.ttf front activated and validated on system - works fine in Illustrator and Photoshop but nowhere to be seen in InDesign !
Wasted several hours looking for a fix, contacted Adobe in the end who informed me about the bug and that I should run an older version (17.0.3)
Adobe - Please fix - and whist you're at it can you also provide Bridge update ASAP :)
Paying top dollar for an app with quite a few issues! :(
-
Kai Sinzinger commented
Hello Adobe! While this error may not be obvious to a large portion of users, it is critical and vital to the trade of type designing and Typographers / Designers in general.
It was impossible for me to even begin to explain this to a customer in an understandable way. Not to mention the hours of research it took to find this error. Again - very critical!!
Please solve this - yesterday
-
Jeffrey commented
Joining in the chorus. Last week I was working on a Silicon Mac Mini with no issues in ID 17.2 and 12.3 (Monterey) This morning I opened up the same files on my home 2021 Intel iMac (also with 12.3) and one font did not show up. Milo MT. My font managers all showed it activated but nothing would bring it back. Even multiple cache cleans, ID resets...etc.. Nothing.
Oddly, my old ID 2019 (left on my 2021 intel for older files) had no problem whatsoever recognizing the font. But I am NOT going to redo an entire issue going to press for one font.
As it is, now I am back to my "Travel" Silicon mac mini which DOES recognize Milo MT. It has a smaller screen, but as I'm on deadline tomorrow this is the only way I'll be able to make it. Not good Adobe.
-
Trine Rask commented
While designing type I discovered that the character gravecomb caused this problem unless I removed the unicode. Jens Kutilek added that if ncaron is present in the font, it is not a problem.
https://forum.glyphsapp.com/t/indesign-v17-2-and-gravecomb/22131/20 -
Justin Penner commented
Please send this link to the dev team as it is probably related: https://forum.glyphsapp.com/t/indesign-v17-2-and-gravecomb/22131/19
I'm experiencing the same problem with fonts that contain gravecomb (U+0300) but not ncaron (U+0148). This is probably a very widespread issue since there would be likely thousands of fonts that are affected by this. I'm also running Catalina and InDesign 17.2
Also worth noting that the same fonts that do not appear in InDesign are working fine in Illustrator.
-
Anonymous commented
Hey Adobe, this critical error is open since end of March. Please hurry up - I guess in Ver. 17.0.1 are other problems you fixed in later versions, so it's not a good solution to downgrade.