Automatic Adobe Fonts syncing of Times New Roman causing local system font conflicts in InDesign

Subject: Bug / Usability Report: Automatic Adobe Fonts syncing of Times New Roman causing local system font conflicts in InDesign

To the Adobe InDesign Product Team,

I am writing to report an ongoing, highly disruptive workflow issue regarding how Adobe InDesign and Creative Cloud handle the default system font Times New Roman on Windows environments.

The Issue:
Times New Roman is a native, pre-installed TrueType font (.ttf) on all Windows operating systems. However, when opening legacy documents, packaged files, or cross-platform files in InDesign, the application frequently flags Times New Roman as a "missing font." Creative Cloud then automatically attempts to sync an OpenType (.otf) variant of Times New Roman from Adobe Fonts.

The Resulting Conflict:
This background synchronization triggers an immediate system conflict. The Creative Cloud desktop app throws a "Font Conflict: A font with the same name is already installed" error because the system already recognizes the native Windows TrueType version. This results in broken links, font substitution alerts, and fragmented style sheets inside InDesign documents.

Requested Action:
InDesign should be intelligent enough to map and prioritize the native, active system version of Times New Roman without forcing a Creative Cloud sync for an identical typeface family. Please refine InDesign’s font-relinking logic so that it recognizes standard local system fonts (.ttf) as valid substitutes for their cloud-based OpenType (.otf) counterparts to eliminate these false-positive missing font errors.

Thank you for your attention to this matter. I look forward to seeing this resolved in an upcoming patch.