-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error (shellExecute) when trying to open files from context menu #8786
Comments
Bump! |
Ok, I can confirm this is still an issue in Notepad++ 7.9.4. Debug info:
|
Apparently this is a widespread issue, judging by this search: Google: "ShellExecute failed (2): Is this command correct?" There are 10 pages of people asking for help getting this issue. There is also duplicate issues on the tracker (but not better than this one, and mostly focussed on workarounds, not getting it fixed properly in Notepad++). How is it not fixed after so many years? @donho |
Duplicate of #4368. |
Duplicated this behavior on install from internal v8.4.7 updater to v8.4.8. Had not seen it before in over ten years of use. Uninstalled and reinstalled clean -- and my desktop rearranged itself, but the NP++ behavior remained. Did a system restore, which put back v8.4.7 (and my carefully curated desktop), and the behavior persists. (and, oddly enough, I just discovered, drag-n-drop no longer works on the desktop, but does elsewhere???) What would it take to reopen this issue? Bug data after first install: Bug data after system restore: |
Due to (ah, I can see this whole issue is predicated on admin mode...ugh). |
Addendum: Uninstalled it all w/Revo uninstaller, took out all associated files and registry entries. Reinstalled from DLed v8.4.8 installer. Original issue remains. Will not open file from right click menu w/ 'run as admin' active on either the exe or the shortcut. Make it inactive, works just fine -- but holy cow, half (maybe more) of the files I work on need admin permissions. This is, to be mellow about it, highly annoying. |
The problem is, they don't care Apparently they are feature focused, not QoL focused. Even no matter the high amount of duplicates/people asking about it |
No, I ensure you that it's not true. With the deployment of Windows11 everywhere from Microsoft, I think it's better to abandon the old explorer context mechanism (NppShell.dll), and I'm considering using another solution instead - with which it works with normal or admin mode. However, with admin mode people will complain about another issue - there'll be always a prompt to ask user if he/she wants to launch Notepad++ in Admin mode for each time you use "Edit with Notepad++", even an instance of Notepad++ in Admin mode is already there. But such issue won't be solved as I see no solution for it. |
Description of the Issue
If you run Notepad++ in compatibility mode ("Run as Administrator"), you may get the following error when you try to open files using the Windows context menu (that is, right click the file and select "Edit with Notepad++"):
ShellExecute failed (2): Is this command correct?
"C:\Program Files\Notepad++\notepad++.exe"
"C:\Users\Username\Desktop\textfile.txt"
The window name is "Notepad++ Extension: Error" and the window icon is Windows Explorer icon. Even though this happens for me with a clean installation of Notepad++, so without any non-standard extensions or plugins.
Screenshot of the error:
![error](https://user-images.githubusercontent.com/61570793/91826341-bad67b00-ec3d-11ea-8b1b-7513ad9f6f90.png)
Steps to Reproduce the Issue
Expected Behavior
Notepad++ should be able to open files in this manner despite running itself as Administrator. Some people intuitively want to run editors like Notepad++ as admin, to avoid errors of a lack of file access or locked files for which Notepad++ asks the user to restart with administrator privileges, in order to be able to save it. These advanced users might enable this setting in compatibility tab, no matter how effective it is, and will now run into this unnecesary error, and will probably have a hard time figuring out the reason for their error.
Actual Behavior
Notepad++ couldn't open a file using the context menu
The text was updated successfully, but these errors were encountered: