P: Lightroom Classic>Edit in PS: Long Delay+Erroneous Error Message opening Ps Beta 2024 25.0

Since I posted the problem in my original thread, I had managed to get LrC to send file to PS23 again WITHOUT installing PS beta. But in the process of me deleting all of the associated director for all LrC, PS23, and PS beta. I think I spot the potential problem that caused the issue. A new shell directory was created for PS24 after the m2257 update, and LrC is trying to divert files to version PS24 thus broke the chain for the Edit In command.

After two days of investigation since the update on Friday, I had backed up my LrC directory, then completed uninstalled LrC, PS23 and PS betal and all of its associated folder in the install directory. Then install PS23 FIRST, and install LrC, and lastly restored my LrC directory from my backup. Things are working as it should and I will wait for the next build on PS beta before I reattempt the install.

For the past two or three days at least, Lightroom does not launch a photo in Photoshop until I request it to do so three or more times. It then gives me "Failure to Launch" messages, several in a row quickly, and when I press ok on each, the photo finally lauches in Photoshop. This was an instantaneous process last week and now it takes a maddenly long time. I am on Mac OS and everything is up-to-date.

Lr Classic no longer sees Ps. I have unistalled and reinstalled both Lr and Ps. No change. Help!

You can see in the image that the Ps version is grayed out. I can edit in Ps by using the Custom editor, but...

Windows 10     Ps 24.7     Lr 12.4

Thanks

you need to install a previous Ps Beta 24.7 in CC

The only way I could fix it is my rolling back to update go to your beta releases, and go to previous version

I've uninstalled and reinstalled both LRC and PS Beta multiple times as well as installed previous versions and none of it has fixed the issue. I am still unable to right click, select "Edit in Photoshop 2024" and have the photo pulled into PS to edit. What else can I do or when can we expect this bug to be resolved?!?!!?

i won't go back to previous version of PS Beta because with the latest version, i've "supress tool" which is very usefull, and this tool doesn not work with previous version of PS Beta.

Hi - I am running Lightroom Classic12.4 in Windows 10. My workflow is to develop in Lightroom Classic, then export files into Photoshop, typically as Smart Objects.

My initial problem came after installing Photoshop Beta, as this workflow stopped working. Under <Preferences> in Lightroom, the <Edit in Photoshop> had defaulted to "Photoshop 2024", which I assume is Photoshop Beta, but although this app booted up, it did not import the file to create the Smart Object.

My next step was to uninstall Photoshop Beta, first in Windows and then in Creative Cloud - for good measure.

Problem now is that under <Preferences> in Lightroom, the <Edit in Photoshop> has blanked out [SEE SNAPSHOT], instead of returning to Photoshop 2023 24.7, which is what is installed. My temporary workaround was to set Photoshop.exe for Photoshop 2023 as the <Additional External Editor> in  <Preferences>, to at least show that the interface at least still worked, although I have since reset this to <not specified>.

To try to fix this, I have un- and reinstalled Lightroom Classic12.4, selecting <Keep> for settings. Unsurprisingly perhaps, the <Edit in Photoshop> is still blanked out.

Before I un- and reinstall Lightroom Classic12.4 with the setting to <Remove> notifications, alerts, interface settings, plugins, and other preferences, I have three questions [1] is this the correct approach to fix this bug or are there any alternatives or other steps needed? [2] Are there any watchouts with removing notifications, alerts, interface settings, plugins, and other preferences in the unistall process? [3] I have not reinstalled Photoshop 2023 24.7, as I assume that this is a Lightroom Classic problem?

Any advice highly appreciated! I am nervous about the uninstall with removed preferences - and digging myself into a deeper hole and still not fixing the bug created by Beta.

Thanks - Ian