The next decisive check is whether installed version 4.1.1 came from an MSIX bundle, because an installed MSIX bundle cannot be updated by the flight’s standalone CalcWide_4.1.2.0_x64.msix; the flight must provide a compatible bundle in that case.^1^

1. Compare the installed and flight package formats

In Partner Center, open the submission that delivered 4.1.1 and inspect its Packages page:

• If 4.1.1 was an .msixbundle or .appxbundle, while 4.1.2 is the stated standalone .msix, that update path is unsupported.
• Publish 4.1.2 to the existing flight as an .msixbundle containing the applicable x64 package. This requires repackaging, but does not require uninstalling 4.1.1 or releasing 4.1.2 publicly.
• If 4.1.1 was also a standalone MSIX, continue below.

MSIX can update to MSIX bundle, but an installed bundle must continue receiving bundle updates.^1^

2. Verify package applicability, not the checks already completed

The Store offers the highest-versioned package that is applicable to the particular device.^2^ Check these remaining conditions:

1. Processor architecture
   • Confirm the test PC is x64 Windows, not ARM64 Windows.
   • Your flight contains only an x64 package, so devices on an unsupported architecture are excluded. Architecture selection limits which devices can run the package.^3^
2. OS build
   • Run winver and confirm the tester is on build 19041 or later, matching the package minimum.
   • Package flights themselves require Windows.Desktop build 10586 or later, but your package’s higher minimum build is the effective requirement here.^4^
3. Device family
   • On the 4.1.2 flight’s Packages page, confirm the package supports the same desktop device family as the public submission.
   • Flight members can obtain packages only from their selected flight; the Store does not fall back to the non-flighted submission to fill a device-family gap. Device-family availability is also bounded by the non-flighted submission.^4^
4. Package family
   • Compare the package Name and Publisher metadata between 4.1.1 and 4.1.2.
   • An update must remain in the same package family, which is derived from both values. Matching only the visible package identity name is insufficient if the Publisher differs.^1^

3. Account association and flight selection

There is no separate tester entitlement, MSA token, or package-flight download API to configure. Delivery is performed by the normal Microsoft Store client for the Microsoft account associated with the known-user entry.^5^

Since the account and group membership are already verified, only account-context details remain relevant:

• The known-user entry must be the email address associated with that Microsoft account.^6^
• If membership was recently edited or resaved, allow up to 30 minutes for the change to take effect; no new flight submission is required.^6^
• If the tester belongs to multiple flight groups, the highest-ranked applicable flight wins even when another flight contains a higher package version. Rank 2 correctly outranks the non-flighted submission at rank 1, but check for any additional flight ranked above 2.^4^

After any membership propagation period, use Microsoft Store → Library → Get updates. This requests currently eligible updates without uninstalling the app.^7^

4. Escalate if every applicability condition matches

If both releases are standalone MSIX packages, the PC is x64 build 19041+, the device families and package-family metadata match, and no higher flight takes precedence, the available documentation does not identify another publisher-side eligibility switch.

Open Windows developer support and provide:

• Product ID and flight submission ID
• Flight name and rank
• Publication timestamp
• Tester account address in redacted form
• Windows build and architecture
• Installed package full name/version
• 4.1.1 and 4.1.2 package formats
• Package Name, Publisher, device family, and minimum OS from both manifests
• Time of the latest Store update check

Windows developer support is the documented escalation route for Partner Center and app-publishing issues.^8^

References

1. App package updates
2. App package requirements for MSIX app
3. App package architectures
4. Package flights
5. How to retrieve MSA token from WinUI application to download Package Flight bundles - Microsoft Q&A
6. Create customer groups
7. Get updates for apps and games in Microsoft Store | Microsoft Support
8. Parallel package flighting (Preview)