Photoshop CS6: "Cannot open file type 'Adobe Photoshop File'" on MacOS right after installing ?

  • 1
  • Question
  • Updated 6 years ago
  • Answered
  • (Edited)
Hi there. Yesterday, I was using Photoshop CS5 to view a PSD on my Macbook Pro.

Today, I got a new computer (Mac Mini) and downloaded the trial for Photoshop CS6 Extended. When I went to open the same file that worked fine on my MBP, I received a warning that the program "cannot open file type 'Adobe photoshop file'".

I dismissed the warning to allow the program to open the file, and it opened and seems to be working fine. All my layers are accessible, nothing has rasterized, etc.

I am wondering two things:
1. Has anyone else encountered this warning?
2. Is this something I need to worry about?

Thanks!
Photo of Allie

Allie

  • 3 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of TinaC

TinaC, Tier 3 support engineer

  • 133 Posts
  • 11 Reply Likes
Does this happen with all PSD files? What happens if you try to open another file type? Where is the location of this file? If it's on an external drive, can you open a PSD on your internal drive?

Was there anything more in the error message?
Photo of Allie

Allie

  • 3 Posts
  • 0 Reply Likes
Thanks for responding so quickly. So far, no other problems. As soon as the first PSD opened, I immediately opened a second PSD from the same location (dropbox) and it opened with no problems at all, no warnings, nothing.. Since it's a brand new computer, I don't have any PSDs locally.

No, there was nothing more in the error message to my recollection. I wish I'd taken a screen shot of it to attach, but didn't think of it until after I dismissed it.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
My guess is that MacOS hadn't read the program metadata and cached the file associations when you first tried it.
After launching (and a little wait) the OS should have all the file type associations cached (remembered).
Photo of Allie

Allie

  • 3 Posts
  • 0 Reply Likes
Understood. I haven't had the problem since. It was probably the caching like you said. It's funny, I work in web development but hadn't considered local caching.

Thanks, Chris and TinaC.