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

Roger_Wernli 

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

But I did take a look this morning at the solutions that I added for this issues in my software.  The fixes are based on supporting the ignored registration as shell extensions by manipulating the AppXManifest file.  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).

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.

Rather than turn the ignored shell extension into a Shell key, I modified the AppXManifest to support the shell extension.  The adjusted AppXManifest file is attached in the image.  It is the desktop4:Extension element near the bottom.  Both desktop4 and desktop5 schemas needed to be added at the top of the file as well.  Again, this is a solution for MSIX on Windows 11 as the extensions don't work on Windows 10.