Microsoft Store & MSIX

Desktopr can generate a Windows desktop build that includes both the traditional Windows installer and an optional MSIX package for Microsoft Store submission.

MSIX is Microsoft’s modern packaging format for Windows applications. Instead of distributing only a traditional .exe or .msi installer, MSIX packages your app into a .msix structured Windows package with a package identity, visual assets, metadata, and Store-compatible configuration.

This is useful if you want to distribute your Desktopr-built app through the Microsoft Store, reduce installation friction for users, and avoid managing a separate Windows code signing certificate for Store distribution.

WARNING

Desktopr only generates the MSIX package when the Microsoft Store identity fields are provided in your app settings. If these fields are empty, Desktopr skips MSIX generation and continues with the normal Windows build.

Why Use MSIX?

Using MSIX gives your Windows app a package identity. This identity is required for Microsoft Store distribution and is used by Windows to recognize the packaged app.

For Desktopr users, the main advantages are:

1. You can submit the generated MSIX package to Microsoft Partner Center.
2. The app can be distributed through the Microsoft Store.
3. Microsoft re-signs Store-submitted MSIX packages after certification.
4. Users installing from the Microsoft Store avoid the usual SmartScreen friction associated with unknown downloaded installers.

Microsoft recommends MSIX for Store submission and documents the Store publishing flow for packaged Windows apps here:

• Publish your app in the Microsoft Store
• Publish your app in the Microsoft Store
• MSIX documentation

Traditional Windows Installer vs MSIX

Desktopr can include different Windows outputs in the build bundle.

Output	Purpose
.exe	Traditional Windows installer, useful for direct downloads outside the Microsoft Store.
.msix	Store-oriented package, useful for Microsoft Store submission.

The .exe installer is still useful if you want to distribute your app directly from your website. The .msix package is useful if you want to publish the app through the Microsoft Store.

WARNING

The MSIX file generated by Desktopr is intended for Store submission only when the Store identity values match the app identity assigned in Microsoft Partner Center.

How MSIX Works in Desktopr

When the Microsoft Store fields are provided, Desktopr adds an extra MSIX packaging step during the Windows build.

The final Windows build bundle may contain a structure similar to this:

nsis/
  Your App_1.0.0_x64-setup.exe
  Your App_1.0.0_x64-setup.exe.sig

msix/
  your_app_id_1.0.0_x64.msix
  msix-build.log

bundle.map.json

The .msix file is placed inside the msix/ folder and included in the Windows build bundle.

The MSIX package is also included in bundle.map.json as a non-signable file. Desktopr does not treat it as part of the normal updater distribution flow.

When MSIX Generation Is Skipped

Desktopr skips MSIX generation when the Store identity fields are not provided.

This means you can build a normal Windows app without configuring Microsoft Store distribution.

MSIX generation is optional and only runs when the required Store identity fields are present.

TIP

If you do not plan to publish your app to the Microsoft Store, you can leave the MSIX fields empty.

Microsoft Store Identity

A Microsoft Store-ready MSIX package must use identity values assigned by Microsoft Partner Center.

These values should not be guessed or manually invented. The user must create or reserve the app in Microsoft Partner Center and copy the identity values from the product identity page.

Microsoft documents product identity details here:

• View app identity details

A typical Partner Center path is:

Product management → Product identity

From that page, copy the required identity values into Desktopr.

Store Identity Fields

store_identity_name

This is the MSIX package identity name.

It maps to the manifest field:

<Identity Name="..." />

Use the exact Package/Identity/Name value from Microsoft Partner Center.

Official Microsoft reference:

• View app identity details

store_identity_publisher

This is the MSIX package publisher identity.

It maps to the manifest field:

<Identity Publisher="..." />

Use the exact Package/Identity/Publisher value from Microsoft Partner Center.

Official Microsoft reference:

• View app identity details

store_publisher_display_name

This is the human-readable publisher name.

It maps to the manifest field:

<PublisherDisplayName>...</PublisherDisplayName>

Use the exact Package/Properties/PublisherDisplayName value from Microsoft Partner Center.

Official Microsoft reference:

• View app identity details

store_package_display_name

This is the display name of the app inside the MSIX package.

It maps to the manifest field:

<DisplayName>...</DisplayName>

Usually, this should match the app name reserved in Partner Center and shown to users in the Microsoft Store.

Official Microsoft reference:

• Package manifest schema

store_logo_background_color

This is the background color used by Windows visual elements in the MSIX package.

It maps to the manifest field:

<uap:VisualElements BackgroundColor="#ffffff" />

Use a valid color value such as:

#ffffff

Official Microsoft reference:

• VisualElements schema

store_short_name

This is an optional short name used in Windows tile-style UI.

It can map to the manifest field:

<uap:DefaultTile ShortName="..." />

This field is optional and is not one of the core Partner Center identity values.

Official Microsoft reference:

• DefaultTile schema

Recommended Workflow

Follow this process if you want to publish a Desktopr Windows app through the Microsoft Store.

1. Create or access your Microsoft Partner Center account.
2. Create or reserve your app product in Partner Center.
3. Open the product identity page.
4. Copy the Store identity values into Desktopr.
5. Run a Windows build with the MSIX fields filled in.
6. Download the Windows build bundle.
7. Extract the generated .msix file from the msix/ folder.
8. Upload the MSIX package to Microsoft Partner Center as part of your Store submission.

WARNING

The identity values are case-sensitive and must match the values assigned by Microsoft Partner Center. If they do not match, the package may fail Store submission.

Signing Notes

For normal direct distribution outside the Store, Windows apps usually need a trusted code signing certificate to improve trust and reduce warnings.

For Microsoft Store MSIX distribution, Microsoft signs the package as part of the Store certification and publishing process. This is one of the main reasons to use the Microsoft Store flow.

Official Microsoft reference:

• Code signing options
• Desktopr signing

Troubleshooting

If MSIX generation fails, common causes include:

1. Missing Store identity fields.
2. Incorrect Store identity values.
3. Invalid app version format.
4. Missing Windows SDK packaging tools in the build environment.
5. Invalid visual asset or manifest configuration.

TIP

If the traditional Windows installer was generated successfully but the MSIX package is missing, the regular Windows build is still usable. Only the Microsoft Store package generation failed or was skipped.