Similar to App-V , Please create MachineScript feature which enables to run scripts with elevated privileges. if already present please guide me  ... View more

Currently there is no convenient way for end end user who has purchased software from an ISV to install a side-loaded MSIX package machine-wide (for all users). Software is often licensed on a per-machine basis and not tied to a specific user. Non-technical users should be able to double-click on an MSIX package and have it installed machine-wide if the vendor has configured it to do so.   Perhaps there are other ways to accomplish this, but here is a suggestion.   Introduce an 'AllUsers' restricted capability to the appxmanifest file that flags the package so that when a user double-clicks the package to install it, it gets provisioned for all users (naturally would require specifying allowElevation in the manifest as well). Similarly, any user who tries to uninstall the package should get prompted for elevated privileges - once elevated, the uninstall should uninstall for all users.   Without this ability, I can't see how MSIX will replace MSI in the long term. ... View more

Hi, As all the other vendors in the Packaging Tool business like Flexera, InstallAware etc. who have the support for creating PSF shims within their tool itself, can MSIX Packaging Tool also have this incorporated within it which will not requiring install other freewares for including supporting for PSF while using the MSIX packaging tool.   BR, DS2803   ... View more

Currently MSIX deployed desktop application (eg. Winforms or WPF) are automatically updated only when app is launched by Start menu item. When user launch app by clicking on app taskbar button or on app desktop shortcut, check for update is not launched. So if new version is available and user runs app always by shortcut or by taskbar button, new version is never detected and thus never installed. This is wrong, because users strongly prefer runs app by desktop shortcut or by taskbar button. Thus I ask to implement checking for update also by clicking on desktop shortcut and on taskbar button. More description you can find on GitHub issue https://github.com/MicrosoftDocs/msix-docs/issues/59 Thanks ... View more

<Separating out Ideas submissions with multiple items>   Being aware of Shortcut management support to be included in upcoming release, will look forward to see the following supported in future releases It will be helpful to address customer requirements in enterprise domain if advance options are provided in the packaging wizard under shortcut section to Pin them to Taskbar OR Start Menu In absence of which administrators will have to deploy a custom script as a different program along with MSIX installation to accomplish the same (Support pin to taskbar or pin to start) ... View more

Per my post here, MSIX packages need to be able to pass command line arguments to executed apps. This is presently not possible.   Without this capability, my ability to package legacy apps with MSIX is severely limited, and has forced me to stay with App-V. ... View more

MSIX AppAttach support so far has only made its way to Azure Virtual Desktop.   There would be benefit for organisations using MECM and on premise VDI solutions if MECM had support for MSIX AppAttach.   This would improve the delivery time in MSIX applications to users of those non persistent VDI's as MECM would not need to download the software first and reduce storage requirements as apps can be hosted on and stream from a DP rather than consume storage on a VDI's differencing disk. ... View more

See original post: Backward Compatibility and the AppXManifest Schema Sets - Microsoft Tech Community ... View more

There are times when integration is required and the container gets in the way.  The upcoming Shared Package Containers will help when both parts are MSIX packages, but not so much when the secondary is not containerized.   In App-V this was solved by RunVirtual, a way to designate that a given process name should run inside a particular virtual environment.  This would also work for MSIX, but I'd like to propose a different idea that likely would offer solutions to more kinds of problems with containerization and multiple applications.   What I would like is a new addition to the AppXManifest whereby I can list some named processes to be controlled.  If a process is named, it would have one of two settings, marking the process to explicitly run inside or outside of the container.  This list would only apply to new processes being started as a child process of a process already in the container.   The flexibility of this would be quite helpful as more apps move into the container. ... View more

We can put arguments into the config.json file inside the MSIX package to have the Launcher64.exe pass those arguments to the installed application when it is launched. What I need to do is pass a query string to the MSIX package from a link on a web page using the appinstaller and have that query string passed as an argument to the installed application.   We are currently using clickonce but that is not supported well in Chrome so we want to move to MSIX. Chrome requires another click on a downloaded .application file.   Brett Burgeson ... View more

We have many 3rd party apps that creates addin to excel , office , powerpoint, word. So far we have been using script to instantiate object and add addin once the user logs off/login .  We also tried with run virtual key in appv 5.1 but it will always launch excel in its isolated environment which again is not helpful.   Are we planning to handle this behaviour too with MSIX ? ... View more

Our application relies on an optional windows feature, in our case Projected File System (Client-ProjFS). It would be great if we could specify those as dependencies in the installer and have the installer enable them. Working around that is very cumbersome at the moment. We couldn't get custom install actions to work as those only seem to be supported for games. ... View more

Provide a solution which will enable multiple MSIX packages to engage with other MSIX Packages (Similar to App-V Connection Groups).    Consider the following requirements:   - Allow Modification Packages to create entries in the Start Menu.   - Allow Modification Packages to be linked to multiple MSIX applications. ... View more

For example, with Notepad++ you can right click a file and you see an "Edit with Notepad++" item.  Because these context menus items are added via registry (and the MSIX container-izes it), the OS is unaware of the new context menu item. ... View more

Bumping this thread to ideas section for @John Vintzel    https://techcommunity.microsoft.com/t5/msix-packaging-and-tools/msix-packaging-tool-missing-file-type-associations/m-p/1834735#M936 ... View more

The OS will support services with MSIX for enterprise customers starting with the 20H1 insider flights.     Adding this as a item specific for the tooling.  ... View more

It would be great if I could export or open a file out of the MSIX Packaging Tool when using the editor. That way I could look at its content or the file version Information. In case its is a config file I could then change something and add it again. ... View more

Option similar to RunVirtual key in App-V is helpful in launching applications like Office add-ins. ... View more

Enterprises have legacy apps they would like to convert to MSIX.  Allow apps with services to be packaged and deployed as MSIX ... View more