Skip to main content
Participating Frequently
October 30, 2025
解決済み

Times New Roman TTF replaced with OTF in InDesign 21.0, causing missing font errors

  • October 30, 2025
  • 返信数 23.
  • 7179 ビュー

All my books (several hundred) are formatted using the Times New Roman TTF font. The new version of InDesign 21.0 changes that to Times New Roman OTF.
Fortunately, version 20.0 is still installed. I know from experience that strange things can happen in updates.. However, the problem with the latest update has also been introduced in that version.
OTF is only available with a licence, which I do not have. 
I would appreciate some help.
Cor van Wijgerden

 

 

<Title renamed by MOD>

解決に役立った回答 Dmytro301376413pen

The same issue with my InDesign 20.5 / Windows 11. I installed Times New Roman from Adobe (https://fonts.adobe.com/fonts/times-new-roman) and replaced the font in the document. It works perfectly now.

返信数 23

Bilel Ayadi
Participant
February 10, 2026

Hello Everyone

 

I have found this as solution:

 

The removal of the folders under these paths:

C:\Users\<user>\AppData\Local\Adobe\Acrobat\
C:\Users\<user>\AppData\Roaming\Adobe\Acrobat\

 

I have as well tested this on 12 different devices, with different “Font” errors.

molebot
Participant
February 17, 2026

Has anyone tried this method? I'm still uninstalling Microsoft updates!--endfragment>!--startfragment>

merritth74903606
Participant
February 17, 2026

I tried this today...to no avail. Same font problems..

Mike Witherell
Community Expert
Community Expert
February 4, 2026

Has anyone on Windows experimented with patching forward to the latest Windows Update to see whether that fixes this TNR problem?

Mike Witherell
Participating Frequently
February 4, 2026

I have the latest Windows Update - I have not had the TNR problem since Windows updated to TNR v 7.11 (I think), which was before this update. However, an external contractor on a Mac has the very same problem with Source Sans 3 when they open my files. I made sure to delete the Google Fonts version of Source Sans 3 from the Windows font folder and activate the Adobe Fonts version of Source Sans 3 before packaging and sending them my file. InDesign at my end is definitely sourcing the font via Font Sync, as evinced by the information in the Search/Replace fonts window.

River7567
Participating Frequently
November 21, 2025

And can we not mark this as "resolved" because the issue isn't resolved, at least not yet. Seems a bit premature...

gosia作成者
Participating Frequently
February 1, 2026

The problem is far from solved; in fact, it's even worse. After the latest updates to Windows and InDesign, repaired files work, but suddenly a message appears saying that there is a conflict with Calibri Bold.
It has been exactly three months since I reported this issue with TNR. 

What a sadness, isn't it?

Mike Witherell
Community Expert
Community Expert
November 20, 2025

As of today, Nov 20, my win11 machine shows that windows patch installed on the 11th of November. Running Windows Update shows nothing newer yet as of today.

Mike Witherell
Participant
November 20, 2025

From what I've gathered, Windows has updated Times New Roman from v7.05 to v7.10 and either InDesign isn't recognizing OpenType or the new font is bugged and has lost OpenType.

 

River7567
Participating Frequently
November 20, 2025

The plot thickens. Thank you for sharing this info! Still not sure which company, Microsoft or Adobe, needs to deploy a fix... I could see this going either way.

Participant
November 19, 2025

Uninstalling Microsoft Security Update KB5068861 made everything all better for me. Not ideal I guess for security reasons, but oh well.

Mike Witherell
Community Expert
Community Expert
November 19, 2025

Anyone have an idea what specific patch version of Windows may be causing this font problem?

Mike Witherell
River7567
Participating Frequently
November 19, 2025

It was the KB5068861 Windows Update for me that caused the problem.

Participant
November 19, 2025

I had the same issue and tried various things. I eventually found that placing older Times New Roman font files (created when packaging another document) into the Document fonts folder at the same level as the INDD file resolved the problem. Hope this helps.

Participant
November 18, 2025

This exact same thing happened to me suddenly but with Segoe UI font.  Every one of my indesign files suddenly changed the font to Segoe UI (OTF).  I have tried several things to resolve this like clearing font caches, reinstalling fonts., but nothing is working.  I have been manually replacing the font in each document, but sometimes a few days later, the file that i updated changes back to OTF.  it's rather frustrating and I can't tell if this is a windows or Indesign issue.  Adobe wasn't very helpful, i don't think they understood what I was trying to explain that the OTF suddenly appeared.  Would love to know  if you resolved this.  

Participant
November 18, 2025

The same issue with my InDesign 20.5 / Windows 11. I installed Times New Roman from Adobe (https://fonts.adobe.com/fonts/times-new-roman) and replaced the font in the document. It works perfectly now.

River7567
Participating Frequently
November 19, 2025

Not everyone can install Times New Roman from the Adobe Fonts Library to solve this. Some folks, including myself, get a vague error that says Times New Roman can't be installed. As far as I can tell, there's not actual issue with the font file(s) itself. Something is creating a disconnect between InDesign and the font files in question, which is throwing the error in InDesign. And, after installing and uninstalling the Windows update mentioned in this thread, I can confirm that specific Windows Update is the catalyst. So, not sure if it's Microsoft or Adobe (or both?) that needs to fix this.

Participant
November 19, 2025

We have several hundred files that are now having this issue, across a shared server with 8 people. We've been replacing fonts on current active files, but it's fairly time-consuming to go back and change layouts on large books.  I hope there's some intent to fix this so we don't spend the next week on it...