Microsoft Store WinAppRuntime.Main Update Stuck on Error 0x80070032 (Dependency Validation Block)

Question

Microsoft Store WinAppRuntime.Main Update Stuck on Error 0x80070032 (Dependency Validation Block)

When attempting to check for updates in the Microsoft Store, WinAppRuntime.Main.1.8 fails to update continuously, displaying a generic "Something went wrong" alert with error code 0x80070032.

Attempted Troubleshooting Steps:

• Running wsreset.exe does not clear the stall.
• Using the Windows Package Manager in an elevated terminal fails to update:

    winget install -e --id Microsoft.WindowsAppRuntime.1.8 --source winget
    # Output: Found an existing package already installed. Trying to upgrade... No available upgrade found.
  

• Attempting a deep purge via Administrator PowerShell blocks the command:

    Get-AppxPackage -AllUsers *WindowsAppRuntime.1.8* | Remove-AppxPackage -AllUsers
    # Output: Remove-AppxPackage: Package failed updates, dependency or conflict validation.
  

Because native core Windows packages rely on this framework running in the background, the deployment engine locks the file system and blocks standard update methods. How can this deployment loop be bypassed to force a clean update of the runtime?

Answer 1

Hi @Caleb Sorrensen ,

Thanks for reaching out.

And thank you as well for coming back to share what worked on your side.

What makes this approach reasonable is that the Windows App Runtime is a shared dependency used by multiple apps and background components. Because of that, normal Store servicing or manual package removal can get blocked when parts of the runtime are still in use. Microsoft’s documentation explains that the runtime includes several related packages, including the Main, Framework, Singleton, and DDLM components, and that some of those pieces are specifically involved in managing updates and preventing changes while the runtime is active.

That is why the standalone installer can help here. It is an official Microsoft deployment path for the Windows App Runtime, and the Redistributable ZIP includes the installer together with the runtime packages for the supported architectures. Running that installer as Administrator is a much cleaner recovery method than trying to uninstall the runtime out from under Windows while other apps are still depending on it.

It may also help to mention that if a normal installer run does not clear the issue, Microsoft documents a --force option for WindowsAppRuntimeInstall.exe. That option can force an update of the runtime packages and shut down currently running Windows App SDK processes if needed, which makes it a useful extra step before moving on to more invasive troubleshooting.

For reference, these are the official Microsoft pages that support this approach:

Latest Windows App SDK downloads: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads

Windows App SDK download archive, including version 1.8: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads-archive

Windows App SDK deployment guide for the runtime installer and installer options: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/deploy-unpackaged-apps

Windows App SDK deployment architecture, including the role of Main, Singleton, and DDLM packages: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/deployment-architecture

General AppX deployment troubleshooting and diagnostic logs: https://learn.microsoft.com/en-us/windows/win32/appxpkg/troubleshooting

Hope this helps! If my explanation to your solution and the information I provided were helpful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.