Application Details Page

Configure the app delivered by the package.

NoteWhen adding an "UWP AppX Build" from the Builds Page in regular installer projects, Advanced Installer uses your existing installer settings to create an AppX package.

With UWP AppX builds, there's the possibility to add several applications:


Specify general information about the Windows Store application.


The unique identifier of the application or package-relative app identifier (PRAID).

Display name

A friendly name for the app that can be displayed to users. There are two explicitly reserved words that may not be used as names for apps uploaded to the Windows Store: "NoUIEntryPoints" and "NoUIEntryPoints-DesignMode". These identifiers are reserved for use by development tools and test suites.


The description of the app.

Visual Group

This feature allows grouping applications under a folder in the Start menu. You can specify a name of a folder to be created on the All Apps List, in which the tile for the app should be stored.

ImportantThis feature is available Windows 10 build 20257 or newer.

Caution! The Visual Group field doesn't support nested folders. If you include a backslash (\) in the value, an error occurs.

NoteThe VisualGroup field is ignored if there is only only one declared app.

AppList Entry

Provides the app display information such as name, description, and a method to launch the app.

Multiple Instances

Declare the application as a multi-instanced UWP app.

Console Application

Declare the application as a console UWP app.

Set as Default Application

Set the default application. The default application will be launched after the APPX is installed.

Associate COM objects with this application

Can associate multiple applications with the same COM objects.

Start Point

Configure the way your app starts otherwise select None.

Application is compiled


Select the default launch batch file for UWP app or executable file for the Windows Store app using C# or VB and XAML. This file must be present in the package.

Entry Point

Specify the ID of the class that is run when the app is activated. (e.g. "Office.Winword.Class").


Specify the command line parameters (arguments) for the application. This field is of Formatted Type and can be edited with Smart Edit Control. You can include references to files, folders and properties.

Working directory

The working directory of the launch executable file for the app. This field is of Formatted Type and you can include references to folders and properties.

Run mode

Sets the application main-window mode at start.

Caution!"Application Arguments", "Working Directory" and "Run mode" are not compatible with MSIX packages built for Windows versions earlier than Windows 10. For more details see this page

Caution!"Application Arguments", "Working Directory" and "Run mode" are not compatible with MSIX packages built for neutral architecture.

Application is HTML-based

Start Page

The default launch HTML page for the Windows Store app using JavaScript.

Supported Rotations

Select the orientations in which you would prefer the app to be shown for the best user experience. These orientation preference choices apply to both the splash screen and the app UI when a new session is launched for your app.


On a device that can be rotated, such as a tablet, the app will not be redrawn for orientations that are not selected here. For instance, if the app specifies only Landscape and Landscape-flipped orientations, and the device is rotated to a Portrait orientation, the app will not rotate.

On devices that can't be rotated, an app might be shown in that device's default orientation and the app's preferred orientation will be ignored. However, on a device with a rotation lock activated, your app's preferred rotation will still be honored.


Define how the app is viewed on the screen.

Minimum width

The minimum width for the view of the app on the screen. It can have on of the following values:

  • Default
  • 320 pixels
  • 500 pixels

NoteThis section is available only when the schema is set to Windows 8.1 from the Build Page - Windows Store App Project.


Configure lock and splash screen notifications.

Toast capable

This flag indicates that the app is allowed to provide toast notifications.

NoteApps should not make decisions about whether to send toast notifications based on this flag.

Lock screen tiles

The type of tile that can be shown for an app on the lock screen. This can either be simply a badge which displays either a number or a glyph to communicate status, or both a badge and text, which can display detailed status.

Tile Updates

Describes how the app tile receives update notifications.

NoteThis section is available only when the schema is set to Windows 8.1 from the Build Page - Windows Store App Project.


The recurrence interval for tile update notifications. It can be set to one of the following values:

  • Half hour
  • Hour
  • Six hours
  • Twelve hours
  • Daily

URI template

The URI template for tile update notifications, a value URI per RFC 3986. It must be an absolute URI with only schemes of unsecure "http:" sites and secure "https:" sites permitted.