Fix Microsoft Store Error 0x803fb112 on Windows 11
Why This Is Happening
You open the Microsoft Store, it immediately tells you that you need to update it , and then it slaps you with error code 0x803fb112. You can't update the Store itself. You can't download new apps. You can't even update existing ones. The whole thing is just stuck in a broken loop that Microsoft's own error message does absolutely nothing to explain.
I've seen this exact error on dozens of machines, and it almost always comes down to one of a handful of root causes. The frustrating part is that 0x803fb112 is a licensing and acquisition error , it means the Store's internal licensing service failed to complete a transaction. That could be triggered by corrupted cache files, a stale or mismatched Microsoft account token, a broken Windows Update dependency, or background services like ClipSVC (Client License Service) that have quietly stopped running.
On Windows 11 especially, the Store relies on a web of background services that all have to be healthy at the same time. If your machine went through a major Windows update, had a hard shutdown, or if your account credentials got cached incorrectly after a password change, any one of those can tip the licensing system into this error state. Domain-joined machines or devices enrolled in Microsoft Intune see this more often than standalone home PCs, but home users absolutely get hit by it too.
The other common trigger is a corrupted Store cache. The Store keeps a local cache at %LocalAppData%\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\LocalCache, and when those files get out of sync with what Microsoft's servers expect, you get exactly this kind of acquisition failure. Antivirus software or disk cleanup tools sometimes prune files from that directory incorrectly, which causes the same symptom.
Here's what makes it particularly annoying: Microsoft's error message just says something went wrong. There's no guidance. No next step. Just a code that means nothing to most people. That's exactly why you're here, and I'm going to walk you through every fix, from the 30-second reset that solves it for most people, right through to the registry-level repair for the edge cases.
Browse all our Microsoft fix guides → if you're dealing with other Windows 11 issues alongside this one.
The Quick Fix, Try This First
Before you go digging through settings and services, try this first. It resolves Microsoft Store error 0x803fb112 in about 60% of cases and takes under two minutes.
This is the WSReset tool, a built-in Microsoft Store reset utility that clears the cache, resets the Store's internal state, and forces it to re-establish its connection with Microsoft's licensing servers. It doesn't touch your installed apps or your account settings.
Here's how to run it:
- Press Win + R to open the Run dialog.
- Type exactly:
wsreset.exeand press Enter. - A black command prompt window will open. Don't close it. It will appear to do nothing for about 30–60 seconds, that's normal. It's working.
- The command prompt will close automatically, and the Microsoft Store will launch by itself.
- Once the Store opens, go to Library (bottom-left icon) and click Get updates in the top-right corner.
If the update completes without the 0x803fb112 error, you're done. If the error comes back, or if the Store opens but still refuses to update or download apps, keep going, the step-by-step section below covers every remaining scenario.
wsreset.exe from there. Running it as a limited user sometimes produces no error but also no result, the cache reset silently fails without admin context.
If WSReset didn't fix Microsoft Store error 0x803fb112, the next most common cause is a stale authentication token. Your Microsoft account credentials are cached locally, and if that cached token has expired, been invalidated by a password change, or corrupted after a Windows update, the Store's licensing service can't authenticate your purchase rights, which is exactly what this error code represents.
Open the Microsoft Store. Click your profile icon in the top-right corner of the Store window. Select your account name and choose Sign out. Once you're signed out, close the Store completely, right-click the taskbar icon and choose Close window, or press Alt + F4.
Now go to Settings → Accounts → Your info. Confirm that you're signed into Windows itself with your Microsoft account (not just a local account). If you see "Local Account" there, that's a separate issue we'll address in the Advanced section.
Reopen the Microsoft Store. Click the profile icon again and choose Sign in. Use your Microsoft account email and password. When prompted, complete any two-factor authentication. After signing back in, go to Library → Get updates.
You should see the Store begin downloading its own update, followed by any pending app updates. If you still see 0x803fb112, the token itself is fine, the problem is elsewhere. Move to Step 2.
The Microsoft Store doesn't operate independently. It relies on several Windows background services, and two of them are particularly important when you're hitting 0x803fb112: Windows Update (wuauserv) and ClipSVC, the Client License Service. ClipSVC is specifically responsible for managing app licensing from the Store. When it's stopped or in an error state, Store transactions fail with this exact error code.
Open an elevated PowerShell prompt. Right-click the Start button and choose Windows Terminal (Admin), then type powershell if it opened in Command Prompt mode. Now run these commands one at a time:
Stop-Service -Name ClipSVC -Force
Stop-Service -Name wuauserv -Force
Stop-Service -Name bits -Force
Start-Sleep -Seconds 5
Start-Service -Name bits
Start-Service -Name wuauserv
Start-Service -Name ClipSVCAfter running those, verify the services started correctly:
Get-Service ClipSVC, wuauserv, bits | Select-Object Name, StatusAll three should show Running. If ClipSVC shows Stopped again immediately, that's a sign of a deeper service dependency issue, jump ahead to the Advanced section. If all three are running, open the Store and test again. Many users who see Microsoft Store not updating on Windows 11 find this step alone clears the error.
Windows 11 includes a built-in troubleshooter specifically for Store app issues. It's not magic, but it does catch and automatically repair a specific set of known problems, including permission issues on Store app package folders and misconfigured service dependencies. It takes about two minutes and requires no technical knowledge to run.
Open Settings (Win + I). Navigate to System → Troubleshoot → Other troubleshooters. Scroll down until you find Windows Store Apps. Click the Run button next to it.
The troubleshooter will scan your system. Watch what it reports. If it says "Fixed" or "Changes were made," that's a good sign. If it says "Couldn't fix", note down the specific item it failed to fix, because that tells you exactly which component needs manual attention.
Common things this troubleshooter repairs automatically: incorrect permissions on %ProgramFiles%\WindowsApps, blocked Store-related firewall rules, and corrupted package registration entries. After it completes, click Close and restart your PC. Don't skip the restart, some of the changes it makes only take effect after a reboot.
After restarting, open the Store and go to Library → Get updates. Check if the 0x803fb112 error is gone. If the troubleshooter reported it found and fixed issues, there's a good chance you're done at this point.
This step is the heavy artillery for fixing a corrupted Microsoft Store installation on Windows 11. When the Store's own package registration gets corrupted, which can happen after a failed update, a botched system restore, or third-party cleanup tools, WSReset alone won't fix it. You need to re-register the entire Store package from scratch using PowerShell.
Don't worry, this doesn't delete the Store or your apps. It re-registers the package manifest, which refreshes all internal configuration, permissions, and licensing hooks.
Open Windows Terminal (Admin). Paste and run this command exactly as written:
Get-AppXPackage -AllUsers -Name Microsoft.WindowsStore | ForEach-Object {
Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
}You may see some red warning text scroll by, that's normal. PowerShell sometimes reports non-fatal errors during this process. Wait for it to finish completely (the prompt returns to PS C:\>).
Now re-register the full suite of Microsoft Store framework packages too. These are dependencies the Store needs to function:
Get-AppXPackage -AllUsers | ForEach-Object {
Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
} 2>&1 | Out-NullThis one takes a few minutes. After it completes, restart your PC. When you log back in, open the Microsoft Store, you should be able to update it and download apps without seeing error 0x803fb112 again.
If none of the above steps have cleared Microsoft Store error 0x803fb112 yet, there's a real possibility that the underlying Windows system files are corrupted. The Store depends on core Windows components, WinRT runtime libraries, the component store, licensing DLLs, and if any of those are broken, no amount of Store-level resets will fix the problem. You have to go deeper.
Windows has two built-in repair tools for exactly this scenario: SFC (System File Checker) and DISM (Deployment Imaging Service and Management Tool). Run them in the correct order, DISM first to repair the component store that SFC draws from, then SFC to repair individual system files.
Open Windows Terminal (Admin) and run this first:
DISM /Online /Cleanup-Image /RestoreHealthThis connects to Windows Update servers to download clean copies of any corrupted system components. It takes 10–20 minutes. Don't close the window. After it completes and reports The restore operation completed successfully, run:
sfc /scannowSFC will scan and repair corrupted protected system files. When it finishes, you'll see one of three results: "no integrity violations found" (system files are clean), "found corrupted files and successfully repaired them" (fixed), or "found corrupted files but was unable to repair some of them" (proceed to the Advanced section, you likely need an in-place upgrade repair).
Restart after both tools complete. Open the Store and test. For the vast majority of users dealing with persistent Microsoft Store 0x803fb112 Windows 11 issues, this is the step that finally resolves it.
Advanced Troubleshooting
Still seeing 0x803fb112? Let's go deeper. These approaches cover enterprise environments, Group Policy conflicts, registry-level fixes, and Event Viewer analysis that pinpoints exactly what's blocking the Store.
Check Event Viewer for the Real Error
Before touching anything else, look at what Windows is actually logging. Open Event Viewer (search for it in Start). Navigate to Applications and Services Logs → Microsoft → Windows → Store → Operational. Filter for errors around the time you tried to update the Store. You're looking for Event IDs in the 5000–5010 range, which are Store licensing failures. The detailed error text will often name a specific component, a failed network call, a missing DLL, or an access denied on a specific registry key, that points you directly to the fix.
Fix the ClipSVC Registry Key
If ClipSVC keeps stopping and won't stay running, a corrupted token store is usually why. You need to clear it. Press Win + R, type regedit, and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ClipSVCRight-click the tokens.dat value (if present) and rename it to tokens.dat.bak. Then restart ClipSVC from Services (Win + R → services.msc). The service will regenerate a clean token store on next launch. Warning: export this registry key first before modifying anything, press File → Export in regedit with this key selected.
Group Policy and Intune Conflicts
On domain-joined or Intune-enrolled machines, a Group Policy setting can block Store updates entirely. Open Group Policy Editor (only available on Windows 11 Pro/Enterprise, type gpedit.msc in Run). Navigate to Computer Configuration → Administrative Templates → Windows Components → Store. Check whether "Turn off the Store application" or "Turn off Automatic Download and Install of updates" is set to Enabled. If your organization has locked these down, you'll need your IT administrator to adjust the policy, the Store literally cannot update when those policies are enforced.
Proxy and Firewall Interference
The Microsoft Store needs outbound HTTPS access on port 443 to *.microsoft.com, *.windowsupdate.com, and storecatalogrevocation.storequality.microsoft.com. Corporate firewalls or third-party security software (especially products from Bitdefender, ESET, or Kaspersky) sometimes intercept Store licensing calls with SSL inspection, which breaks the certificate chain and triggers acquisition errors like 0x803fb112. Temporarily disabling your VPN or security software and retrying is a fast way to test this hypothesis.
In-Place Upgrade as Last Resort
If SFC reported it couldn't repair corrupted files, an in-place upgrade (repair install) is your cleanest option. Download the Windows 11 ISO from Microsoft, mount it, run setup.exe, choose Upgrade this PC now, and keep your files and apps. This reinstalls Windows system files without wiping your data, and it resolves corruption that no other tool can reach.
winver) and the full event log entries from Event Viewer ready when you contact them.
Prevention & Best Practices
Once you've fixed Microsoft Store error 0x803fb112, the last thing you want is to end up back here in three months. The good news is that most of the things that cause this error are preventable with a few simple habits.
The biggest one: don't use third-party system cleanup tools on folders under %LocalAppData%\Packages. Tools like CCleaner, Advanced SystemCare, and similar utilities sometimes aggressively prune files in Store app cache directories, not realizing those files are actively used for licensing. The Store's cache is not junk, touching it causes exactly the kind of corruption that leads to 0x803fb112.
Keep Windows Update running on schedule. The Microsoft Store's internal components are updated through Windows Update, not just through the Store itself. Machines that have Windows Update paused for months at a time end up with mismatched Store framework versions, which breaks acquisition. If you've paused updates, set a reminder to unpause them at least once a month.
On shared or family PCs, make sure each user signs into Windows with their own Microsoft account rather than everyone sharing one account. When multiple people share a single account's cached credentials, token conflicts are much more common, and Store licensing failures like this one are a predictable result.
If you're on a corporate machine, talk to your IT team about Windows Store for Business or Microsoft Store for Education policies. Organizations that use those management tools can pre-approve apps so individual users never hit licensing errors in the first place.
- Set Windows Update to install updates automatically, never pause for more than 7 days at a time.
- Never run disk cleanup tools that touch
%LocalAppData%\Packages, exclude this folder from any cleanup software. - Sign in to Windows with a Microsoft account, not a local account, to keep Store licensing tokens fresh.
- Once a month, open Microsoft Store → Library → Get updates to keep all apps current before issues accumulate.
Frequently Asked Questions
Will WSReset delete my installed apps?
No, WSReset only clears the Microsoft Store's cache files, which are temporary data the Store uses to speed up browsing and downloads. Your installed apps, their data, your account information, and your purchase history are all stored separately and are completely untouched. Think of it like clearing browser cookies, your bookmarks and browsing history stay intact. The only thing you might notice after running it is that the Store feels slightly slower for the first launch or two while it rebuilds its cache.
Why does Microsoft Store say I need an update but then won't actually update?
This loop happens because the Store detected that a newer version of itself is available on Microsoft's servers, but when it tries to download the update package, the licensing acquisition step fails with error 0x803fb112. It's caught between knowing it needs to update and being unable to complete the transaction. The fix isn't to manually download a Store update, the Store must update itself. Clearing the cache with WSReset or re-registering the package via PowerShell breaks the loop and allows the update to proceed normally.
I can't install any apps at all from the Store, is this related to 0x803fb112?
Yes, directly. Error 0x803fb112 is a licensing acquisition failure, which means the Store can't validate your right to download or install any app, paid or free. Until the underlying licensing service issue is fixed, every install and update attempt will fail. The Store update itself is just the most visible symptom. Work through the steps in this guide sequentially, fixing the Store update error will also restore your ability to install and update other apps.
Does this error mean my Windows license is invalid?
No. Error 0x803fb112 is a Store app licensing error, not a Windows activation error. It has nothing to do with whether your copy of Windows itself is genuine or activated. You can verify your Windows activation status by going to Settings → System → Activation, if it says "Windows is activated," your license is fine. The 0x803fb112 error is specifically about the Store's internal app-licensing system, which is a completely separate mechanism from Windows activation.
The PowerShell re-registration command showed lots of red error text, did it fail?
Almost certainly not. When you run Add-AppxPackage against all installed packages, PowerShell generates warnings for packages that are already properly registered or that have minor version conflicts, it logs these as errors even though nothing went wrong. As long as the command didn't stop mid-way and return you to the PowerShell prompt (PS C:\>), it completed its run. The red text is PowerShell being overly verbose about non-fatal conditions. Restart your PC after the command finishes and test the Store, that's the real indicator of whether it worked.
I'm on a work laptop managed by IT, can I fix this myself?
It depends on what's causing it. You can safely try WSReset and signing out/in of the Store on any machine. But if the error is caused by a Group Policy setting, Intune compliance policy, or a corporate firewall rule, those are things only your IT team can change. Running gpresult /h gpresult.html in Command Prompt (save the file and open it in a browser) will show you all Group Policy settings applied to your machine and whether any of them restrict the Store. Share that report with your IT administrator if you find a Store-related policy in effect.