Plan for your deployment
No matter if you are targeting the consumer market or enterprise, the key to successful distribution is knowing the devices your deployment is targeting. Depending on the platform you are targeting, you may have additional dependencies that need to be resolved. Some enterprise companies have a single operating system distributed through out the organization. Others have a mixed collection of hardware and operating systems. In order to be successful in an mixed environment it is important to create a solution that will install easily on all operating systems while limiting the variations in installer technologies.
All developers also need to know the minimum supported operating system they want to target. Targeting the lowest common denominator of the operating system, may get you the best potential reach, but often earlier releases of the operating system may not support certain API calls your application is built using.
MSIX platform support
MSIX was introduced to Windows 10 version 1709 (10.0.16299.0) and greater. This means if you are using the basic MSIX functionality and targeting Windows 10 version 1709 or greater, it will just work. For a complete list of supporting operating systems and supporting features, see Supported Platforms.
Services packaged in MSIX
The ability to package services in MSIX were introduced in Windows 10 Client 2004 (10.0.19041.0) and greater. Therefore if your application is using services packaged in MSIX it is limited to deployment on those operating systems. Admin privileges are required for installation due to the fact that a service may start in the background and make changes to the machine. To learn more about using MSIX Package Services in MSIX, see Convert an installer that includes services.
Server support for MSIX Packages
MSIX is not built into Windows Server. MSIX is however supported on Window 10 Server with Desktop Experience builds 1709 and greater when AppInstaller application is installed. If you are targeting earlier builds of the server, you must also install MSIX Core. For information on MSIX Core, see MSIX Core.
Windows 10 1703 and earlier support for MSIX Packages
If you are targeting earlier versions of Windows, than Windows 10 Client 1709 (10.0.16299.0), you will need to use MSIX Core. By installing MSIX Core on the earlier Windows editions, you will be able to deploy and run MSIX applications.
For a complete list of supporting operating systems and supporting features, see Supported Platforms.
Upgrade, downgrade and architecture considerations
MSIX packages can be upgraded, downgraded, or repaired when the original package is reinstalled. For efficiency, when downgrading, MSIX does a differential update which means that there is no re-download of the old payload.
When updating an existing package, there some are additional factors that you should consider. MSIX bundles and MSIX packages can be architecture specific. While you can upgrade and downgrade apps between architecture, as shown in the table below, you cannot reinstall the same version of different architectures.
| Installed (version) | Upgrade or Reinstall version | Behavior | Result |
|---|---|---|---|
| x86 (1.0) | x86 (1.0) | Reinstall | Supported |
| x86 (1.0) | x86 (3.0) | Upgrade | Supported |
| x86 (1.0) | x64 (1.0) | Reinstall | Not Supported |
| x86 (1.0) | x64 (3.0) | Upgrade | Supported |
| x86 (3.0) | x86 (1.0) | Downgrade | Supported |
| x86 (3.0) | x64 (1.0) | Downgrade | Supported |
Downgrade
When uninstalling or downgrading MSIX, MSIX preserves the user's appdata. Therefore it is important to note that unless that data created by the newer app is backward compatible, accessing the data with the downgraded app could present an issue. If the data is not backwards compatible, you may not wish to allow the user to downgrade.
To learn more about how you can control the update settings for your apps, see Configure update settings in the App Installer file
MSIX bundles
MSIX bundles are packages that are designed to contain multiple architectures. MSIX packages on the other hand only support a single architecture. MSIX bundles can upgrade be used to upgrade or downgrade MSIX packages, but the reverse is not true. You cannot upgrade or downgrade a MSIX bundle with a MSIX package.
To learn more about creating bundles, see Bundle MSIX packages
Transition users to your packaged app
Before you distribute your app, consider adding a few extensions to your package manifest to help users get into the habit of using your packaged app. Here's a few things you can do.
- Point existing Start tiles and taskbar buttons to your packaged app.
- Associate your packaged application with a set of file types.
- Make your packaged application open certain types of files by default.
Also, consider adding code to your packaged application that accomplishes these tasks:
- Migrates user data associated with your desktop application to the appropriate folder locations of your packaged app.
- Gives users the option to uninstall the desktop version of your app.
For more information and examples, see Transition users to your app.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for