WPNinjas HeaderWPNinjas Header

MSIX Commander released

For a long time, I had some issues with my tool MSIX Commander, regarding running it out of an MSIX container. Now I finally managed to get the new Version working as an MSIX.

After spending numerous hours in the evening, I finally had one quiet morning alone on the breakfast table and had time to think in different way about my problem. Then I came up with an idea for a workaround and that idea really worked.

Once that nagging issue was finally resolved I had also some time for other point from my feature list. So, I’m very proud to announce, that the Version is now released and has the following new and in my opinion cool features.

New Features:

– Now also available as an MSIX

– Let’s you not only enable sideloading but also Developer Mode

– You can now open a CMD, Regedit or Notepad inside your MSIX Container for troubleshooting. Almost like the /appvve: parameter for App-V


– Error on startup when sideloading has never been activated

– Fixed some writing errors

If you’re curious about how I open other Tools inside the MSIX Package container, watch out for my next blog where I will explain how that works and how it can be done with some simple PowerShell code.

Do you ask yourself why I let you open Notepad inside an MSIX Container and why not start Explorer? For now, there is a problem that explorer.exe cannot be started inside an MSIX Container.

Therefor I let you open the editor as a workaround. First you select “File” and then “Open” in the Editor. Then you can change the filter to “All Files” and there you go you have a nice explorer replacement.

You can now browse your file System and look inside your MSIX Package Filesystem. In this example an MSIX package of the Edge Chromium Edition.

Like always you can get the latest version here: https://github.com/bergerpascal/MSIX_Commander/releases

I hope you enjoy the new features.

If you have any questions, features request, bugs or any other type of feedback pleas let me know.


Hans Straat · June 27, 2019 at 14:33

tried to run the executable but got a nice notifiction from Symantec

Scan type: Auto-Protect Scan

Event: Security Risk Found!

Security risk detected: WS.Reputation.1

    Pascal Berger · June 27, 2019 at 15:56

    Hi Hans, regarding to the following article the WS.Reputation.1 message you mention, is related to an EXE that Symantec thinks is not used enough:

    This can also happen with Smartscreen from Microsoft.
    Unfortunately, that is something I cannot do anything about. There need to be more users who use Symantec and who use my tool 🙂 I know in terms of Smartscreen it would help to singe the tool with an “EV Code Signing Certificate”. I already sing my tool with a trusted Code Signing Certificate. But I don’t have access to an EV Code Signing Certificate. Since they are very very expensive.

    Symantec has a Website where you as a Symantec Customer can report a false positive:
    It would be very nice if you could take same time to fill out the questions of Symantec. Unfortunately, I don’t have enough information about your infrastructure to fill out the questions.
    Kind regards

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.