Skip to main content
Participant
January 4, 2026
Question

Photoshop 27.x OpenVINO DLL conflict with third-party plugins when opening files via Recent

  • January 4, 2026
  • 3 replies
  • 169 views

Summary:
Photoshop 27.2.0 (Windows 11) exhibits a plugin compatibility issue related to OpenVINO DLL load order that is dependent on document-open workflow.

Description:
When using Photoshop 27.2.0 on Windows 11 (Intel Core Ultra 7, NVIDIA RTX 5060), invoking certain third-party plugins that depend on Intel OpenVINO (e.g., Luminar Neo) can fail with “Entry Point Not Found” errors if the document is opened via File → Open Recent or launched from Lightroom → Edit in Photoshop. The same plugin loads successfully when Photoshop opens a fresh document via File → Open.

Process Explorer shows that in failing cases, Photoshop initializes its ML/OpenVINO components during document rehydration, causing the plugin to resolve openvino_*.dll from the Photoshop application directory rather than its own runtime, resulting in an ABI mismatch. Clearing Photoshop’s Recent Files resets the behavior. This appears to be a timing-dependent DLL search-order conflict during plugin initialization.

872783iA0CB3617B4D68B29.jpg

Repro steps:

1. Launch Photoshop

2. Open a document via Open Recent or from Lightroom (edit in PS)

3. Invoke plugin → error

4. Clear Recents, open same file in PS via File → Open → plugin loads correctly

3 replies

creative explorer
Community Expert
Community Expert
January 8, 2026

@Tony5CEA I can't tell if you are being super-sarcastic or not, because the last few steps, you got the plugin to work?

m
Tony5CEAAuthor
Participant
January 8, 2026

No sarcasm intended, apologies for that. Let me try to be clearer, since I still see the issue but it's dependent on order of operations.

What I observe is that in the case where I (1) Launch Photoshop, (2) Open a new (never-opened) file, and (3) Launch Luminar Neo as a filter -> then No OpenVINO dll errors occur on launching the Luminar Neo plugin.

 

In the case where I (1) Launch Photoshop, (2) Open the same file via File → Open Recent, then (3) Launch Luminar Neo as a filter -> then Photoshop throws a large number of OpenVINO dll “Entry Point Not Found” errors.

 

A third case is where I then (1) Clear Photoshop Recent Files, (2) Open the same file as above via File → Open, and (3) Launch Luminar Neo -> then No OpenVINO dll errors occur on launching the Luminar Neo plugin.

 

This is reproducable. And I also see that if I pass a file off to Photoshop from Lightroom (Lightroom → Right-click → Edit in Photoshop) and then invoke Neo as filter, this also generates a slew of openvino dll entry point errors. I'm guessing this may have to do with when photoshop vs the plugin try and initialize the OpenVINO stack on my system. And just for completeness, my system is configured with dual GPU, an Intel iGPU and a discrete NVIDIA RTX 5060 GPU.

 

 

 

 

creative explorer
Community Expert
Community Expert
January 8, 2026

@Tony5CEA thanks for the clearer picture. Definitely a bug. Wowza, dual GPU?!

I was wondering if you can just push Photoshop on one of the GPU, just make it discrete NVIDIA RTX 5060 GPU (sorry big fan of NVIDIA). 

m