Fix Microsoft Store Error 0x80073d0a?

To fix Microsoft Store error 0x80073d0a, you need to clear the Store’s cache and reset its data, which resolves the vast majority of cases. If that does not work, the next steps are to run the Windows Store Apps troubleshooter, check your system date and time, and re-register the Store app via PowerShell.

What Error 0x80073d0a Means

Error 0x80073d0a is a Windows Update and Store error that typically appears when you try to download, update, or launch an app from the Microsoft Store. The error message usually reads “Something unexpected happened” or “The application was not able to start correctly.” The code itself points to a problem with the delivery or registration of the app package, meaning Windows cannot properly install or verify the app’s files.

This error is not specific to one app; it can affect games, utilities, or system apps. It is most commonly reported after a Windows update, when the Store’s cache has become corrupted, or when a previous app installation left behind incomplete files. Unlike errors that indicate a bad internet connection or a full disk, 0x80073d0a usually points to a local software conflict rather than a network or hardware problem.

Why the Cache Gets Corrupted

The Microsoft Store relies on a local cache to speed up downloads and manage app licenses. This cache stores temporary files, thumbnails, and metadata about the apps you browse. Over time, these files can become corrupted due to interrupted downloads, sudden system shutdowns, or conflicts with antivirus software that quarantines parts of the cache. When the cache is damaged, the Store cannot correctly read the app package, triggering error 0x80073d0a.

Another common cause is a mismatch between the Store’s cached license and the actual Microsoft account permissions. If your account was recently changed or if the system clock is wrong, the Store may reject the app package as invalid. The system clock is a surprisingly frequent culprit because Windows uses it to verify the digital signatures on app packages; if the date or time is off by more than a few minutes, the signature check fails.

Step-by-Step Fixes

Work through these fixes in order. Most users resolve the error with the first two steps, but the later steps cover deeper system issues.

Clear the Store cache. Press Windows + R, type wsreset.exe, and press Enter. A blank command prompt window will open, and it may stay open for a minute or two. When it closes, the Store will open automatically. This resets the cache without deleting your installed apps or account information.
Run the Windows Store Apps troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10). Select Windows Store Apps and run it. This tool automatically detects and fixes common Store issues, including corrupted cache files and misconfigured permissions.
Check the system date and time. Right-click the clock in the taskbar and select Adjust date/time. Ensure Set time automatically is on, then toggle it off and on again. If the time zone is wrong, fix it manually. Restart the Store and try again.
Re-register the Store app. Open PowerShell as administrator (right-click the Start button and select Windows Terminal (Admin) or PowerShell (Admin)). Run the following command and wait for it to finish:
Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
This command reinstalls the Store’s app registration without downloading anything new.
Repair the Windows Update service. Open Command Prompt as administrator and run these commands one at a time:
net stop wuauserv
net stop cryptSvc
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
This resets the Windows Update cache, which the Store depends on for some downloads.
Create a new user account. If the error persists only for your current user profile, create a new local administrator account in Settings > Accounts > Family & other users. Log into the new account and test the Store. If it works, the issue is with your original profile’s permissions, not the system.

What to Try If the Error Persists

If none of the above steps work, the problem may be deeper. First, check for pending Windows updates. Go to Settings > Windows Update and install any available updates, then restart. A partially installed update can leave the Store in an inconsistent state.

Second, review your antivirus or firewall settings. Some third-party security suites block the Store’s background services. Temporarily disable the real-time protection (do not leave it off) and try the download again. If it works, add an exception for the Store app in your security software.

Third, consider a system file check. Open Command Prompt as administrator and run sfc /scannow. This scans for corrupted system files and repairs them. If it finds issues it cannot fix, run DISM /Online /Cleanup-Image /RestoreHealth to repair the system image itself.

Common Misconceptions

A frequent misconception is that error 0x80073d0a means your Microsoft account has been banned or that you need to reinstall Windows. Neither is true. The error is almost always a local software issue, and a full reinstall is rarely necessary. Another misconception is that clearing the Store cache will delete your downloaded apps; wsreset.exe only removes temporary files, not installed applications or licenses.

Some users also believe that the error is caused by a full hard drive. While low disk space can cause other Store errors, 0x80073d0a is not directly tied to storage capacity. If your disk is full, the Store will typically show a different error about insufficient space, not this one.

Alternatives to the Microsoft Store

While you are troubleshooting, you can still install apps from other sources. Many popular apps that appear in the Store are also available as direct downloads from the developer’s website. For example, Spotify, Discord, and many games have standalone installers. However, apps that rely on the UWP (Universal Windows Platform) framework, such as certain Xbox titles or built-in Windows apps, generally need the Store to function correctly.

You can also use the winget command-line tool, which is built into Windows 10 and 11. Open Command Prompt and type winget install "App Name" to install many applications without using the Store interface. This bypasses the Store’s graphical layer but still uses the same underlying package system, so it may not work if the core Store service is broken.

Frequently Asked Questions

Will resetting the Store delete my apps?

No. Running wsreset.exe clears only the cache and temporary files. Your installed apps, game saves, and Microsoft account sign-in remain intact. The Store will simply re-download thumbnails and metadata the next time you open it.

Why does this error happen only for one app?

If only one app fails, the app’s package may be corrupted or its license may have expired. Try uninstalling that specific app, then reinstall it from the Store. If the error persists, the app’s developer may have released a broken update; check the app’s support page for known issues.

Can I fix this error without an administrator account?

Most fixes require administrator privileges, especially the PowerShell re-registration and the Windows Update service commands. If you are on a standard user account, you will need to ask the administrator to run these steps. The wsreset.exe command, however, works on standard accounts.

Is error 0x80073d0a the same as 0x80073d0b?

No. Error 0x80073d0b is a different code that usually indicates the app you are trying to install is not compatible with your version of Windows. Error 0x80073d0a is about the app package’s registration and delivery, not compatibility. The fixes for the two errors are different, so check the exact code before troubleshooting.

How long does the wsreset command take?

It usually takes 30 seconds to a few minutes. The command prompt window stays open during the process. If it stays open longer than five minutes, close it and try running the Store directly; the cache may have been cleared successfully even if the window did not close automatically.

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 →