Pro edition. An MSIX package contains the installed application files (not an installer), together with a manifest that describes the app to Windows.
If you only have an installer (setup.exe or .msi), create a PSADT package with it and convert it to MSIX. The Conversion Assistant can repackage the installer for you.
Step 1: Source Files #
Upload the application files, for example the folder with the application’s EXE and DLL files.
Step 2: Package Identity #
| Field | Description |
|---|---|
| Display name (required) | The app name users see |
| Publisher (identity) (required) | The technical publisher, for example CN=Contoso. It must match the signing certificate. The wizard sets it to match automatically when it builds. |
| Publisher display name | The vendor name shown in the Start menu, for example Contoso Inc. |
| Version (required) | A four-part numeric version, for example 1.0.0.0 |
| Architecture | x64, x86 or arm64 |
| Logo (PNG) | A PNG image from your uploaded files. Choose — none — to use a placeholder. |
The step also shows the resulting Package Family Name.
Step 3: Dependencies (Dependencies & Capabilities) #
- Capabilities. Pick from the standard values or type your own.
runFullTrustis required for classic Win32 applications. - Framework dependencies. For example the Visual C++ runtime (VCLibs), WinUI or the Windows App Runtime. Pick a preset or enter
NameorName|MinVersion.
Step 4: Applications #
Choose the Primary executable from your uploaded .exe files. This is the program that the Start menu entry launches.
Step 5: Signing #
Windows only installs signed MSIX packages.
| Field | Description |
|---|---|
| Signing certificate | Choose a certificate or keep use the active certificate. You can also Generate test certificate or Upload certificate… here. |
| Timestamp server | Default http://timestamp.digicert.com. A timestamp keeps the signature valid after the certificate expires. If the server cannot be reached, the package is signed without a timestamp and you get a warning. |
If no certificate exists, a long-lived self-signed certificate is created automatically on the first build. Its public certificate (.cer) is saved next to the package so you can trust it on target machines.
Step 6: Preview & Build #
- Shows the validation results and the generated AppxManifest.
- When the status reads All checks passed — ready to build, click Finish to build, sign and save the
.msix.
Result: {name}.msix and {name}.cer.