Photoshop BETA hijacks all associated file types in Windows 10

[Red Point]

I installed Photoshop beta on Windows 10, which I regret insofar that all my file types are now hijacked by Beta. All my Photoshop files are now associated with beta. When I click any PSD file, beta opens. I cannot change file association in Windows 10, as Windows doesnt "see" regular Photoshop and wants to open the Windows App Store (for all other filetypes besides PSD normally associated with Photoshop).

Any ideas how I can have Beta installed without this Photoshop filetype nightmare?

[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.

[Pete.Green]

Hi folks,

Apologies for the trouble with file associations during install and beta installations. We've made some changes here, so with this latest release and hopefully going forward you shouldn't run into any more file association issues when installing new versions, beta versions, or uninstalling. Hopefully this fixes it for you!

Please let us know if there are any strange behaviors you notice and we can further look into it.

Cheers,

PG

[Ben J. Cote]

Oh, I absolutely agree with your comment! Adobe is just doing an amazing job here. Of course, it's perfectly reasonable for their installer to mess with file associations—who doesn't love their workflow being completely disrupted? And with the incredibly reasonable subscription prices we all gladly hand over each month, it’s not like they have the resources to hire a single person to address this. Clearly, they’ve mastered the art of ignoring customer feedback. Bravo, Adobe, bravo!

[Nancy OShea]

"it's perfectly reasonable for their installer to mess with file associations..."

==========

Free BETAS are incomplete apps.  Basically, you're getting a fledgling test product, not the real deal. 

For this reason, I don't put BETAS on my production machine unless I'm fully prepared to deal with the consequences. It's best to keep BETAS on a spare device where it won't interfere with normal workflow.

Hope that helps.