Fix Error 0x80860010 “This App Made Too Many Requests” on Windows 11 | Vikas Kapadiya

Error 0x80860010 “This app made too many requests. Press Retry to continue.” when signing into a Microsoft account in Edge, the Store, or Xbox. The cause is a corrupt cached credential. Clear it with cmdkey and reboot.
A friend pinged me last week. Every time he tried to sign into his Microsoft account — in Edge, then the Store, then the Xbox app — Windows threw the same modal:
Written out, the message reads:
Retry did nothing. Retry again did nothing. He had already reinstalled the app, cleared Edge’s cache, and run the Store troubleshooter. None of it helped, because none of it touched the actual cause.
The fix took about two minutes: clear the cached Microsoft credentials in Windows, then reboot. This post explains why “too many requests” is misleading here, and gives you three ways to clear the credential — a script, a safer targeted script, and a fully manual path.
0x80860010 reads like a rate limit, and the message all but tells you to wait it out. That framing sends people down the wrong road — waiting, retrying, reinstalling.
What is really happening: Windows caches your Microsoft account tokens in Credential Manager. When one of those cached entries is stale or corrupt, the app keeps presenting the bad token to Microsoft’s sign-in service. The service rejects it, the app immediately retries with the same bad token, and after a few loops you trip a throttle. The throttle is real. The token behind it is the problem.
That is why pressing Retry makes things worse, not better. Each press feeds the same corrupt credential back into the loop.
The error often shows a correlation GUID of ff000000-0000-0000-0000-000000000000. A request that reaches the service comes back with a real GUID. All zeros means the call failed locally, before it ever got a proper handshake — consistent with a bad cached credential, not a server-side limit.
This same corrupt-credential cause shows up under other codes too. If you have seen 0x8007000e or 0x80004005 while signing into your Microsoft account, the Store, or Xbox, the fix below clears all three.
Windows ships cmdkey, a command-line tool for the credential store. You can list every saved credential and delete the stale Microsoft ones. This script does exactly that — it enumerates saved credentials and removes each target.
Create a file named clear-creds.bat, paste this in, and save:
Double-click it and let it run. Line by line:
Then reboot. This step is not optional. Several people — my friend included — cleared the credentials, tried to sign in immediately, and still failed. A restart lets Windows drop the in-memory copies and fetch fresh tokens on next sign-in. After the reboot, sign back into Edge, the Store, or Xbox. It works.
The loop removes all targets cmdkey reports: saved Remote Desktop logins, mapped network-share passwords, and some app credentials, along with the Microsoft ones. Nothing here is destructive — Windows re-prompts and re-saves each as you use it again — but you will re-enter a few passwords. If that matters to you, use the targeted script below instead.
If you would rather not clear unrelated logins, filter the list to the credentials that actually matter for this error. Microsoft account tokens are stored under targets that start with MicrosoftAccount, WindowsLive, or XblGrts (Xbox):
Same idea, narrower blast radius. It touches only the account tokens tied to the sign-in loop and leaves your RDP and network-share credentials alone. Reboot afterward, same as before.
If the broad script fixed everything and the targeted one leaves you still stuck on the Xbox app specifically, the XblGrts entries are the ones to clear — the Xbox app keeps its own grant tokens separate from the main account token.
If you would rather see what you are deleting, do it in the GUI. Same outcome, more clicks.
Removing these does not delete your Microsoft account or your data. It only clears the local cached tokens, which Windows rebuilds on your next sign-in.
0x80860010 is not really a rate-limit problem, and no amount of waiting or reinstalling fixes it. A single corrupt token in Credential Manager keeps getting replayed until the sign-in service throttles the app. Clear the cached credentials with cmdkey, reboot so Windows forgets the in-memory copies, and sign in fresh.
If you remember one command from this post, make it this:
That is the credential store the error is stuck on. Once you clear it and reboot, the loop is gone.
Credit where it is due: the cmdkey approach comes from a Reddit comment by u/Fipdo that has quietly rescued a lot of people since 2023 — and still worked when my friend hit this in 2026.
More field notes when the next problem is specific enough to be useful.
Gandhinagar, India · Usually replies by email.