Fix Error 0x80073d0b: Windows Store App Update

Error 0x80073d0b appears when Windows can’t install or update a Microsoft Store app, usually because of a corrupted cache, a stalled download, or a permissions conflict. The most reliable fix is to clear the Windows Store cache and then reset the problematic app, which resolves the majority of cases without touching system files.

What Error 0x80073d0b Means

This error code is part of the Windows Update and Store error family. It typically shows up as “Something happened and this app couldn’t be installed” or “This app couldn’t be updated” when you try to install, update, or launch an app from the Microsoft Store. The code itself translates to ERROR_INSTALL_POLICY_FAILURE in Windows system internals, which points to a policy or permission problem rather than a hardware fault.

Common triggers include:

A corrupted Store cache that blocks new downloads
An app that was partially installed or left in a pending state
User account permissions that prevent Store apps from writing to their own folders
Group Policy or parental controls restricting app installation
A stalled background download that locks the app’s package

Why the Store Cache Causes This Error

The Microsoft Store uses a local cache to speed up browsing and downloading. When that cache becomes corrupted—often after a forced shutdown, a failed update, or a disk-full event—the Store can’t read its own metadata correctly. The result is that it rejects new installations or updates with error 0x80073d0b even though your internet connection and account are fine.

Clearing the cache forces the Store to rebuild its index from scratch. This is a safe, non-destructive process: it does not delete your installed apps, personal files, or Store purchases. It only removes temporary files that Windows can regenerate automatically.

How to Fix Error 0x80073d0b (Step-by-Step)

Try these fixes in order, testing the Store after each one:

Run the Windows Store Apps troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters, select Windows Store Apps, and run it. This tool automatically detects and repairs common Store issues.
Clear the Store cache. Press Win + R, type wsreset.exe, and press Enter. A blank Command Prompt window will appear, then close automatically when the cache is cleared. The Store will open afterward.
Reset the problematic app. Go to Settings > Apps > Installed apps, find the app that fails, click the three-dot menu, choose Advanced options, then click Reset. This clears the app’s local data and re-registers it with Windows.
Re-register all Store apps via PowerShell. Open PowerShell as administrator and run: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. This refreshes the app registry without reinstalling anything.
Check your account permissions. Ensure you are logged in as an administrator. If you’re on a child account, parental controls may block installations—temporarily disable them in Settings > Accounts > Family & other users.
Restart the Windows Update service. Open Services (press Win + R, type services.msc), find Windows Update, right-click and choose Restart. Do the same for Microsoft Store Install Service if present.

What to Do If the Error Persists

If the steps above don’t work, the issue is likely deeper—either a corrupted system file or a policy conflict. Run the System File Checker by opening Command Prompt as administrator and typing sfc /scannow. This checks and repairs protected Windows files. After it finishes, run DISM /Online /Cleanup-Image /RestoreHealth to fix the underlying system image.

Another option is to uninstall the app entirely and reinstall it. Go to Settings > Apps > Installed apps, click the app, choose Uninstall, then download it again from the Store. This often clears any corrupted package remnants that the Reset option misses.

Common Misconceptions About This Error

Many users believe error 0x80073d0b means their Microsoft account is banned or their device is broken. Neither is true. The error is a generic permission failure, not a security flag. It also does not mean your internet connection is faulty—the Store can download other apps fine while one specific app fails.

Another misconception is that deleting the entire Store folder or disabling the Store via Group Policy is a fix. That will only make the problem worse, as it removes the Store’s ability to function at all. Stick to the built-in reset tools and PowerShell commands, which are designed for this exact scenario.

Preventing Future Occurrences

To reduce the chance of seeing this error again:

Keep Windows Update current—Microsoft regularly patches Store-related bugs.
Ensure your system drive has at least 10–15% free space; a full disk can interrupt app installations.
Avoid force-closing the Store or shutting down during an update.
If you use third-party “cleaner” tools, disable their Store cache-cleaning features—they can corrupt the cache.

Frequently Asked Questions

Will clearing the Store cache delete my apps? No. wsreset.exe only removes temporary files and store settings. Your installed apps and purchases remain untouched.

Can I fix this without an administrator account? Most fixes require admin rights, especially the PowerShell command and service restarts. If you’re on a standard user account, ask the administrator to run the steps.

Does this error affect all Store apps or just one? It can affect a single app or all of them. If it’s one app, reset that app first. If it’s all apps, run the cache reset and the PowerShell re-registration.

Is error 0x80073d0b the same as error 0x80073d0a? No. 0x80073d0a usually indicates a licensing or entitlement issue, while 0x80073d0b is a policy/permission failure. The fixes overlap, but the root causes differ.

What if the Store itself won’t open after the reset? Restart your PC. If it still won’t open, re-register the Store app using the PowerShell command listed above, but replace Get-AppXPackage with Get-AppXPackage -Name Microsoft.WindowsStore.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →