Both desktop4 and desktop5 schemas needed to be added at the top of the file as well. It is the desktop4:Extension element near the bottom. The adjusted AppXManifest file is attached in the image.

Rather than turn the ignored shell extension into a Shell key, I modified the AppXManifest to support the shell extension. This, of course, only works on Windows 11. 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).įor MSIX Packaing, the solution for the problem that I added focuses on supporting the skipped shell extension context menu handler.

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

I have quoted your problem there, and then replied with my debugging suggestions. Thus, to give it the attention it deserves, I am putting more detailed replies to a new topic in the “Help Wanted” section: please follow the discussion in this new topic = I (and plenty of other regulars here) have not noticed any difficulty installing plugins with v7.8.6.

This does not sound like a problem specific to v7.8.6 – or at least, if it is specific to the version, it’s specific to the version plus whatever is unique about your system. But I always seem to have the problem of the plugins// I downloaded them but they don’t seem to be installed at all I always check to basically know if there was any problems and that it was none of plugins would comeup and they don’t seem to be installed I don’t think that this can’t be a hard issue to fix right I’m counting on you to fix it

Notepad++ 8.5.7 instal the new for mac