Unable to open files after moving them to external drive

Hi @PH_Red,

Hope you're doing well!

We would like to follow up on your issue. Are you able to resolve the issue? Please feel free to update the discussion if you need further assistance.

We would be happy to assist you. 

Thanks,

Harshika

Just on a whim, worth a try: start a Terminal window and have a look in the /Volumes directory. There is a long-standing bug in InDesign where stray, abandoned volume mounts cause all kinds of trouble. Clearing the stray entries from /Volumes would then fix the issue.

What version of OS are you using? There has been an issue (especially since Monterey) where Apple needs you to specifically allow access to external disks. Check your System Preferences > Security & Privacy > Full Disk Access and make sure your Adobe apps are listed there. If not, add them.

@PH_Red

Can you rewrite your message - fixing all the typos? 

What exactly are you doing - and how - and when exactly do you get an error? 

But if you have an error when opening INDD file from external drive - after saving / copying it there - do you flush cache / eject your drive - before disconnecting it?

@PH_Red 

Adobe does not support saving to or opening from a network or external drive. They recommend that you copy the files to your hard disk first.

InDesign 10.5 (CS4) was released 25 years ago in 1999. If that wasn't a typo, it will run best on the on an older computer and macOS that supports it.

Jane

How exactly are you moving these files and like Barb I'd also be interested in what 10.5 really should be. We also need to know what Mac operating system you're using.

10.5? Is that a typo? Did you mean 19.5?

19.5 is the beta version of InDesign. Beta indicates the software is still under development, and as a best practice, you want to play with a beta to look for problems but not use the beta (any beta) for real work. I'm not saying that's the issue here—I haven't seen this reported elsewhere—but does working in 19.4 (the latest official release) or 18.5.3 (the previous official release) eliminate the issue? That would pinpoint the beta as the problem. 

If not, please come back and provide some additional details, including a screen shot of the error message.

~Barb