Copy link to clipboard
Copied
Issue Description:
We are experiencing consistent crashes when opening InDesign files stored on an Azure File Share. The issue occurs for multiple users, and only when accessing files from the File Share location. When the same files are copied locally, they open without any problem.
Environment Details:
InDesign Version: 20.5
Operating System: Windows 10/11 (please adjust if needed)
Storage: Azure File Share (SMB)
Sync method: Files accessed directly from network storage (not OneDrive synced)
What We’ve Tried:
Copied files locally → :white_heavy_check_mark: No crashes
Restarted devices and InDesign → :cross_mark: Issue persists
Checked local network connectivity → :white_heavy_check_mark: Stable
Tested with multiple files and accounts → :cross_mark: All crash when stored in File Share
Impact:
Users are unable to work on shared InDesign documents stored in Azure File Share, affecting collaboration and productivity.
Copy link to clipboard
Copied
Thanks for sharing the details. InDesign does support working with network-based storage like Azure File Share, but depending on your network setup, access permissions, or latency, unexpected crashes can sometimes occur. As a temporary workaround, please try copying the file to a local directory (such as your Desktop), working on it there, and then manually moving it back to the Azure File Share after saving. This helps avoid corruption or instability caused by network communication issues. You can also review this enterprise article for more details: https://adobe.ly/47H3pf8.
That said, the latest version of InDesign is v21.0. Please update to that version and see if the issue persists. When the crash occurs, do you see the Adobe Crash Reporter dialog box? If yes, please submit the crash report and share the email address used while sending it via DM on the community, so I can check the logs. You can find the steps here: https://adobe.ly/4oswrGt.
Lastly, it would be helpful if your IT or the network team could check the Azure network logs during the crash to identify any access or sync interruptions.
Looking forward to your update.
Abhishek
Find more inspiration, events, and resources on the new Adobe Community
Explore Now