Photoshop file associations

[RG631971]

Apparently, this is an old problem that ultimately has never been resolved.  Every time there is a PS update, it somehow messes up the file associations.  For example, beta version will become the default.  In and of itself, this would not be so bad.  The totally irresponsible aspect of it is the user is not able to remake the association desired through normal windows processes.  Regardless of techninque I try that works for all the other software I have checked, picking PS exe from the Photoshop 2025 directory, which its icon properties indicates is the program, still results in a different version running.  Now, never going to tell me that as talented as the programmers at Adobe obviously are, this could not be addressed and fixed.  Seems all other software, or at least the vast majority, is capable of it.  So one logically has to ask what is Adobe leveraging in their approach to again just be a pain for their user base?  This issue has been raised many times in this forum and I have yet to find an answer that solves the problem.  Appreciate any insight anyone can provide.

[D Fosse]

The underlying problem is that when you update - and choose to remove the old version! - that old version is removed after the new one is installed. Sequence matters.

And so the file associations established in the new version install, are broken again when the old one is subsequently removed. It takes the file associations with it on the way out.

This is very easy to avoid in the future. If you decide that you want to remove the old version, do that first, before initiating the new install. Then you will never have any problems. If you have several versions installed, always follow strict version order both ways. Think of it as tennis balls in a plastic tube, open only at the top.

Yes, I agree that this is basically a problem with the CC installer. It shouldn't be a problem to change the order of operations so that it removes old versions first.

[jane-e]

@RG631971 

File associations are controlled by your OS (Windows), not by Adobe. Typically the last installation or update takes over the association.

https://support.microsoft.com/en-us/windows/change-default-apps-in-windows-e5d82cad-17d1-c53b-3505-f...

Many of us update our applications manually so that we have more control over the process.

EDIT: 57 seconds behind @D Fosse — I didn't see his post while typing.

Jane

[D Fosse]

Exactly. The last installer activity, whatever it is, controls file associations. That's the basic principle in Windows.

I don't see that there's any other practical way to do it, so It's probably like that on Mac too.

As long as you take this into consideration, all these problems can be easily avoided.

[RG631971]

Thanks for the effort, but the reality is it (Microsoft help) represents pretty much information not applicable in this case.

Now, it could be the craziness of Windows. Microsoft is even worse than Adobe. Not only do they take an even more invasive approach but their support is even worse and the software flakier.  Sorry, I digress, those are separate issues.

To the point of my previous comment, when I go to choose default apps by file type, a number of graphics programs are listed but not Photoshop 2025. The only other option is look for apps in the Microsoft Store. Set defaults by app provides a listing of Microsoft apps.

If I go into explorer and right click a psd file to "open with" PS 2025 is not in the original listings. However, I can proceed with "look for another app on this pc" and navigate to the app of interest. In this case,

"C:\Program Files\Adobe\Adobe Photoshop 2025\Photoshop.exe"

However, running that executable does not open PS 2025 but another version. Taking the approach described works for any other program. Based on that, it seems pretty clear that Adobe is configuring something, somewhere in their updates beyond what the operating system is doing.

It would seem that Adobe wants to force users to use Photoshop or Photoshop Beta. Which seems kind of odd since I distinctly remember a time when a user could not only install a beta version but previous revisions of Photoshop as well.

In context of your last sentence, I am not certain what you mean by "manually".  I do not use the automatice update feature because of this very issue.  Make it a point not to update the beta version unless there is a regular PS version to update as the "last" update.  The approach seemed to be working until this last update.  Which, at least in my mind, suggests something changed about the update process.