How to get started today


Some folks have asked me if there is anything we can do to start the move to MSIX today?


The tooling is expected to be in a Windows Insider preview in the June timeframe.  Meanwhile folks can start by using the Desktop bridge.  100% of apps that convert to the desktop bridge will update to MSIX.


Check out for more information.


If your app does not easily convert via the desktop bridge, don't worry.  We will have more support coming for MSIX to make the transition easy!


John Vintzel | @jvintzel

Principal Program Manager Lead, MSIX 

28 Replies

Hi John,


I work in the space of appv and msi technology and I am excite to know more about MSIX.

given we are migrating apps on win 10 I would like to know which is the best tool to convert our existing desktop apps into appx. I would also like to know if we can use sccm to distribute this appx package and whether it needs to installed into private store for business.

What if we have a mixture of Win7 & Win10 computers and WinForms & WPF apps.  Can MSIX be used to replace ClickOnce and provide the deployment & auto-update for these scenarios?  If so, how do we get started reviewing/testing to possibly convert?  Thx

best response confirmed by John Vintzel (Microsoft)



When looking to move your existing apps forward to MSIX, I'd recommend starting with the tooling vendor creating your packages today (if you have one). For example, if you're using the WiX Toolset to create your installation packages, we at FireGiant have created an extension to create .appx packages (and soon MSIX packages when Windows provides full support for MSIX) along with your .msi packages. I expect all the other major packaging vendors will support MSIX as well. If you don't have a vendor already, there are several to choose from (I think this presentation showed them:


As to your second question, MSIX will allow you deploy directly via SCCM. You can use the Windows Store for Business but it is not a requirement. MSIX deployment is much more like MSI in that way.


Hope that helps.

We do offer an auto-updating solution on Windows 10 to replace ClickOnce with MSIX. As for Windows 7, to use MSIX you need to wrap the MSIX file with the MSIX SDK on GitHub.  That will allow you to read, extract, verify the package and deploy it the devices.  There is no native auto-updating with MSIX on Windows 7, again that would need to leverage the SDK.


For Windows 10, this session covers the update behaviors and more.

You can start by converting your existing app to .appx with the Desktop App Converter (you can find it in the Microsoft Store)

You can use MDMs to distribute.

Yes, you can distribute your app by putting them on Microsoft Store or Store for Business

You can use the auto updates through App Installer. For more details checkout


1) The build talk MSIX Inside and Out

2) this blog

3) The documentation for App Installer:

There are support from these vendors.
Advanced Installer, flexera, cloudhouse etc..
For win 7, as per my knowledge you have to wrap the msix inside a msi and can deploy it. This again is not a good move going back to msi..

The following have announced upcoming support for MSIX:

Advanced Installer








Great feedback.  We offer the SDK for folks that might want to minimize the packages they create.  For Windows 7 it is essentially treating the MSIX file as a .cab file, minimizing the repackaging across multiple operating systems.


John Vintzel

Principal Program Manager Lead, MSIX


Eagerly waiting for the tool to be released from MS.

Stay tuned.. We will post some updates as more becomes available.  Most likely sometime this summer.



We’re an application packaging specialist with many do we get added to this list?



Hi John ,


As you stated MS is working on tool to convert pre-existing packages into msix. Is there an update on it ?

A Preview of the MSIX Packaging Tool will be coming shortly. We will post an announcement here when it is available.

I wrote a blog article with a step by step tutorial on how you could convert a setup to an msix and test it today with the tools provided by Microsoft right now:

Great tutorial! Thank you for putting it together.

Will MSIX be able to create an Custom Actions as it is possible with MSI right now? Working closely with a lot of enterprise customers I see this is very common requirement in MSI packages.
Example for CA in MSI: If target machine's Computer Name contains text "ABC" then run specific command line.
Will something similar be possible with MSIX? 

The MSIX team has been pretty clear that they see Custom Actions as a problem and thus there are no mechanisms to execute any custom commands during installation. At this time, there isn't any option to get input from the customer during installation either. Custom code will have to be executed by your application.


PS: This is the core reasons I expect the Windows Installer (MSI) will remain the "Anything Installer" (see: for quite a while. As MSIX covers more functionality of Windows, it will start to replace more and more MSIs. But Windows provides a wide surface area so I expect it to take a while to support the full breadth of applications.