Guidance for app package management

Learn how your app's packages are made available to your customers, and how to manage specific package scenarios.

OS versions and package distribution

Different operating systems can run different types of packages. If more than one of your packages can run on a customer's device, the Microsoft Store will provide the best available match.

Generally speaking, later OS versions can run packages that target previous OS versions for the same device family. Windows 10 devices can run all previous supported OS versions (per device family). Windows 10 desktop devices can run apps that were built for Windows 8.1 or Windows 8; Windows 10 mobile devices can run apps that were built for Windows Phone 8.1, Windows Phone 8, and even Windows Phone 7.x. However, customers on Windows 10 or Windows 11 will only get those packages if the app doesn't include UWP packages targeting the applicable device family.


You can no longer upload new XAP packages built using the Windows Phone 8.x SDK(s). Apps that are already in Store with XAP packages will continue to work on Windows 10 Mobile devices. For more info, see this blog post.

Removing an app from the Store

At times, you may want to stop offering an app to customers, effectively "unpublishing" it. To do so, click Make app unavailable from the App overview page. After you confirm that you want to make the app unavailable, within a few hours it will no longer be visible in the Store, and no new customers will be able to get it (unless they have a promotional code and are using a Windows 10 or Windows 11 device).


This option will override any visibility settings that you have selected in your submissions.

This option has the same effect as if you created a submission and chose Make this product available but not discoverable in the Store with the Stop acquisition option. However, it does not require you to create a new submission.

Note that any customers who already have the app will still be able to use it and can download it again (and could even get updates if you submit new packages later).

After making the app unavailable, you'll still see it in Partner Center. If you decide to offer the app to customers again, you can click Make app available from the App overview page. After you confirm, the app will be available to new customers (unless restricted by the settings in your last submission) within a few hours.


If you want to keep your app available, but don't want to continuing offering it to new customers on a particular OS version, you can create a new submission and remove all packages for the OS version on which you want to prevent new acquisitions. For example, if you previously had packages for Windows Phone 8.1 and Windows 10, and you don't want to keep offering the app to new customers on Windows Phone 8.1, remove all of your Windows Phone 8.1 packages from the submission. After the update is published, no new customers on Windows Phone 8.1 will be able to acquire the app though customers who already have it can continue to use it). However, the app will still be available for new customers on Windows 10.

Removing packages for a previously-supported device family

If you remove all packages for a certain device family (see Programming with extension SDKs) that your app previously supported, you'll be prompted to confirm that this is your intention before you can save your changes on the Packages page.

When you publish a submission that removes all of the packages that could run on a device family that your app previously supported, new customers will not be able to acquire the app on that device family. You can always publish another update later to provide packages for that device family again.

Be aware that even if you remove all of the packages that support a certain device family, any existing customers who have already installed the app on that type of device can still use it, and they will get any updates you provide later.

Adding packages for Windows 10 to an existing app

If you have an app in the Store that only included packages for Windows 8.x and/or Windows Phone 8.x, and you want to update your app for Windows 10, create a new submission and add your UWP .msixupload or .appxupload package(s) during the Packages step. After your app goes through the certification process, the UWP package will also be available for new acquisitions by customers on Windows 10.


Once a customer on Windows 10 gets your UWP package, you can't roll that customer back to using a package for any previous OS version.

Note that the version number of your Windows 10 packages must be higher than those for any Windows 8, Windows 8.1, and/or Windows Phone 8.1 packages you have used. For more info, see Package version numbering.

For more info about packaging UWP apps for the Store, see Packaging apps.


App package management is not supported for MSI and EXE apps.


Package version numbering is not supported for app add-ons.