Skip to content
Discussion options

You must be logged in to vote

The Solution

This loop occurs because active background Windows applications (such as Phone Link, Windows Clock, Photos, or Widgets) hold an open lock on the older WinAppRuntime files. Because they are actively running, the native AppX package deployment engine rejects standard overwrites or uninstallation attempts.

To fix the deployment loop, you must bypass the storefront mechanics completely by running the direct standalone installer executable found inside the stable redistributable ZIP bundle:

  1. Open Task Manager and force-close any running background UWP applications (e.g., Photos, Phone Link, Clock, Widgets).
  2. Visit the official Latest Windows App SDK downloads page.
  3. Scroll down to the

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by CommanderDusK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant