Microsoft Store installs outdated package (v1.3) instead of the published version (v1.4) (Simple Image Converter)

Question

Hello,

I am experiencing a critical issue with the distribution of my application Simple Image Converter.

Summary of the issue

• Version 1.4 has been successfully validated and published on the Microsoft Store.

On a PC that never had the application installed, version 1.4 installs correctly (installed size: 159 MB, matching the submitted package).

On a PC that previously had version 1.3 installed, even after uninstalling it, the Microsoft Store installs a package of 145 MB, which corresponds exactly to version 1.3.

In this scenario, the application fails to launch, likely due to a mix of files from versions 1.3 and 1.4.

Observed symptoms

The Store shows “Open” instead of “Install”, as if it is reusing a previously installed package.

The installed size (145 MB) matches the old version 1.3.

The Store does not download the 1.4 package on these machines.

The issue is reproducible on multiple PCs that previously had version 1.3 installed.

Technical details

The AppId is identical between versions 1.3 and 1.4.

• The installation directory is the same.

Version 1.4 uses a Nuitka build, while version 1.3 used PyInstaller (different internal file structure).

It appears that the Store is reusing a cached or staged package from version 1.3 instead of downloading the new version 1.4.

What I need

A purge of the outdated 1.3 package from the CDN and Store caches.

Verification that version 1.4 is correctly propagated and delivered to all users.

Confirmation that the Store will no longer reuse the 1.3 package for this AppId.

I am intentionally keeping one PC in the problematic state so I can test again once you have applied the necessary corrections.

Thank you for your assistance.

Answer 1

This behavior matches a known pattern where an older app package is reused instead of the newer one, leading to mixed or incompatible files between versions.

In environments where an older version of an app was previously installed, shared or cached files from that older version can be reused and effectively “downgrade” or corrupt the newer installation. A similar issue is documented for Microsoft Store apps when different versions are deployed or updated in mixed ways (for example, via management tools vs. online Store), where older shared files replace newer ones and prevent the updated app from working correctly.

Because this is a Store content and distribution issue (CDN/caching and package propagation for a specific AppId), resolution requires direct intervention from Microsoft Store/Partner Center support rather than local client troubleshooting. The necessary actions include:

1. Having Microsoft support verify that only the 1.4 package is active and offered for the app’s AppId in all rings and markets.
2. Having Microsoft support check for any stale or misconfigured deployment artifacts (such as older offline or staged packages) associated with version 1.3 that could still be targeted to existing devices.
3. Requesting that Microsoft purge or invalidate any cached 1.3 content associated with the app’s AppId on the Store/CDN side so that all devices, including those with prior 1.3 installs, are forced to retrieve the 1.4 package.

From the developer side, there is no supported way to purge Store/CDN caches or force global package invalidation; this can only be done by Microsoft. The correct next step is to open a support ticket through Partner Center (or the appropriate Microsoft support channel for Store publishers), provide:

• The app’s exact AppId and package identity details for 1.3 and 1.4.
• Reproduction details (fresh machine vs. machine with prior 1.3, observed installed sizes, and failure to launch).
• Confirmation that 1.4 is the only version that should be distributed.

Support can then:

• Confirm that 1.4 is fully propagated.
• Remove or disable any remaining 1.3 deployment artifacts.
• Trigger cache invalidation so that affected devices no longer receive or reuse the 1.3 package.

Keeping one device in the problematic state is useful; once Microsoft confirms the purge and propagation, that device can be used to validate that the Store now downloads and installs the correct 1.4 package and that the app launches successfully.

---

References:

• Microsoft Store app cannot start when one user installs an older version than the current version installed by another user in Windows 10
• Migrate Application Settings

Answer 2

But then, can you provide me with the correct direct link to open a support ticket through Partner Center (or through the appropriate support channel for Store publishers)?