Problem starting Photoshop CC and plugins from Lightroom Classic CC

  • 5
  • Problem
  • Updated 7 months ago
I have an issue with Lightroom Classic CC being used with Photoshop and other plugins. Please note that this issue started at some point in the past with the previous version of LR CC and PS CC 2017, but since this is on my laptop (I haven't updated my primary workstation yet) I hadn't gotten around to it.

The situation:
1. I am working on a fully up-to-date Windows 10 laptop with an integrated NVidia CPU.
2. Lightroom Classic CC itself seems to work just fine.
3. Photoshop CC 2018 also works fine as long as it is started separately. The plugins (Nik software) also seem to work just fine when they are started standalone.

The problem:
When I try to edit a file from Lightroom (right-click, edit in photoshop) the following happens:
1. I see LR create a new file (PSD or JPEG, depending on settings).
2. I see the Photoshop splash screen loading and a new button for PS appears on the windows taskbar.
3. In the task manager I see two processes appear: The Adobe GPU Sniffer and Photoshop CC.
4. When Photoshop appears to be done loading, the splash screen disappears. However the Photoshop screen does not load. The button on the windows task bar also dissappears.
However both the GPU Sniffer process and the Photoshop processes remain in my task manager. They never disappear until I end them manually.
5. If I wait for a sufficiently long time, I get this message: "This file could not be edited because Photoshop CC 2018 could not be launched".

This also happens with plugins (like the Nik plugins). Although I do not see a splash screen and (logically) a GPU sniffer program,. I do see their processess running in the task manager.

What I have tried thus far:
1. Signing out and back in to the cloud app.
2. Reinstall of Photoshop, LR and the Nik plugins.
3. I tried turning off the GPU accelleration (in both LR and PS separarely and at the same time).
4. I tried solutions in various threads on this forum, like checking for missing registry keys (but they were already present) or removing/renaming certain files (which also yielded no results, so I reverted back to the clean installation (with Nik plugins).

Other findings:
1. I did find that if I open Photoshop BEFORE I choose 'Edit in Photoshop' in LR, it will work just fine. That's a clumsy workaround for PS but it doesn't work for the plugins. However for this to work I must kill all the
2. I can open the plugins from Photoshop just fine. But they don't work from LR. 

So the issue seems to be that LR is able to start external programs (PS, Plugins), and that their processes start, but that they never actually appear and effectively I'm stuck. 

I cannot get this to work properly. This is very critical functionality in my workflow, since many of my edits go through PS or one of the Nik plugins. I have something of a workaround for Photoshop.

Can someone help me with this issue? Thanks!
Photo of Rene van Glabbeek

Rene van Glabbeek

  • 4 Posts
  • 0 Reply Likes
  • worried

Posted 7 months ago

  • 5
Photo of Rene van Glabbeek

Rene van Glabbeek

  • 4 Posts
  • 0 Reply Likes
Anyone? This has really ruined my workflow...
Photo of Jerusha Pfannenschmidt

Jerusha Pfannenschmidt

  • 1 Post
  • 0 Reply Likes
Same problem here, our other computer doesn't have these issues. Hardware/settings related?

*Update, Since there are hardware differences between our PCs, I started trobleshooting with the hardware. Since one computer is an AMD graphics and the computer without issues is and Nvidia gpu, I updated the AMDgraphics driver and enabled the "use graphics processor" under Edit/Preferences/Performance/Camera Raw

Working fine now and photoshop is opening up the copy with lightroom edits. Hope this it works for you as it did for me.
(Edited)
Photo of Rene van Glabbeek

Rene van Glabbeek

  • 4 Posts
  • 0 Reply Likes

Unfortunately that isn't the issue for, I've tried it with and without acceleration, I'm using NVidia and I've tried various drivers versions (including the latest one). But thanks for the information.


Photo of Laszlo Mag

Laszlo Mag

  • 1 Post
  • 0 Reply Likes
I'm having the same problem. Extremely frustrating!
Photo of Paulo Roque

Paulo Roque

  • 1 Post
  • 0 Reply Likes
Adobe help us please
Photo of Rene van Glabbeek

Rene van Glabbeek

  • 4 Posts
  • 0 Reply Likes

I also have not been able to resolve this thus far, I don't dare upgrade my primary system at this point.


Photo of R D

R D

  • 1 Post
  • 0 Reply Likes
Having a similiar problem. Lightroom Classic works fine. Photoshop cc 2018 works fine. When I open a RAW file in LR Classic and do my editing and then say "edit in photoshop" the photoshop window does not open. If I click on the photoshop icon at the bottom of the screen photoshop window opens and my file from LR is there to edit in PS. It is a workaround for me but just adds an extra step to click on the PS icon each time. I have tried opening PS 1st then LR, also tried opening LR 1st then PS but no difference. The only time LR Classic will open photoshop and display photoshop is if I open LR Classic and PS is NOT open - it then opens PS and shows the screen and file but this is the only time I do not have to click on the PS icon to open the PS screen. I am using Windows 7.
Photo of Jeffrey McPheeters

Jeffrey McPheeters

  • 10 Posts
  • 1 Reply Like
I'm having similar issue on a MacBook Pro 2012 with OS X 10.12.6. Interestingly, it was working just fine for a few days, using Command-E on an image in Lightroom Classic, which then launched and opened in PS CC 2018, or, if PS was already opened, simply appeared as a window or tab in PS CC 2018. But today, when I do this, sometimes the image does open, but sometimes not, and whether it does or doesn't it still creates a modal error box: The file could not be edited because Adobe CC 2018 could not be launched. I haven't installed or changed the services on this system. The only thing I can think of was that yesterday I opened Bridge 2018 and launched some files into PS directly from Bridge instead of through LR and since that time, I'm getting this error/issue.