Skip to content


My feedback

1 result found

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Adobe InDesign: Bugs » Crash  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello All,

    Please update to the latest version of InDesign, Id 13.1 for the fix of the problem.


    An error occurred while saving the comment
    GWA commented  · 

    When Adobe InDesign is working on a file on a Network Drive (NAS) with its source images referenced also on the NAS, if the user saves the file back to the NAS, and Packages the document to the NAS, (Our use case has us packaging multiple documents or packaging the same document a second time under a new destination but also on the same NAS) there is an error that occurs when the user has unsaved data such as changes to the document or photo references in the file - when the user goes to save the document. The program does not save, it freezes and is reported under Windows 10 (1903) task manager as Not Responding.

    It will not be able to recover, so the users' changes *after* packaging the second time but before saving their changes, will be lost. This issue is repeatable and occurs during saving, but also sometimes during packaging.

    A similar issue was reported in March of 2018 here which is reported as solved. This issue needs to be reexamined. The software crashes before it can create a save recovery file and also does not create a crash report. The documents are a mix of PDF and JPEG files and the issue happens generally after 1 or 2 successful packaging attempts.

    I have seen descriptions on the support website of similar issues persisting on Mac OS X





    Therefore this issue is not specific to Mac and affects both Windows and Mac. Not having a save recovery file is a huge hindrance because any save we perform on our files has a random chance of locking out the entire program and losing our work.

    "Do not work off the network drive" is not an acceptable solution or work around.

    This issue has been around for months if not years according to support posts so how about you give it some attention please.

    GWA supported this idea  · 

Feedback and Knowledge Base