"Edit in Adobe Photoshop 2022" is not transferring photo to Photoshop

[W. Shane Schmidt]

In Lightroom Classic, I am unable to use the Photo>Edit In>Edit in Adobe Photoshop 2022" plug in.  Lightroom Classic will launch Photoshop (usually), but the photo does not make the trip.  I suspect the problem is somewhere with the catalog because Adobe automatically repaired a "corrupted catalog" earlier tonight. This happened after my laptop shut down and restarted in response to a STOP error.  So I presume this is the culprit, but I don't know how to fix it.

I tried going to Preferences and creating another plug in preset in the External Editing tab, but that did not change anything.  

Other external editing plug-ins seem to work fine.

I am on a PC w/Windows 10 and have Lightroom Classic v11.5 and Photoshop v23.5.

Any ideas??

--Shane

[DdeGannes · Accepted solution]

I would try the following, shut down your computer and then reboot.

[W. Shane Schmidt]

That seems to have done the trick...but on the second (maybe third?) try.  In fact -- no kidding -- the hand-off between apps seems to be smoother, faster now.  

--Shane

[W. Shane Schmidt]

Well...it looks like we're stuck again.  Photoshop seems to be the culprit.  I am not keen about reinstalling because I don't want to lose preferences, presets, and the like...plus, I am not especially good at working outside of setup wizards.  Is there a way to force an update -- i.e., reinstall an update -- to see if that corrects whatever issue lurks in the software?

[W. Shane Schmidt]

So I did "fix" this.  I reverted to the previous version of Photoshop 12.4.2 and that seems to have corrected the issue...

[TheDigitalDog]

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. 
Better? 

[W. Shane Schmidt]

The apps are talking to each other again.  I presume it was the shutdown/reboot recommended by Denis.  I had tried that first, however; it is my go-to when things don't work.  I thought the problem might have been more serious since it followed a Windows STOP error shutdown.  Keeping my fingers crossed that the problem was a glitch.

--Shane

[W. Shane Schmidt]

Very frustrating.  The issue is not resolved and it is happening again.  I have uninstalled and reinstalled the software.  Not sure what else to try...