Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Creative Cloud app allows me to upgrade from PS 26.10.0 to PS v27.1 but not to PS v27.0

New Here ,
Nov 26, 2025 Nov 26, 2025

I'm currently using Photoshop v26.10.0 and wish to update to Photoshop v27.0.  In the Creative Cloud app, my "New updates" list includes Phototshop v26.11.2 and Photoshop v27.1, but not Photoshop v27.0.  (Updating to v27.1 works and migrates my preferences, but that version of Photoshop has a bug that prevents me from using a specific feature that I need, hence my interest in updating to v27.0.)

Within the Creative Cloud app, I can find "Older Versions" of PS, including 27.0, but when I install from that panel, none of my preferences/actions/presets are migrated, and my PS 26.10.0 is not removed. 

Is there a way to upgrade to v27.0 that will migrate my preferences and remove v26.10.0?  

TOPICS
macOS
201
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Nov 27, 2025 Nov 27, 2025

There should always be options in the installer dialog to migrate preferences and remove older versions. That is the general update dialog and not dependent on version. Look again.

 

But first of all, I would check that the bug you're referring to isn't in reality caused by migrating preferences. 

 

Preferences are rewritten on every application exit and are prone to corruption by irregular shutdowns. Small errors will accumulate over time and carry over. Here's the thing: A new version will hav

...
Translate
Adobe
Community Expert ,
Nov 27, 2025 Nov 27, 2025

There should always be options in the installer dialog to migrate preferences and remove older versions. That is the general update dialog and not dependent on version. Look again.

 

But first of all, I would check that the bug you're referring to isn't in reality caused by migrating preferences. 

 

Preferences are rewritten on every application exit and are prone to corruption by irregular shutdowns. Small errors will accumulate over time and carry over. Here's the thing: A new version will have partly new code, and so latent errors may unexpectedly surface to cause problems in the new version. Corrupt preferences usually look like application bugs and are often mistaken for that.

 

I always advise against migrating preferences for this reason and I never do it myself. Just make sure to save out your custom actions, brushes etc. first.

 

Also, be careful about removing old versions. The installer removes the old version after the new one is installed, which may break file asoociations. Leave it, and remove it later when you're confident everything works as it should. When you do, start with the newest and go backwards. Then reinstall the one you want. This is the safe procedure to avoid all problems with file associations.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 28, 2025 Nov 28, 2025
LATEST

Thanks, this is very helpful.  Much appreciated.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines