Skip to main content

Notepad++ Error for 64bit - ShellExecute failed (2): Is this command correct?

Cause: It happens when you set Notepad++ to "run as" administrator on Windows 7.
Fix: To fix this, you need to manually edit the registry of your system to create a new option in pop-up menu to open files with Notepad++
Step 1 : Delete existing Edit with Notepad++ entry from registry
Go into your registry as an administrator (Run -> regedit) and search for notepad++.exe. Find the key under HKEY_CLASSES_ROOT that has an entry with the Edit with Notepad++ (or maybe Edit with &Notepad++) and delete the entire key. Right click and you should see that you no longer have that option.
Step 2: Create new entry Open with Notepad++
  1. Go to:
    HKEY_CLASSES_ROOT\*\shell
  2. Create a new key under shell called OpenWithNotepad and create a subkey under that called command.
  3. In the OpenWithNotepad key the default string is what you want the context menu item to be called. I set it to Open with Notepad++.
  4. Still in the OpenWithNotepad key, create a new string value called icon and set the value to path-to-notepad++.exe where path-to-notepad++.exe should be the full path, e.g. C:\Program Files\Notepad++\notepad++.exe.
  5. Under the command key edit the default string value and change it to "path-to-notepad++.exe" "%1" where path-to-notepad++.exe should be the full path, e.g. C:\Program Files\Notepad++\notepad++.exe.
Result: When you right click on a file, this option it should now ask you properly for giving Notepad++ admin access to a file.
You still need to go to the properties for notepad++.exe and set it to run as an administrator.
Labels:

Comments

Post a Comment

Popular posts from this blog

What is release, and what is a deployment?

T o understand the concepts and the technical implementation in many tools, you need to know how tool vendors define the difference between a release and a deployment. A  release  is a package or container containing a versioned set of artifacts specified in a release pipeline in your CI/CD process. It also includes a snapshot of all the information required to carry out all the tasks and activities in a release pipeline, such as: The stages or environments. The tasks for each one. The values of task parameters and variables. The release policies such as triggers, approvers, and release queuing options. On the other hand,  Deployment  is the action of running the tasks for one stage, which results in a tested and deployed application and other activities specified for that stage. Starting a release starts each deployment based on the settings and policies defined in the original release pipeline. There can be multiple deployments of each release, even for one stage. ...
Post a Comment
Read more

Considerations for deployment to stages

When you have a clear view of the different stages you'll deploy, you need to think about when you want to deploy to these stages.  Continuous Delivery is about deploying multiple times a day and can deploy on-demand. When we define our cadence, questions that we should ask ourselves are: Do we want to deploy our application? Do we want to deploy multiple times a day? Can we deploy to a stage? Is it used? A typical scenario we often see is continuous deployment during the development stage. Every new change ends up there once it's completed and builds. Deploying to the next phase doesn't always occur multiple times but only at night. When designing your release strategy, choose your triggers carefully and consider the required release cadence. Some things we need to take into consideration are: What is your target environment? Does one team use it, or do multiple teams use it? If a single team uses it, you can deploy it frequently. Otherwise, it would be best if you were a ...
Post a Comment
Read more

Explore Release Pipeline

A release pipeline takes artifacts and releases them through stages and finally into production. The first component in a release pipeline is an artifact: Artifacts can come from different sources. The most common source is a package from a build pipeline. Another commonly seen artifact source is, for example, source control. A manual trigger, where people start to release by hand. A scheduled trigger, where a release is triggered based on a specific time. A continuous deployment trigger, where another event triggers a release. For example, a completed build. Furthermore, a release pipeline has a trigger: the mechanism that starts a new release. A trigger can be: Another vital component of a release pipeline is stages or sometimes called environments. It's where the artifact will be eventually installed. You can have many stages (environments); part of the release strategy is finding the appropriate combination of stages. Another component of a release pipeline is approval. People ...
Post a Comment
Read more