[quote="leo"]Is that when double-clicking the shortcuts inside Opus, or only from outside of Opus?
What happens when double-clicking the same shortcut from Windows Explorer / File Explorer?
Is double-clicking folders working OK, and the problem is only with shortcuts to folders?[/quote]
Hi Leo
The errors happens when I double-click the shortcuts inside Opus
When double-clicking the same shortcut from Windows Explorer, it works fine.
The problem is only with shortcuts to folders, no problems with double-click folders.
Unfortunately, I can't see anything in them which looks likely to cause the issue. There are differences between your registry settings and mine, but of the ones that seem potentially involved, re-creating them here did not cause the problem to appear here. Either the problem is not in the registry itself or it's quite subtle and I am missing it.
Here are some other things worth trying:
[ul][li](Assuming Opus Pro:) If any scripts are enabled under Preferences / Toolbars / Scripts, try turning them all off & clicking OK, to see if they are involved.
[/li]
[li](Assuming Opus Pro:) Set Preferences / Miscellaneous / Advanced: dlldir_security = False, click OK and then reboot. (If this does not help, please reset it to True and reboot again.)
[/li]
[li]If neither applies or helps, please download and run Microsoft's Process Monitor tool.
While Process Monitor is collecting data in the background, double-click a shortcut to trigger the problem.
Then go back to Process Monitor and use File > Save and choose Native Process Monitor Format (PML). The output will be large, but should zip to something quite small.
Please email the zip to me and I'll see if it reveals what's happening. It's possible a shell extension is involved, which this will reveal, but either way it should tell us what is trying to be accessed and where to look to fix things.[/li][/ul]
Thanks for the procmon logs. I think I've found the problem, and it is in the registry after all.
Please open regedit.exe and go to HKEY_CLASSES_ROOT\lnkfile\shell (that's LNKFILE with an L, not INKFILE with an I).
Below there, you should see Chemtable with name "Uninstall completely with Reg Organizer" and pointing to Y:\23\Applications\Utilities\Uninstaller\Reg Organizer [realtime]\Portable2\RegOrganizerPortable\App\Reg Organizer\RegOrganizer.exe (which does not exist).
Delete the entire Chemtable branch and things should start working again.
Full path of the thing to delete: HKEY_CLASSES_ROOT\lnkfile\shell\Chemtable
Thank you so much, your instructions really help to solve the problem.
I guess you have opened the report of Process Monitor, and you find that the PATH NOT FOUND in the Result column, which indicates the "Y:\23...RegOrganizer.exe" does not exist and which causes the error. Is my guess correct?
[quote="leo"]Thanks for the procmon logs. I think I've found the problem, and it is in the registry after all.
Please open regedit.exe and go to HKEY_CLASSES_ROOT\lnkfile\shell (that's LNKFILE with an L, not INKFILE with an I).
Below there, you should see Chemtable with name "Uninstall completely with Reg Organizer" and pointing to Y:\23\Applications\Utilities\Uninstaller\Reg Organizer [realtime]\Portable2\RegOrganizerPortable\App\Reg Organizer\RegOrganizer.exe (which does not exist).
Delete the entire Chemtable branch and things should start working again.
Full path of the thing to delete: HKEY_CLASSES_ROOT\lnkfile\shell\Chemtable[/quote]