Package Information Page

Define general information about the package including attributes that describe how the package appears to users and prerequisites.

Package

Define general information about the package.

ID

The globally unique identifier name for the package.

Display Name

A friendly name for the package that can be displayed to users.

Description

A friendly description that can be displayed to users.

Version

The version number of the package. The format is a version string in quad notation, e.g. "Major.Minor.Build.Revision".

Package Integrity

Select the level of run time package integrity checks and remediation for the package:

On
Off
Default

Supported Users

Specify if the package is multi-user compatible. This setting will be evaluated at install time to verify if the package can be installed on the system.

Single
Multiple

Allow Execution

Specify if the executable contained by the package is allowed to execute.

Logo

A path to a file that contains an image. Depending on the scale, the image size can vary.

*Scale*	400	200	150	125	100
*Size*	200 x 200 px	100 x 100 px	75 x 75 px	63 x 63 px	50 x 50 px

Asset Generator

Generate the Logo assets.

Source

The source image used to create the assets.

Destination

The path on disk where the assets are created.

Scales

Press the [ ... ] to select what are the scales of the generated assets.

Scaling Mode

The scaling used when creating the generated visual assets.

Bicubic (Sharper Edges, Highest Quality)
Bilinear (Sharper Edges)
Nearest Neighbor (Smoother Edges)

Generate

Press the [ Generate ] button to create the assets.

Publisher

Define the publisher information.

Display Name

A friendly name for the publisher that can be displayed to users.

ID

This field must match the publisher subject information of the certificate used to sign a package.

To learn more about the Publisher ID, check out the How to correctly set the Publisher ID for a UWP AppX article.

Migration

Migration is not compatible with MSIX packages built for Windows versions earlier than Windows 10. For more details see this page.

Migration is not compatible with MSIX packages build for neutral architecture.

Automatically migrate previous user data from the desktop app upon first launch of this store version. This is Microsoft's recommendation so users can seamlessly have everything in place.

Uninstall code

This is the actual Upgrade Code of your app.

User data folder

The subfolder containing your app's user data. Based on the following examples, choose one of the default Local or LocalLow folders:

%USERPROFILE%\AppData\Local\YourApp

%USERPROFILE%\AppData\LocalLow\YourApp

UI level

Set the UI level to determine the migration user experience.

Ask user about data migration - moves the user data and uninstalls any previous versions by prompting every time.
Automatically migrate user data - the same as above without any prompts.

Use the Show notification option to notify the user when the migration has completed. The notification will be shown regardless of the UI level.

Virtualization

Virtualization settings for the MSIX package.

File System

Enables virtualization for the file system entries of your application.

If file system virtualization is disabled, the file system entries of your application can be accessed by other apps (read and write).

Registry

Enables virtualization for the registry entries of your application

If registry virtualization is disabled, registry entries of your application can be accessed by other apps (read and write).