If you are an OEM or an ISV working with an OEM to provide your app to be included in a PC image, you will need to provide the OEM with a 'preinstall package'. This post will review what a preinstall package is and how to generate them. Note that preinstall packages can only be created by Microsoft. Preinstalled apps also must be free and can't be changed to paid.
Preinstall apps are Microsoft Store apps that are integrated by OEMs into their OS images, the are the default apps available to user when they setup their PC for the first time. If an app is to be available in the Microsoft Store and an OEM device, the device OEM image must integrate a preinstall app package. This is to ensure version and binary continuity of the app and that the app is automatically updated from the Store. Enterprises can include line of business (LOB) apps into OS images via sideloading. See the documentation here for more on the Enterprise scenario. This post reviews the ISV / OEM scenario.
OEMs and ISVs working with OEMs can request to have their Windows Developer Partner Center account provisioned with 'preinstall' permissions. Do this by emailing
Your email should include:
Once your account has been enabled with preinstall permissions, the Partner Center Windows app Manage packages page will be extended with the 'preinstallation' UI shown below:
A preinstall package is a zip file that contains:
You can validate the app can be installed in the currently running OS with the files provided in the preinstall zip, with the following steps:
Add-AppxProvisionedPackage -Online -PackagePath .\myPackage.msix -LicensePath .\myLicense.xml
Additional parameters for Add-AppProvisionedPackage here.
After successfully running this command, run the app from the app list to verify the app starts as expected.
Additional documentation: Generate preinstall packages for OEMs - Windows UWP applications | Microsoft Docs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.