How do I migrate/upgrade my users from an .msi to an .msix based setup?

%3CLINGO-SUB%20id%3D%22lingo-sub-2595809%22%20slang%3D%22en-US%22%3EHow%20do%20I%20migrate%2Fupgrade%20my%20users%20from%20an%20.msi%20to%20an%20.msix%20based%20setup%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2595809%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20created%20a%20.msix%20version%20of%20my%20installer%20(using%20MakeAppx%20and%20a%20manual%20PackageLayout).%20It%20works%20fine%20by%20itself%20and%20installs%20%26amp%3B%20runs%20my%20app%20without%20issue%20(a%20C%2B%2B%20FullTrust%20UWPDesktop%20app).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20my%20app%20previously%20was%20just%20a%20simple%20Windows%20C%2B%2B%20application%20and%20shipped%20using%20an%20.msi-based%20installer.%20The%20same%20installer%20was%20used%20for%20both%20first%20install%20%26amp%3B%20build-over-build%20upgrade.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20the%20next%20release%20of%20my%20app%20to%20go%20out%20with%20the%20.msix%20instead.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20fine%20for%20all%20new%20users%20but%26nbsp%3Bhow%20do%20I%20upgrade%20my%20existing%20users%20from%20the%20.msi%20to%20the%20.msix%20based%20installer%3F%20Currently%20if%20I%20try%20to%20%22upgrade%22%20from%20.msi%20to%20.msix%20it%20causes%20two%20versions%20of%20the%20app%20-%20the%20old%20.msi%20version%20and%20the%20new%20.msix.%20I%20suppose%20I%20need%20to%20get%20the%20.msix%20install%20to%20remove%20the%20old%20.msi%20version%20of%20the%20app%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2676995%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20migrate%2Fupgrade%20my%20users%20from%20an%20.msi%20to%20an%20.msix%20based%20setup%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2676995%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1116054%22%20target%3D%22_blank%22%3E%40deonb11155%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGreat%20question%2C%20thanks%20for%20reaching%20out!%20This%20is%20because%20we%20don't%20associate%20the%20two%20apps%20types.%20How%20you%20can%20do%20this%20'upgrade'%20depends%20on%20how%20you%20are%20deploying%20your%20app.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20using%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fdesktop%2Fmanaging-your-msix-deployment-enterprise%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Emanagement%20tool%3C%2FA%3E%2C%20you%20can%20manage%20the%20deployment%20and%20uninstallation%20from%20there.%3C%2FP%3E%0A%3CP%3EOr%2C%3C%2FP%3E%0A%3CP%3EYou%20can%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpsf%2Frun-scripts-with-package-support-framework%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Euse%20a%20script%3C%2FA%3E%20to%20perform%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fadministration%2Fwindows-commands%2Fmsiexec%23%3A~%3Atext%3Dthe%2520advertised%2520package.-%2C%2Fx%2CUninstalls%2520the%2520package.%2C-%253Cpath_to_package%253E%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Euninstall%3C%2FA%3E%20when%20you%20install%20the%20msix.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3ESharla%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

I have created a .msix version of my installer (using MakeAppx and a manual PackageLayout). It works fine by itself and installs & runs my app without issue (a C++ FullTrust UWPDesktop app).

 

However my app previously was just a simple Windows C++ application and shipped using an .msi-based installer. The same installer was used for both first install & build-over-build upgrade.

 

I want the next release of my app to go out with the .msix instead.

 

This is fine for all new users but how do I upgrade my existing users from the .msi to the .msix based installer? Currently if I try to "upgrade" from .msi to .msix it causes two versions of the app - the old .msi version and the new .msix. I suppose I need to get the .msix install to remove the old .msi version of the app?

 

1 Reply

Hi @deonb11155,

 

Great question, thanks for reaching out! This is because we don't associate the two apps types. How you can do this 'upgrade' depends on how you are deploying your app.

 

If you are using a management tool, you can manage the deployment and uninstallation from there.

Or,

You can use a script to perform the uninstall when you install the msix.

 

Best,

Sharla