Fix Windows 10 Store Error 0x87af000b

The Windows 10 Store error 0x87af000b, usually accompanied by “Something went wrong,” is a licensing or account-sync problem that appears when the Store can’t verify your right to download or update an app. The fix is to reset the Store cache, re-sign into your Microsoft account, and check that your system date/time are correct — these three steps resolve the error in most cases.

What Causes Error 0x87af000b?

This error code is part of the Microsoft Store’s “licensing” family. It means the Store tried to confirm that you own an app or that your device is authorized to install it, but the confirmation failed. Common triggers include:

A corrupted Store cache file that holds outdated license data.
A Microsoft account that has logged out or lost its sync token.
System clock or time zone set incorrectly, which breaks the secure handshake with Microsoft’s license servers.
An app that was installed from a different account (e.g., a work or school account) and is now being updated under a personal account.
A pending Windows update that has left the Store in a partially updated state.

Unlike some Store errors that point to network problems (like 0x80072efd), 0x87af000b is almost always about authorization, not connectivity.

How to Fix It: Step-by-Step

Try these in order. The first two fix the majority of cases; the later ones are for stubborn situations.

Run the Windows Store Apps Troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Store Apps, and run it. This automatically resets the cache and checks for common issues.
Reset the Store cache manually. Press Win + R, type wsreset.exe, and press Enter. A blank Command Prompt window will open; wait for it to finish and close. The Store will open automatically. This clears the local cache without deleting your installed apps or accounts.
Re-sign into your Microsoft account. Open the Store, click the profile icon at the top right, select Sign out, then sign back in. If you use multiple accounts, make sure the one you’re signed into is the one that originally purchased or installed the app.
Check date, time, and time zone. Right-click the clock in the taskbar, choose Adjust date/time, and ensure Set time automatically and Set time zone automatically are both on. If they’re already on, toggle them off, restart, and turn them back on.
Re-register the Store app via PowerShell. Right-click the Start button, select Windows PowerShell (Admin), and run: Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}. This re-registers the Store without affecting your data.
Install pending Windows updates. Go to Settings > Update & Security > Windows Update and click Check for updates. Restart after installing.

If none of these work, the problem may be tied to a specific app that was installed under a different user profile. Try removing that app and reinstalling it from the Store while signed into the correct account.

Why Does the Error Happen After a Windows Update?

Windows updates often change how the Store handles licenses. When a major feature update (like version 21H2 or 22H2) installs, it may reset some account tokens or modify the licensing service. If the update interrupted an app installation, the Store can lose track of which apps your account owns. The error 0x87af000b then appears when you try to update or launch that app. The re-registration step (PowerShell) is particularly effective in this scenario because it rebuilds the Store’s package registration without requiring a full system restore.

Is This Error the Same as 0x87af000c or 0x803F8001?

No, but they are related. Error 0x87af000c is often a network or server issue, while 0x803F8001 (the “This app can’t run on your PC” error) is a compatibility problem. 0x87af000b specifically points to a licensing check failure. If you see 0x87af000c, try restarting your router and checking Microsoft’s service status page. If you see 0x803F8001, the app may not support your Windows version or processor architecture. Knowing the difference helps you avoid wasting time on the wrong fix.

Can This Error Affect Apps Already Installed?

Sometimes yes. If the error appears when you try to launch an app rather than update it, the license for that app has become invalid locally. The app may still open if you run it from the Start menu, but it might crash or prompt you to sign in. In that case, the re-sign and cache reset steps are your best bet. If the app was a free download that you never “purchased” (i.e., clicked Get), the Store may have lost the license record. Reinstalling the app usually restores it.

Frequently Asked Questions

Will resetting the Store cache delete my apps or data?

No. wsreset.exe only clears the Store’s temporary files and cache. It does not remove installed apps, game saves, or account credentials. You will need to sign back into the Store, but your apps remain untouched.

Why does the error only happen for one specific app?

That usually means the app was installed under a different Microsoft account than the one you’re currently signed into. For example, if you used a work account to install an app and then switched to a personal account, the Store can’t verify the license. Sign out of the Store and sign in with the account that originally installed the app.

I tried everything, but the error persists. What else can I do?

If you’ve gone through all the steps, the next option is to create a new local user account and sign in with it. If the Store works there, your original user profile may be corrupted. You can migrate your files and then switch to the new account. As a last resort, use the Reset this PC feature (keeping your files) to reinstall Windows without losing personal data.

Is this error a sign of a virus or malware?

No. 0x87af000b is a legitimate Store licensing error, not an infection indicator. However, if you also notice unusual pop-ups or system slowdowns, run a full Windows Defender scan to rule out malware that might have tampered with system files.

Does this error affect Windows 11 too?

Yes, the same error can appear on Windows 11, and the fixes are nearly identical. The troubleshooting steps, PowerShell command, and cache reset all work on Windows 11. The main difference is the Settings layout, but the menu names are similar.

Can I avoid this error in the future?

Keep your system date/time set to automatic, always sign in with the same Microsoft account, and let Windows updates install completely before using the Store. If you frequently switch between accounts, sign out of the Store when you’re done to avoid token conflicts.

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 →