Hi Leo,
I often use the feature above or "PowerShell 7" -> "Open here" but this does not work anymore. I am getting an error "This file does not have an app associated with it for performing tgis action....."
I am running the latest version of DOpus.
Please help.
Thank a lot in advance
Best regards,
Michael
The button might be using an outdated link to PowerShell. Try
CLI DOSPROMPT=noadmin,powershell EXEC=pwsh.exe
If this doesn't work either, try a button with only
pwsh.exe
Those aren't the default commands to do those things in Windows (File Explorer) or Opus.
Do they work in File Explorer or fail there as well?
Do the default commands work in Opus? (You can find them in the Tools menu, or when right-clicking the file display background.)
Hi Leo,
Thanky you for the quick reply.
In standard FileExplorer both work perfectly. So mmmmh. And it only recently worked wit DOpus at well. Probably due to a Windows update? Were ther any changes concerning this?
Best regards,
Michael
And yes, accessing them from the Tools menu, they also work in DOpus. So what is the diffence from accessing them viContext Menu or via the Tools Menu? How can i make them work again?
I couldn't tell you the difference as I don't know what the non-standard menu items run.
As a hunch, have you tried rebooting since you last updated Opus?
Yes, I rebooted the system. Can I somewhere change, what's inside the context menu?
Which context menu is it?
Hi Leo, ist just the context menu that pos up when I right click on a folder. It is different from the context menu i get when right clicking on a folder on standard file explorer. So I gues, ther must be settings within DOpus where one can edit the content and functionality of the contect menu of DOpus
Hi,
Thank you for giving me that advise. As always I'm very cautios when changing something in the Registry. By the way, I believe, that is has to do with DOpus, because the context menus from DOpus and FileExplorer differ. When there is no other solution, I will try your registry entries one by one.
Opus never creates a “PowerShell 7” submenu in the folder context menu, so that is either coming from something else that was installed or is something you configured under Settings > File Types.
If you don’t see the same thing in File Explorer it may just be the way File Explorer hides a lot of context menu items until you select “Show more options” in its initial context menu.
I tried under a folder context menu and you are correct, It fails in DOpus. Mine works under Drive but not folder.
File Explorer opens the command with zero issue but DOpus fails.
Hey Michael, Since I DO have the same issue as you when right clicking on a folder and opening a PowerShell 7 window I played around with it for a bit until I could get it working and here is what it took.
I know you don't like messing with the registry but I went from non opening of the Powershell windows on Folders in DOpus to now it is working fine for Folders.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Folder\shell\Powershell7x64]
@="Open Powershell 7 Here"
"NoWorkingDirectory"=""
[HKEY_CLASSES_ROOT\Folder\shell\Powershell7x64\command]
@="C:\\Program Files\\Powershell\\7\\pwsh.exe -wd \"%V\""
Hi there,
Thank you very much for further investigation in this topic. I tried it out and, interrestingly, the PowerShell 7 entry in DOpus's context menu is completely gone. The PowerShell 7 entry in FileExplorer context menu also changes, for example the Powershell icon is gone.
So, to recap:
a) We have two different context menus. One in DOpus and one in FileExplorer
b) The entries in File Explorer still work. I am talkin about these:
- "Show more options -> Command Prompt -> Open here"
- "Show more options -> Command Prompt -> Open here as administrator"
and
- "Show more options -> PowerShell 7 -> Open here"
- "Show more options -> PowerShell 7 -> Open here as administrator"
c) The same entries in DOpus don't work anymore ??
d) Last time I when I was using them in DOpus they still worked smoothly (can't remember when it was, but DOpus version was 13.21)
My guess is, that some Windows Upgrades are responsible for this. And, although the issue is not THAT essential, the developers of DOpus should investigate in this at least a little bit.
Thank you once more. Best regards,
Michael
Hey Michael,
You can use the following to get rid of the entries you used that I posted and it will return to the way it was.
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\Folder\shell\Powershell7x64]
@="Open Powershell 7 Here"
"NoWorkingDirectory"=""
[-HKEY_CLASSES_ROOT\Folder\shell\Powershell7x64\command]
@="C:\\Program Files\\Powershell\\7\\pwsh.exe -wd \"%V\""
I have the Open Here both with cmd.exe and powershell that work regardless, This issue came to light right after the 26200.8875 update on Win11 for me.
Like you the Powershell 7 menu doesn't work in DOpus, You are correct we are not going to get much help from GP Software on this issue even though the only program it doesn't work in is theirs.
You are correct in that the orig menu for powershell disappears when you add the two entries and you should have a entry in the context menu that says "Open Powershell 7 Here" without a Icon showing. That entry is the one that was added by my two entries.
Have you tried the command/button suggested here?
Hi,
No, I haven't tried it so far, because I have no idea what you mean with the "command button". Can you explain that a bit further, please?
Best regards,
Michael
Have a look at How to use buttons and scripts from this forum.
This is an alternative to the menu in the context menu that functions in the rest of windows correct?
Yes, it's one of a couple of workarounds which you can use to avoid the problem.
As to the issue with the context menu you have, we have never been able to reproduce that from the details in the other similar thread, which suggests there's more to it than just "Opus". Possibly something on your system is blocking Opus from performing the action when it's done in certain ways or by certain processes/exes.
(Assuming it is the same as in the other similar thread. In this thread, I don't think anyone has told us where the particular menu item comes from, or how it's set up. So we can't try to reproduce it without more information.)