Skip to content
TroubleGrid

Microsoft games fail to sign in to Xbox Live with error 0x87DD0005

Last verified October 2026Tested against Windows 11, all serviced versions, Windows 10 version 22H2, Microsoft Store and Xbox app games (Solitaire, Mahjong, Jigsaw, Gears of War 4, Rise of Nations: Extended Edition), Reported incident window: 13-16 October 2026Good evidence

If a Microsoft Store or Xbox app game fails with 0x87DD0005 while the Xbox app and xbox.com sign in normally with the same account, the failure is in Xbox Live's authentication path, not on your PC. That is what a wave of users hit from the evening of 13 October 2026. Removing the October updates, restoring a pre-update system image and reinstalling games all failed to fix it, and it cleared region by region on 15-16 October with no user action. Check the cheap signals first and give it a day before you change anything.

Start here

  1. Check whether the problem is on your PC at all

Error 0x87DD0005 reads like a problem with your machine, and because it landed the same day as the October 2026 Patch Tuesday updates it was widely blamed on them. The reports do not support that. Microsoft never listed it as a known issue on KB5127648 or on the Windows release health dashboard, the Xbox status page stayed green throughout, and the people who did the most drastic things to their PCs were not the ones who got fixed. This page is about telling a service-side sign-in failure apart from a real problem on your PC, so you do not spend an evening reinstalling a 170 GB game for nothing.

Symptoms

  • "We couldn't sign you into Xbox Live" with error code 0x87DD0005 when a Microsoft Store or Xbox app game starts
  • The game offers to continue as a guest, and your progress and cloud saves are not visible
  • The Xbox app and xbox.com both sign in normally with the same account
  • The Microsoft Store works, but every Xbox-backed game fails the same way
  • The Xbox status page reports no problem
  • A Windows update installed shortly before it started

Why this happens

An Xbox Live authentication failure on Microsoft's side

The pattern in the reports is a service-side failure, not a local one. Around nineteen people described the same error in a single Microsoft Q&A thread within hours of each other, starting the evening of 13 October 2026, across Solitaire, Mahjong, Gears of War 4 and Rise of Nations. The Xbox app, the Microsoft Store and xbox.com kept signing the same accounts in while only the games were refused. Nothing done locally reliably changed the outcome, and recovery arrived without anyone doing anything: users in New Zealand, the UK and Germany reported sign-in working again on 15 October, and a user whose every repair step had failed found it working on 16 October after simply retrying.

Check whether the problem is on your PC at all · Give it a day before you change anything

Why the October updates looked guilty, and why the evidence does not support it

KB5127648 and, as users in the thread named it, the .NET Framework update KB5127694 installed on 13 October, hours before the error appeared, so for most people the update was the only thing that visibly changed. But two users went further than uninstalling: one removed the last two updates, and one restored a system image from 7 October and blocked updates entirely. Both still got the error. In the other direction, one user's un-updated laptop was never affected and kept working after the pending updates were installed. A cause that is absent when the symptom is present, and present when the symptom is absent, is not the cause. Microsoft's own known-issues list for KB5127648 covers Smart App Control, Remote Desktop error 0xC000000D and USB Audio Class 1.0 devices, and says nothing about sign-in.

Fixes

Check whether the problem is on your PC at all

about 5 min

Three checks, two minutes, and they decide whether anything you do locally can possibly help.

Applies to: Windows 10 and Windows 11, Microsoft Store and Xbox app games

  1. Sign in to xbox.com in a browser with the same account. If that works, your account and password are fine.
  2. Open the Xbox app and check whether it shows you signed in. During this incident it did, for everyone who reported it.
  3. Launch a different Microsoft Store or Xbox game. If every one of them fails with 0x87DD0005 and not just the game you care about, the problem is in the sign-in path those games share, not in any one game.
  4. If you have a second PC, or someone else in the house has an account, try there. Reports split both ways during this incident - one household had a working account on the same network, another had one PC affected and two not - so a second device is a useful signal but not proof on its own.
  5. Do not treat the Xbox status page as the answer. It reported no problem throughout, while people across several countries were unable to sign in.

Reported to work by 5 users; not confirmed by the vendor.

Source: Microsoft Q&A, Microsoft Q&A

Give it a day before you change anything

about 1 min

During this incident, waiting is what actually worked, and the people who did the most to their machines got nothing for it.

Applies to: A sign-in failure that matches the service-side pattern above

  1. If the checks above point at the service rather than your PC, stop and leave the machine alone. Do not uninstall Windows updates, reinstall games, or reset Gaming Services yet.
  2. Re-try sign-in every few hours. Recovery in October 2026 arrived at different times in different regions, between about one and three days after the failures began, with no action from the user.
  3. Do not play in guest mode while you wait. One user who was signed back in found their progress reset to Level 1, and reported three days later that their cloud save still had not come back. Starting a guest session risks writing an empty save over a good one.
  4. If it is still failing after about two days, treat it as a problem on your machine and treat it as local and see "When something else is wrong" below.

Reported to work by 5 users; not confirmed by the vendor.

Source: Microsoft Q&A, Microsoft Q&A

Restart the Microsoft Account Sign-in Assistant service

about 5 min

Three users reported this restored sign-in, and a Microsoft Q&A moderator later suggested it - but it is unclear whether it did anything, because the service-side recovery was reaching people the same day.

Applies to: Windows 10 and Windows 11

  1. Press Windows+R, type services.msc and press Enter.
    services.msc
  2. Find Microsoft Account Sign-in Assistant in the list. Write down its current Startup type before you change it, so you can put it back.
  3. Double-click it, set Startup type to Automatic, and click Apply.
  4. Click Start, or Stop and then Start if it is already running. Close the dialog.
  5. Open the Xbox app, confirm it shows you signed in, then launch the game.
  6. If it makes no difference, set the Startup type back to what you noted in step 2.

Reported to work by 3 users; not confirmed by the vendor.

Source: Microsoft Q&A, Microsoft Q&A

Known issues

  • Microsoft has published no known issue for the 13-16 October 2026 Xbox Live sign-in failures. The known-issues list for KB5127648 covers Smart App Control, Remote Desktop error 0xC000000D and USB Audio Class 1.0 devices only, and the Windows release health dashboard does not mention sign-in at all.

    Affects KB5127648 (13 October 2026) · Status: unknown

  • Cloud saves did not necessarily come back with sign-in. One user signed in again on 15 October 2026 to find their progress reset, and reported on 18 October that the cloud save still had not been restored.

    Affects Microsoft Store and Xbox app games · Status: open

If none of this worked

This page describes a specific pattern: every Xbox-backed game refused at once, while the Xbox app and the browser signed in fine, during 13-16 October 2026. If you are seeing 0x87DD0005 outside that window, or only one game fails while others sign in normally, the diagnosis here probably does not apply and the problem is more likely local to that game or your profile - one user hit the code in ARK: Survival Evolved alone while their other Xbox games kept working. For a genuinely local failure, the steps a Microsoft Q&A moderator recommends are wsreset.exe, then Repair and Reset on Gaming Services under Settings > Apps > Installed apps, then signing out of and back in to the Microsoft Store and the Xbox app, then a restart. Be aware that during the October 2026 incident those steps were tried and reported as not helping, which is the clearest sign they were addressing the wrong machine.

Common questions

Did KB5127648 or KB5127694 cause this?
The evidence says no. One user removed both updates and still got the error; another restored a 7 October system image and blocked updates and still got the error; a third's un-updated laptop was never affected and stayed working after the updates were installed. Microsoft lists no such known issue for KB5127648, and the Windows release health dashboard does not mention sign-in at all. The updates installed hours before the failures started, which made them the obvious suspect, but timing is not causation.
Should I uninstall the October 2026 update?
No. It did not work for the users who tried it during this incident, the updates reinstalled themselves for one of them, and you would be removing October's security fixes for nothing. KB5127648 also fixes mouse input stutter in games and AC-3 audio playback, so you would be giving up real fixes as well.
Why does the Xbox app sign in when the game will not?
They do not clear the same sign-in step. In every report here the Xbox app and the Microsoft Store showed the account signed in while each game was refused, which is why "the Xbox app works" is a diagnostic signal rather than a reason to rule out a service problem. What differs between the two paths is not documented by Microsoft, so treat any explanation of the internals - including the widely repeated claim that Gaming Services is at fault - as unverified.
The Xbox status page says there is no problem. Doesn't that rule out an outage?
No. The status page reported everything healthy for the whole of this incident while users across several countries could not sign in to any game. Treat a green status page as weak evidence at best.
My progress is gone. Should I keep playing?
Not in guest mode. Playing while signed out can write a fresh local save that later syncs over a good cloud save. Wait until the game shows you signed in with your own profile. Note that one user's cloud save had still not been restored three days after sign-in came back, so if progress is missing after you are signed in, contact Xbox support rather than playing on.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • October 13, 2026-KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100.9711)Official

    Microsoft · Support page · checked Oct 19, 2026

    • KB5127648 was released on 13 October 2026 for Windows 11 versions 26H2, 25H2 and 24H2
    • The known issues Microsoft lists for KB5127648 are Smart App Control being unable to be turned back on, Remote Desktop failing for non-admin users with error 0xC000000D, and USB Audio Class 1.0 devices failing to start; Xbox Live and Microsoft Store sign-in are not among them
    • KB5127648 fixes mouse input stutter in some games and AC-3 audio playback in some applications
  • Windows 11, version 24H2 known issues and notificationsOfficial

    Microsoft · Documentation · checked Oct 19, 2026

    • As of the page's 17 October 2026 revision, the Windows release health dashboard lists no known issue about Xbox Live, Microsoft Store or game sign-in failures for the October 2026 updates
  • XBOX won't sign me in after a Windows Update 0x87DD0005Community report

    Microsoft Q&A · Forum · checked Oct 19, 2026

    • Reports of error 0x87DD0005 in Microsoft Store and Xbox app games began on the evening of 13 October 2026 and ran through 15-16 October 2026
    • Around nineteen distinct people reported the same error in this one thread, across Microsoft Solitaire & Casual Games, Microsoft Mahjong, Gears of War 4 and Rise of Nations: Extended Edition
    • Several users reported that the Xbox app, the Microsoft Store and xbox.com all signed in normally with the same account while every game failed
    • One user removed the last two updates and the error persisted; another restored a 7 October system image and blocked updates, and the error still persisted
    • One user's un-updated laptop was unaffected, and it kept working after the pending updates were installed
    • Sign-in started working again without any user action for users in New Zealand, the UK and Germany on 15 October 2026
    • Reinstalling games (including a 170 GB reinstall), clearing Credential Manager, clearing the TokenBroker cache, time sync and resetting the Xbox app and Store were all reported as not helping
    • Three users reported that setting the Microsoft Account Sign-in Assistant service to Automatic and restarting it restored sign-in on 15 October 2026
    • The Xbox status page showed no problem while users were affected
    • One user who was signed back in found their progress reset to Level 1, and reported on 18 October 2026 that their cloud save still had not been restored
  • Can't Log into Microsoft Xbox GamesCommunity report

    Microsoft Q&A · Forum · checked Oct 19, 2026

    • A user reported error 0x87DD0005 in Microsoft Jigsaw and Microsoft Solitaire on 14 October 2026 while the Xbox app showed a signed-in state
    • A Microsoft Q&A moderator recommended wsreset.exe, repairing and then resetting Gaming Services, and signing out and back in to the Microsoft Store and Xbox app; the user reported on 15 October 2026 that none of it worked
    • The same user reported on 16 October 2026 that sign-in worked again after a retry, with no specific change identified
    • The user reported that the Xbox web status page showed no issue
  • How to fix 0x87DD0005 error on Ark Survival EvolvedCommunity report

    Microsoft Q&A · Forum · checked Oct 19, 2026

    • A user reported error 0x87DD0005 launching ARK: Survival Evolved on 14 October 2026 while other Xbox games still worked
    • A Microsoft Q&A moderator suggested on 18 October 2026 setting the Microsoft Account Sign-in Assistant service to Automatic and starting or restarting it, then opening the Xbox app before launching the game
    • Resetting the Microsoft Store cache, time sync, resetting the Xbox app, the Gaming Services repair tool, reinstalling Gaming Services and reinstalling the game were all reported as not helping