Is this bug related to the problem where IDML files created from InDesign 2025 documents cannot be placed into InDesign 2024 files?     We are getting an error that states "Cannot place this file.  No filter found for the requested operation" ... View more

Is there an extension that disables background exports?  If so, could you please share?  DisableAsyncExports.txt no longer works in InDesign 2025. ... View more

Anyone have an updated workaround that works in InDesign 2025?  DisableAsyncExports worked successfully for us until the new release. ... View more

We just had that happen in our office....AFTER I sent an email to all users to disable the automatic update for InDesign and not install the 2025 version until I notified them that it was ready for deployment.  One user went ahead and updated anyway, then opened and saved a bunch of files in 2025 that can't be opened in 2024, and come to find out there's a bug that we can no longer bypass in the new version.  Sigh. ... View more

Users that rely on workarounds to disable background exporting of PDF files should not update to InDesign 2025.  Those workarounds do not appear to work in the new version.     I keep hoping that the new major releases of InDesign will successfully fix this issue.  But of all things don't remove the one option we had that allowed us to reliably export larger, complex InDesign files to PDF. ... View more

Amen.  Thank goodness the contextual menu pop up can be turned off.  It always is located exactly where you need to be actually working.  Who needs this anyway, when those options and more are nearly always a right-click away when you actually want it.   I agree--the tutorial pop up windows are also ridiculous.  If you want easy access to tutorials for users who do not understand what the HELP menu is for, just put an icon at the top right that can be clicked.  Even worse is when that pop up forces you to click on it to continue working.   ... View more

Just as a follow up--it appears when we get the "cannot save file is damaged error" that we can successfully save the file by attempting to save it a second time.  We're still testing to see if this consistently works, but if anyone else is running into this probem this workaround is worth a try. ... View more

We have been having similar issues for the last few major releases of InDeisgn.  We have a 3-person department that saves to a network share.  All are on Mac.  We have files that we have used for years, as well as new files, that we are inexplicably unable to save, and get an error message that the file cannot be saved.  In Finder, the file shows as having a size of zero bytes.  If we have closed the file already, it cannot be reopened and it's as if it is basically gone.   We can "workaround" by trying to make sure we catch the error before saving, and doing SAVE AS with a new file name.  Unfortunately, we are finding that doing this once is not even enough anymore...so we are getting multiple differently names files for what should be just one.  It's a logistical nightmare, and unacceptable for a product that is this expensive and intended for more than just a single person design shop.   This thread seems to describe our issue well.  Unfortunately I have tried to repair file and folder permissions on the network share and it has not fixed anything.  It does seem like it could be read/write permissions related...but beyond what I have done I have no idea how to fix it.   https://community.adobe.com/t5/indesign-discussions/file-save-issues-on-network-using-indesign-2020/td-p/10901738   All I know is that this has taken what was (in the 2019 version) a highly streamlined, efficient workflow and turned it into something that we now need to presume will add an unpredictable amount of additional time for each and every task we need to complete.  Combine this with the incessant problem of us having to manually find/replace "missing" fonts on thousands of files because Adobe changed the font file type for this font in the Adobe Fonts service, it's enough to make this 20 year veteran in the field consider bagging groceries instead.     Paper or plastic, Adobe?   Thanks, Adobe!   ... View more

I noticed this too.  I had much better results exporting from Adobe Express to a PDF, and then using acrobat to save the JPG / PNG files.   ... View more

Thank you for the reply!  I sent a link to the packaged file in DM.   For others following this issue, packaging the file had interesting results.  When I opened the INDD file from the package, the Museo Fonts were identified as missing by InDesign.  When I opened the IDML file, these fonts synchronized with Adobe fonts (though, each font was listed a crazy number of times in the find font dialog)   INDD   IDML   ... View more

Update:  InDesign 17.1 update has not resolved this issue for me.   ... View more

Also, for anyone researching or experiencing this issue:   I looked at an InDesign file that was one of our original branding templates from 2015.  This file used the Museo Sans Rounded OpenType Type 1 font activated from Adobe Fonts.  As you can see from the packaged instructions from this file from 2015, these fonts were OpenType Type 1 fonts that were synced.       When I opened this InDesign file, Museo Sans Rounded did not show up as missing, and the font synchronized with the Museo Sans Rounded OpenType True Type font on CC.  The difference with this file?  I hadn't used this font within any defined Character or Paragraph styles.  It had just the basic paragraph style applied, with a manual font override.  (See styles on the screenshot?  It's blank, and the style count is 0.)     Compared to the font info panel on a document with the font missing.  The font was applied to 17 styles, and now has (OTF) appended to the end of the font name.  (No, it is not a different font).     This seems consistent with the fact that I can drag and drop creative cloud library assets using this font into a blank document (with no pre-defined paragraph or character styles) and have no font warning.  If I drop the same asset into a document that has the styles defined, the font shows up as missing.   @Anshul_Saini -- are character and paragraph styles related to the missing font issue that has been fixed in the prerelease?  It would be helpful to share information about this bug  with support technicians so they can better determine if a customer's font problem is due to actual Type 1 fonts that are no longer supported, or a bug that is being fixed.  TY. ... View more

Thank you @Anshul_Saini.  I am very much hoping that you are correct that this problem will be fixed once the update comes out.     I have spoken twice with Adobe support on the phone.  They were fairly adamant that my font issue is due to the Postscript / Type 1 fonts being phased out.  They explained that the original Museo Sans Rounded OpenType Type 1 font from CC will no longer work, and that my only option is to find and replace the now missing font in all of my files with the "new" Museo Sans Rounded OpenType True Type font currently on CC.   It seems like there is some conflicting information about this issue, and it's leaving me uncertain about whether or not my problem will be fixed with this update or if I will need to go ahead and replace all these fonts on a large scale.  Is a beta version with this update available for download so I can at least test and know if my problem will be fixed when the update comes out?  What will happen with the files that I've already replaced the fonts in once this release comes out?  TY ... View more

I spoke with Adobe support again.  They again claimed that the old missing font is being discontinued because it was a Type 1 postscript font per this article https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html   According to this, my missing font should still be supported.  I have no idea why the font type needed to change at all.   Fonts activated from the Adobe Fonts library may appear in Creative Cloud software with a file type of OpenType Type 1. This should more precisely display as the file type OpenType CFF. CFF is a compact representation of Type 1 that we will continue to support. We are working with our product teams to clarify this font description and avoid future confusion.   Support said my only option is to find and replace the fonts manually across my entire library of documents. ... View more

We have used the Rounded subset fonts in thousands of files for several years, which were activated and used from the Creative Cloud service from the start.  It appears that the original font was an OpenType Type 1 (postscript) font.     Over the past few weeks, this font now shows up as missing in all our documents, and has (OTF) at the end of the missing font name.  I think this is what you mean by conflicting formats of missing fonts, and how ID will try to help identify the missing font type.   We are able to find and replace the font with the one that is "currently" in use by Creative Cloud.  This is the font info after the change:     The replaced font looks identical in our layouts, so that is not the issue.  The incredibly profound problem is--we have thousands of files that now show the font as missing, and have to find/replace multiple font weights in each of these documents.  This is a font used in our corproate branding and every single file we have created is affected, and it is used witin paragraph styles in every document. ... View more

Actually, the Type 1 end of life notice from Adobe states that fonts activated from Creative Cloud may show up as OpenType Type 1.  They are considered OpenType fonts.  The missing font is OpenType Type 1 per screenshots provided on other replies.  So it does not appear that this font was a true Type 1 that needed replacing?   I'm tired of chasing my tail on this.  All I know is that this font has worked seamlessly after activating from CC for years, until now.  ... View more

For anyone also running into issues with this problem, it may be connected to the reported issue at the following post regarding incorrect identification of font type.  It's at least worth a read, especially combined with the note from the Adobe End of Life notice for postcript type 1 fonts.   https://community.adobe.com/t5/indesign-discussions/opentype-font-marked-as-postscript-type-1-font/td-p/12633363   https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html   ... View more

Also...I'm seeing that this notice exists on the Postscript End of Life page on Adobe.  The missing font was activated several years ago from CC fonts, and shows up as type OpenType Type 1 in InDesign.  This font shows up as a Type 1 font in previously exported PDF files.  After replacing the font again from CC fonts, the type changes to OpenType True Type.   https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html   ... View more

Is this related to my issue with a font activated from Creative Cloud that is now showing up as missing?  We have a font that has been activated and used for years from CCC, whose name has suddenly changed to have an (OTF) at the end of it in my InDesign documents.  This font now shows up as missing in InDesign.  The font is still available from Creative Cloud.  If I replace the font with the one available on Creative Cloud, the font type changes.   Please see font info from the missing font, the font info on the replaced font, and a screenshot of InDesign that shows that there are OpenType options available on the font that is missing (suggesting it may have originally been an Open Type to begin with)? ... View more

Okay, I looked at the font information panel in InDesign for the missing font.     I was incorrect that it was a True Type.  It was a Type 1 font.  They have replaced it with an OTF, and InDesign now shows it as a missing font.  I still have the same problem.   What reasonable, time saving option exists to now update this font across thousands of files?  And seeing as our other major branding font is still in the Adobe system as a Type 1 font, is this all going to happen again when they get around to that font?   It's not like we have a single book, or a single edition that will just need to use the new font going forward.  We have a vast catalog of information saved as individual files.  Each individual file has layers whose visibility is turned on or off to display customized information when placed into another InDesign document.  So when we make a presentation for a client, we place several dozen linked files in it with custom layer visibilities--each one now having this missing font.  Since a book file doesn't allow this layer visibility modification, or overlaying custom information over a stock asset, we can't operate using this as a workaround. ... View more

I looked at the font info for the missing fonts in InDesign (see screenshot).  It looks like the missing font is an OpenType Type 1 font.  The missing font originated from Creative Cloud fonts, NOT from any other 3rd party.   Until this problem started, the font name was Museo Sans Rounded--without the OTF suffix.  This font name appears to have changed across thousands of files at the same time   I did a find/replace on the missing font with the "new" version of the font available from Adobe.  I took a screenshot of the font properties post-replace.  The Font Name and Type are different.  The PostScript name and font version is the same.  The same font was already replaced in two linked graphics in the document, and shows up on the list as MuseoSansRounded-500.     I then opened up a PDF exported using the same fonts / styles from a few months before the problem began, and attached a screenshot of the font properties from the PDF.  We were successfully able to embed this as a Type 1 font a few months ago with no problems, and we have made no changes to fonts on our end. ... View more

The font was activated and synchronized from Creative Cloud for our entire team, just like the other primary font that we use in our branding.  I'm just going based on what Adobe Support said in our call, and both the tech and floor manager said that other users are also reporting this problem and they have put in requests to the product development teams to find a solution for it.  They attributed it to the phasing out of TT and PS fonts, and they mentioned some fonts were affected due to copyright reasons, but it sounded like this was not very common.   I did more troubleshooting last night.  For years, this font appeared in the Character panel in InDesign as Museo Sans Rounded.  Since this problem began, the font name in our existing files now shows up as Museo Sans Rounded (OTF).  We did not do anything to change the name of this font.  This name change seems to be why the software can't find the font--because it doesn't exist.   We have used this font in multiple CC shared library assets, which have been used countless times over the past several years by our team without problem.  If I drag and drop one of these assets into a previously created file, the asset looks for Museo Sans Rounded (OTF) and the font shows up as missing.  The paragraph and character styles in the existing documents are now looking for Museo Sans Rounded (OTF) and can't find the font.  If I drag and drop this SAME asset into a new blank document, it looks for Museo Sans Rounded, and no font is missing.  The paragraph styles associated with the asset were added to the styles panel and look for the correct font.   So, I went into our template and deleted ALL character, paragraph, and object styles in our template file, saved and closed it, and made a new document from the template.  Dragging the CC library asset into this file now works as expected--it is looking for Museo Sans Rounded, and no fonts are missing.  The styles that were associated with the library asset were added to the paragraph and character styles panels and point to the correct font.   This doesn't solve the problem with all our existing documents though, and I'm still seeing no other way to fix the existing documents without doing find / replace font manually within each.   ... View more

I was hopeful that you were on to something here with the version of InDesign and we could just roll back.  We're on 17.0.1 so it looks like this version shouldn't be having this problem.   We've been running quite awhile on Mac OS Catalina, and the problem just started in December.  This seems to be tied in somehow to CC fonts.  All the other fonts we had showed up as missing initially too--I had to deactivate ALL fonts on CC and reactivate them one by one through InDesign as the document called for them.  All the other fonts reactivated with that one step in all documents--except the ones with this OTF suffix.   I'll look into the FindChangeByList script and see if that helps with anything.  The book option may help in some cases, but since we aren't using books by the time the documents were all added it might not be much of a time saver.  Thank you for your suggestions! ... View more

The information about the problem being caused by changes with True Type fonts came from Adobe support, which was confirmed by the floor manager while I was on the call.     This font was activated from Creative Cloud fonts from the start, and it is universally showing up as missing.  Whatever has happened, it is not a change that we initiated on our end. ... View more

Bill—thanks for the tip about the ‘winter’ hour.  That wasn’t what threw us off before, but we change our clocks locally next weekend.  I’ll keep this in mind if the problem comes back next week. Thanks Bob for helping to narrow down the source of the problem! ... View more

Thanks for all these suggestions! I actually tried to work with the foreground/background export idea before going file by file through my linked assets.  It was just too weird that the file could generate a PDF only in one circumstance--a bad font or link should be bad across the board. What I found was that there is a way to disable background exports and force InDesign to process the export in the foreground (like it used to way back).  I followed the instructions at the link below and exported the file directly from the network file to a folder on the network and it worked perfectly! Seems like a hiccup in the background export process, at least with longer complex files.  Hopefully posting the "solution" here helps someone else. Background tasks won't cancel/load ... View more

We have no hyperlinks in the file, just linked documents. However, I've narrowed down some information regarding the export error.  FYI, we work off of a network (I know, not "supposed" to).  WITH INDESIGN FILE SAVED ON NETWORK EXPORT TO PDF:  Crashes PACKAGE w/PDF CREATION:  Successfully exports all fonts, links, INDD, IDML.  Crashes on the PDF creation. WITH INDESIGN FILE ONLY (NOT LINKS) SAVED ON DESKTOP EXPORT TO PDF:  Crashes PACKAGE w/PDF CREATION:  Successfully exports all fonts, links, INDD, IDML.  Successfully exports PDF file. I have been able to re-create these results several times.  Why would it be able to create a PDF via Package but not via Export-->PDF?  Is the PDF process any different using Package? Thanks! ... View more

Thanks for all the suggestions! Yes, idml is what I meant.  I am able save it as an .idml file, but the file won't open after saving. There is one page linked in this document that seems to be causing the problems.  When I remove it the document exports fine.  InDesign used to show each linked file being processed as the PDF exports, but now it looks like the background tasks panel doesn't do that?  If I could see that I would be able to narrow down the culprit.  For now I'm going to try isolating the links to see if one is causing the problem. I really don't know what the error message means: (the entire report is at the pastebin link above) Exception Type:        EXC_BAD_ACCESS (SIGSEGV) Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note:        EXC_CORPSE_NOTIFY Termination Signal:    Segmentation fault: 11 Termination Reason:    Namespace SIGNAL, Code 0xb Terminating Process:   exc handler [0] ... View more