Copy link to clipboard
Copied
I have Lightroom classic release 12.2.1 and Photoshop release 24.3.0 installed on windows 10. When I try to edit an image in photoshop from Lightroom Photoshop 2022 (which is also installed) opens. How can I make LR open Photoshop 2023?
Originally everything worked as it should (PS 2023 was linked) but after I installed PS beta, and later deleted it, this started happening.
Uninstalling and reinstalling Ps 2023 should fix it.
No need to re-install LR, as it turned out. Just re-installing PS did the trick. Thanks for answering.
Copy link to clipboard
Copied
Uninstalling and reinstalling Ps 2023 should fix it.
Copy link to clipboard
Copied
Indeed it did fix it. Thank you (Tusen takk 😀)!
Copy link to clipboard
Copied
When the 'link' between Lightroom Classic and Photoshop has issues, one of the first things to try is this:
1. Use the Adobe Creative Cloud application to uninstall both Photoshop and Lightroom Classic and when asked, keep preferences.
2. Install Photoshop first, then Lightroom Classic. The order is what is very important here.
Better?
Copy link to clipboard
Copied
No need to re-install LR, as it turned out. Just re-installing PS did the trick. Thanks for answering.
Copy link to clipboard
Copied
Adobe should use their A.I. skills to make sure this nonsense never happens. When I tried to uninstall Ps, it complained the Lrc was open. Closed it and it was still complaining several minutes later. Decent software developers would have closed down the phantom Lrc. Or let you correct the default program for editing in Lrc. And why doesn't Adobe provide an answer, rather than the users who are doing their job for them?
Copy link to clipboard
Copied
what about us that our iOS can't download the new version
Copy link to clipboard
Copied
If you open Preferences from the Edit menu, on the External Editing tab is an option "Photoshop version" where you can switch between all the versions of Photoshop you have installed. No need to reinstall anything.
Copy link to clipboard
Copied
There's a long standing, well docuimented, acknowledged bug with that - which is why the "reinstall" workaround exists.