Xbox Error 0x80860010 | Fix Sign In Loop Fast

Xbox error 0x80860010 points to a sign-in request loop, so clearing cached sign-in data and logging in fresh often restores access.

Seeing this code can feel random because it pops up in the middle of something normal, like launching a game, opening the Xbox app on PC, or trying to add an account on a console. The good news is that it’s rarely a “broken account” problem. It’s more often a stuck sign-in handshake, a cache that won’t let go, or a device that keeps retrying until the service says “too many requests.”

This guide walks you through fixes in the order that saves the most time. Start with the fast checks, then move to the deeper resets only if the code keeps returning. Take it step by step, and you’ll avoid deleting stuff you didn’t need to touch.

What Xbox Error 0x80860010 Means In Plain Terms

On both console and PC, this code commonly shows up when a Microsoft account sign-in request keeps repeating and the service begins refusing new attempts for a while. You might see messaging that hints at repeated requests, sign-in failure, or a general “something went wrong” flow.

The trigger can be simple: too many sign-in attempts in a short span, a partial sign-in token stored on the device, or a service hiccup that left your session in a half-signed state. Once the device is stuck in that loop, tapping “Try again” over and over tends to make it worse.

What You Notice	What It Often Points To	Best First Move
Error appears right after repeated sign-in tries	Rate limit or request loop	Wait, then restart device
Console signs in other accounts, not yours	Local profile token stuck	Remove profile, add again
Xbox app on PC fails while Store sign-in is weird too	Store/Xbox identity cache conflict	Reset app, clear Store cache

If the code popped up during a wider outage, the fix may be as simple as waiting it out. Before you change settings, it’s worth checking Xbox service status at xbox.com/status to see if sign-in is degraded in your region.

Fast Checks That Fix A Big Chunk Of Cases

These steps aim for the quick win: stop the loop, clear the most common temporary blocks, and try a clean sign-in once the device settles. Do them in order and resist the urge to mash the retry button.

Pause sign-in attempts — Put the controller down for 10–15 minutes so the service cooldown can pass.
Restart the console or PC — A full restart clears stuck background sign-in tasks that a quick app close won’t touch.
Verify the account works on the web — Sign in at account.microsoft.com to confirm your password and security prompts are fine.
Check date and time settings — Wrong time can break token validation and keep the device chasing a fresh session.

If you changed your password, turned on two-step verification, or approved a security prompt on another device, wait a few minutes before you try again. Account security changes can take a short moment to sync across sign-in endpoints.

Fixing Xbox Error 0x80860010 Step By Step

This section is the main event. Pick the path that matches where you see the error, then work down the list until the sign-in succeeds.

On Xbox Series X, Series S, Or Xbox One

Power cycle the console — Hold the power button on the console for about 10 seconds, unplug for 60 seconds, then boot up.
Remove the profile — Go to Settings > Account > Remove accounts, remove your account, then add it back.
Clear alternate MAC address — Go to Settings > General > Network settings > Advanced settings > Alternate MAC address, clear it, then restart.
Try a wired connection — Plug in Ethernet for the sign-in attempt to rule out Wi-Fi drops during token exchange.

When you add the account back, sign in once, then stop. If it fails, wait a bit before the next attempt. Rapid retries are one of the fastest ways to keep the loop alive.

On The Xbox App For Windows 10 Or Windows 11

Reset the Xbox app — Open Settings > Apps > Installed apps > Xbox, choose Advanced options, then use Repair, then Reset if needed.
Reset Microsoft Store — Use Settings > Apps > Installed apps > Microsoft Store, then Repair, then Reset.
Clear the Store cache — Press Win + R, type wsreset, then press Enter and wait for the Store to reopen.
Sign out everywhere in Xbox apps — Sign out of Xbox app, Xbox Game Bar, and Microsoft Store, restart the PC, then sign in to Store first.

A lot of PC cases come down to Store identity and Xbox identity getting out of sync. Signing in to the Microsoft Store first, then opening the Xbox app, often produces a clean token chain.

If You See A “Too Many Requests” Message

Stop retrying for a while — Treat it like a cooldown, because it is. Waiting can be the difference between one clean sign-in and an hour of looping.
Restart once after the wait — A restart after the cooldown clears queued background attempts that can fire the moment you reopen the app.
Try one sign-in attempt — One attempt, then pause again if it fails. This keeps you from triggering the same limit.

If you’re dealing with xbox error 0x80860010 on PC and the Microsoft Store is acting odd too, do the Store reset and wsreset steps even if the Store itself looks fine. The identity bits are shared under the hood.

Network And Time Settings That Can Trigger Sign-In Loops

Sign-in is picky about stability. Tiny interruptions that you’d never notice in a game can still break the authentication handshake. This section is about removing the subtle tripwires.

DNS And Router Cleanup

Restart your router and modem — Unplug both for 60 seconds, power modem first, then router, then try sign-in after the network settles.
Switch DNS on the console — Set DNS to a known public provider, then restart the console before trying to sign in again.
Remove custom network tweaks — Turn off ad-blocking DNS filters, “gaming accelerators,” or proxy-style features while testing.

If your home network uses strict filtering, sign-in endpoints can fail while regular browsing still works. A quick test is using a mobile hotspot for one sign-in attempt. If it works on the hotspot, the issue sits in the home network path.

Date, Time, And Region Settings

Set time automatically — On Windows, enable automatic time and time zone, then press Sync now in time settings.
Confirm console region matches your account — Check Settings > System > Language & location and confirm it’s correct.
Restart after changes — Time changes don’t always apply cleanly until a restart.

A mismatched clock can cause token validation to fail. The device then asks for a new token, then fails again, and the loop keeps spinning until the service refuses more requests.

Account And Device Cleanups When The Error Keeps Returning

If you’ve done the standard resets and the code still comes back, the goal changes. Now you want to remove stale credentials and rebuild a clean sign-in state across devices.

Clean Sign-In State Across Devices

Sign out on every device — Sign out of Xbox app, Store, Game Bar, console profile, and any extra Windows user sessions tied to the account.
Remove stored credentials on Windows — Open Credential Manager, remove entries tied to Microsoft, Xbox, and Store, then restart.
Re-add the account in the right order — Sign in to Microsoft Store first, then Xbox app, then Game Bar if you use it.

When people see xbox error 0x80860010 and keep trying different passwords, they often end up storing multiple failed credential attempts. Clearing those cached entries helps Windows stop reusing bad tokens.

Repair Gaming Services And Xbox Components On PC

Update Windows fully — Install pending updates, restart, then test sign-in before changing more settings.
Reinstall Gaming Services — Remove it from Installed apps, restart, then reinstall from Microsoft Store.
Repair system files — Run an elevated Command Prompt and use sfc /scannow, then restart when it finishes.

Gaming Services issues can block Xbox app authentication flows. If the Xbox app opens but sign-in fails with the same code after resets, reinstalling Gaming Services is one of the better “next” moves.

Last-Resort Console Moves That Still Protect Your Data

Clear local saved games only if prompted — Most saves live in the cloud, yet read the on-screen wording before you confirm anything.
Reset console and keep games and apps — Use Settings > System > Console info > Reset console, then choose the option that keeps games and apps.
Sign in once after reset — Do a single sign-in attempt after setup, then let the console sit for a minute before opening more apps.

This reset option is less drastic than it sounds. It rebuilds system settings and local account tokens while keeping installed games. It’s a solid choice when the console keeps looping during sign-in.

Keeping Sign-In Stable After You Fix It

Once the code is gone, a couple habits reduce the odds that it returns. The theme is simple: fewer rapid sign-in requests, fewer cached conflicts, and a cleaner path between device and service.

Avoid rapid retry loops — If sign-in fails, wait before the next attempt so you don’t trip request limits.
Keep the console in a clean power state — Restart once a week if you use instant-on features that keep sessions hanging around.
Update apps and system software — Install console updates and Microsoft Store app updates so authentication components stay aligned.
Use one account per session on PC — Switching between Store accounts and Xbox accounts can cause mismatched tokens.
Use steady internet for sign-in — Wired beats Wi-Fi for the sign-in step, even if you switch back to Wi-Fi later.

If you share the console, add accounts one at a time and let each sign-in finish before adding the next. If a family member hits the same code, the same cooldown rule applies. One clean attempt beats ten rushed attempts every time.

When you hit xbox error 0x80860010 again after a clean stretch, treat it like a signal. Stop retrying, restart once, then do the lighter cache steps before you jump to resets. Most repeat cases resolve with a short wait and a clean sign-in path.