Step 3. in the first post above doesn’t require installing any other pdf software. No change in default handler of .pdf files is needed. There simply needs to be more than 1 program to open .pdf files (other than SumatraPDF) in Directory Opus Open With menu. Add Notepad for example and try opening .pdf file using SumatraPDF. Error will be produced.
Edit Windows registry and make SumatraPDF the one and only handler of .pdf files, so there is no Directory Opus Open With menu, just the Directory Opus Open With… command and SumatraPDF will produce no errors.
I’ve tested Context menu - Open With - SumatraPDF behavior on stock Windows 7 Explorer and 3rd party explorer replacements (Total Commander, XYplorer, xplorer², Q-Dir, Directory Opus) and only Directory Opus produces the mentioned Context menu - Open With - SumatraPDF error. Therefore, one could say that it’s up to the developers of Directory Opus to fix this issue.
However, I’ve also tested Directory Opus Context menu - Open With - SumatraPDF alternatives behavior with Adobe Acrobat Reader DC, Adobe Reader XI, Foxit Reader, PDF XChange Editor, Nitro Pro and only SumatraPDF produces this error.
Moreover, on this type of error SumatraPDF always opens 3 tabs.
Let’s say C:\test.pdf is opened.
In the first tab the actual test.pdf file is opened successfully.
In the second tab *Error loading C:* is displayed
In the third tab Error loading C:\Windows\system32\test.pdf is displayed.
SumatraPDF opens .pdf file in one of the tabs successfully, therefore I assume Directory Opus invokes SumatraPDF with a full path of the file.
There is something unique between Directory Opus Open With menu (when there’s more programs than SumatraPDF alone) and SumatraPDF behavior.
@kjk Should I contact the developers of Directory Opus to address this issue?
It would be great if we could avoid that ping pong game scenario between developers where both sides see the ball being on the opposite court.