# How to create MSIX packages from an .exe or .msi app?

Last updated: July 24, 2026

This guide explains how to use the MSIX Packaging Tool on Windows 10 (version 1809 or later) to convert an .exe or .msi installer into an MSIX package for silent distribution to Windows 10 devices (1803 or later) via Mobile Device Manager Plus. Administrators select the installer, sign it with a .pfx certificate, provide package details like name, publisher, and version, then let the tool monitor installation and capture post-install tasks such as shortcuts. The finished package is saved and uploaded to the MDM console for distribution.

## Description

MSIX is a Windows app package that provides modern packaging experience to all Windows apps. With the MSIX packaging tool, admins can create an MSIX package from an EXE. With MDM, admins can silently install MSIX apps on devices running **Windows 10, version 1803 or above**.

Follow the steps given below to create MSIX packages.

## Steps

1. Download the [MSIX packaging tool](https://www.microsoft.com/en-in/p/msix-packaging-tool/9n5lw3jbcxkf) from the Windows Store on a device running **Windows 10, version 1809 or above**.
2. Launch the tool and select **Application Package** to create the MSIX app package.
3. Browse and select the installer to be packaged. Under **Additional Options**, check the **Sign Package** box and select a .pfx certificate file to sign the package. If your certificate file is password protected, provide the password. Click on **Next**.
4. Select **Create Package** on this computer if you wish to save the package on the same computer upon creation. Click on **Next**.
5. Provide the required package details:
   - **Package name:** Package name to identify the package. Package name is case sensitive and cannot contain spaces.
   - **Package display name:** Name of the package to be displayed to the user.
   - **Publisher name:** Name of the app publisher.
   - **Publisher display name:** Publisher name to be displayed to the user.
   - **Version:** The app version.

   The above mentioned details are mandatory to create the package. The publisher name and publisher display name are prefetched from the uploaded certificate. You can optionally enter the **Installation Path** if you wish to save the app in a location other than Program files.
6. On the **Prepare the computer** screen, availability of the MSIX Packaging Tool Driver is checked. This driver is required to monitor and capture all the changes made by the installer on the machine. The package is created based on the changes made. To ensure no other processes are captured, it's recommended to use a clean machine to create the MSIX packages. Ensure **Windows Search** is **Disabled**. Click on **Next**.
7. On the next step, the tool monitors the installation of the application. Click on **Next** once the installation is complete.
8. On the next step, any post installation tasks can be captured. Here you can also create the desktop shortcut and Start Menu shortcut. This will ensure that these shortcuts are created when the app is installed on the target machine. You can also install any pre-reqs required by the app in this step. Click on **Next** after successfully running the application.
9. Provide the location to save the created MSIX package and click on **Create** to create the package.
10. Upload the MSIX package on the MDM server by following the steps given [here](https://www.manageengine.com/mobile-device-management/help/app_management/windows_app_management.html?create_msix#Silent_installation).

## Frequently asked questions

### What Windows version do I need to silently install MSIX apps through MDM?

Devices must be running Windows 10, version 1803 or above, for MDM to silently install MSIX apps.

### Why should I use a clean machine when creating an MSIX package?

The MSIX Packaging Tool Driver monitors and captures every change the installer makes so the package can be built from those changes. Using a clean machine with Windows Search disabled ensures no unrelated processes get captured in the package.

### Which package details are filled in automatically when I create an MSIX package?

The publisher name and publisher display name are prefetched automatically from the uploaded certificate; the package name, package display name, and version still need to be entered manually.