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.

Comments

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. ...

Enable Trace on Dynamcis 365 on premise using PowerShell

Enable trace settings through Windows PowerShell Note These changes made in Windows PowerShell do not update the Registry. These changes update the DeploymentProperties and ServerSettingsProperties tables in the MSCRM_CONFIG database. Register the cmdlets 1.      Log in to the administrator account on your Microsoft Dynamics CRM server. 2.      In a Windows PowerShell window, type the following command: Add-PSSnapin Microsoft.Crm.PowerShell To obtain a list of the current settings, type the following command: Get-CrmSetting TraceSettings Set the trace settings 1.      Type the following command: $setting = Get-CrmSetting TraceSettings 2.      Type the following command to enable tracing: $setting.Enabled=$True 3.      Type the following command to set the trace settings: Set-CrmSetting $setting 4.      Type the following command...

Delivery cadence and three types of triggers

Both the release and stages make use of triggers. There are three types of triggers we recognize. Continuous deployment trigger You can set up this trigger on your release pipeline. Once you do that, your release pipeline will trigger every time a build completes, and a new release will be created. Scheduled triggers This speaks for itself, but it allows you to set up a time-based manner to start a new release—for example, every night at 3:00 AM or 12:00 PM. You can have one or multiple schedules per day, but it will always run at this specific time. Manual trigger With a manual trigger, a person or system triggers the release based on a specific event. When it's a person, it probably uses some UI to start a new release. When it's an automated process, some events will likely occur. You can trigger the release from another system using the automation engine   Navigation Traditional IT deployment cycle What is Continuous Delivery? What is release, and what is a deployment? Azure...