Notepad++ 8.5.7 and "ExplorerCommandHandler" used to register the Context Menu

Question

A company complained to me about Notepad++ version 8.5.7 and packaging it into MSIX.&nbsp; It seems that the vendor changed how the native install registers their context menu.&nbsp; Rather than registering under a ShellEx key, it uses a Shell key and a registry value named "ExplorerCommandHandler" that points to the COM InprocServer handler.
&nbsp;
I have never seen this done before and documentation on it is hard to find, but the native install works flawlessly.&nbsp; Meanwhile the MMPT ignores it because it is a shell verb without a command subkey.&nbsp; This case should probably be handled by the MMPT.
&nbsp;
For those reading this, TMEditX 3.5 also does not detect this situation, but it is something I'll put on the list for later this fall.

timothy_mangan · Answer

Roger_Wernli&nbsp;
&nbsp;
The approach to fix the problem by turning the shell extension into a traditional shell entry is something done in the native registry while in monitoring mode, so paths should look "normal".
&nbsp;
But I did take a look this morning at the solutions that I added for this issues in my software.&nbsp; The fixes are based on supporting the ignored registration as shell extensions by manipulating the AppXManifest file.&nbsp; This support was added for MSIX in TMEditX 6.5, and has been coded in an unlreleased version of TMEdit for App-V at this time (it will be in v 3.7 of TMEdit when released).
&nbsp;
FOR MSIX:
For MSIX Packaing, the solution for the problem that I added focuses on supporting the skipped shell extension context menu handler. This, of course, only works on Windows 11.
&nbsp;
Rather than turn the ignored shell extension into a Shell key, I modified the AppXManifest to support the shell extension.&nbsp; The adjusted AppXManifest file is attached in the image.&nbsp; It is the desktop4:Extension element near the bottom.&nbsp; Both desktop4 and desktop5 schemas needed to be added at the top of the file as well.&nbsp; Again, this is a solution for MSIX on Windows 11 as the extensions don't work on Windows 10.

&nbsp;

tompaul678 · Answer

I just came across this problem with appv 5.1. Updated the notepad version and the context menu is gone.

roger_wernli · Answer

TomPaul678&nbsp;Here also context menu issues with App-V 5.1.&nbsp;Notepad++&nbsp;7.8.5 works fine&nbsp;Notepad++ 8.5.8 doesn't work:&nbsp;Does someone know if there is a way to resolve it?

timothy_mangan · Answer

When repackaging for App-V, the only solution right now is as follows:
After installing/configuring the app, use the registry to modify the SHELL file association under "Classes\*" (there might be a ProgID involved, so if so look there -- I am going from memory here!)

Under the shell entry you'll find a value name of "ExplorerCommandHandler". You can remove everything under the "Shell" key, and then under that add a traditional Shell Integration (since the menu provided by the shell extension is the same every time), which is a key "Open" containing a key "Command" with a default value of the path to the Notepad++ exe file with "%1" as an argument.

See https://www.tmurgent.com/TmBlog/?p=3643 for more explanation.

roger_wernli · Answer

TIMOTHY_MANGAN&nbsp;Hi TimThanks and sorry for the late reply.&nbsp;The "old" context menu does work but the icon is missing.On the sequenzer the icon is shown and the parameter has has been added to the registry.&nbsp;On a test client if i look outside of the Notepad++ virtual environment the icon parameter has not been published.If i look inside of the Notepad++ virtual environment the icon parameter is available but the path has not been resolved.&nbsp;I think the path should look like in the command key.&nbsp;Any idea why this is happening?&nbsp;kind regards&nbsp;&nbsp;

Forum Discussion

Notepad++ 8.5.7 and "ExplorerCommandHandler" used to register the Context Menu

Share

Resources