Shared package container

Shared package containers allows IT Pros to create a shared runtime container for packaged application – sharing a merged view of the virtual file system and virtual registry - enabling access to one another’s package root files and state. Beginning on Windows 10 Insider Preview Build 21354, IT Pros will be able to manage what apps can be in what container is important to the conversion of MSIX from legacy installers. The concept of a shared container is used primarily for customization, sharing pre-requisite software, and supporting addons for converted apps. Please note that this is an enterprise only feature and will require administrative privileges to use.

Shared package container operations are independent of app deployment operations. What this means is that apps do not have to be installed prior to share package container definition being deployed to a device. It also means that not all apps that are defined inside the shared package container need to be installed for the shared package container to run. The apps inside the shared package container will be able to independently update without having to modify the shared package container definition.

Note that an app will only be allowed to be inside one container. Deploying a shared package container that contains an app that is already part of a shared package container will result in an error.


To use the feature, enterprises will require an administrator on the device. Additionally, the packages will all need to be .msix packages. To package your installers as MSIX package, visit our create package from existing installer documentation.

Shared package container definition

Shared package contianer is defined by a .xml file. The container definition requires a unique name and a list of packages that belong to that container. Only main packages need to be included in the .xml. Optional packages and modification packages will automatically be included in the shared package container as they already share the same container as their main package. Note that the priority of the packages is established from top to bottom of the list. Meaning that the top package will have the highest priority. Priority of the package is used for conflict resolutions among packages that may have the same files. Below is a sample of one.

<?xml version="1.0" encoding="utf-8"?> 
<AppSharedPackageContainer Name="ContosoContainer"> 
  <PackageFamily Name="Fabrikam.MainApp_8wekyb3d8bbwe"/> 
  <PackageFamily Name="Contoso.MainApp_8wekyb3d8bbwe"/> 
  <PackageFamily Name="ContosoCustomize_7xekyb3d8ccde"/> 

When you have the container definition .xml, you can use the following PowerShell commands to deploy, reset, update, and remove a Shared Package Container from the device. Note that all other app deployment commands remain the same (i.e installing packages)

PowerShell commands

Deploy a shared Package container definition

Add-AppSharedPackageContainer <path> 

This command deploys the shared package container definiton for the particular user. Optional parameters include the following:

Parameter Description
ForceApplicationShutdown Closes all packages currently running in the Shared Package Container.

Remove a shared package container

Remove-AppSharedPackageContainer -Name <name>  

This command removes the shared package container definiton for the particular user. Optional parameters include the following:

Parameter Description
ForceApplicationShutdown Closes all packages in the Shared Package Container.

Get information on a shared package container

Get-AppSharedPackageContainer -Name <name> 

This command gets information about the shared package container. In particular, it will show what packages are inside the shared package container.

Reset shared package container

Reset-AppSharedPackageContainer -Name <name>  

This command destroys all the application data of the container, including the virtual files and registry keys.