0x87DD0005: We couldn’t sign you in to Xbox Live PC

By Brian Aykut. Published: Monday, 29th November, 2021


This article provides a step-by-step approach on how to fix “Error 0x87DD0005: We couldn’t sign you in to Xbox Live” on PC. This error usually indicates one of two things. An issue with Xbox Live’s online services, or an issue with a local dependency related to sign in. Sometimes it’s as simple as a reboot to get give these services a good kick or simply updating the “Xbox Identity Provider”. Below this image is a step by step list to aid in troubleshooting.

Example of error: We Couldn't sign you In to Xbox Live 0x87DD0005 Xbox Game Pass PC

How to resolve the problem

  • Firstly restart your PC. Don’t skip this as it’s worked for me more than once and is a quick resolution.
  • Check Xbox Live service status to ensure there’s not a problem there.
  • If you’re unable to check the service status make sure you’ve got an internet connection.
  • Attempt signing in to an Xbox Service via the web such as https://www.xbox.com/ to verify your account is indeed working and active.
    • If you have trouble with this step it may be worth contacting Xbox support (via https://support.xbox.com/ – digging down on the most relevant support issue will present you with a contact us link. I’ve not provided a direct link as it may vary with region as support.xbox.com redirects to locale specific pages).
  • After the following steps please close and then restart the Xbox app before attempting to launch the game again.
    • Open Microsoft Store and check for updates, install any relating to Xbox or Microsoft Store (in one instance only “Xbox Identity provider” needed an update for me to resolve it)
    • Search for the game you’re having trouble with via the Windows search bar/start menu and right click it > App Settings then click repair

Final Words

I’ll continue adding to this list as I find additional solutions, thus far I’ve personally run into this issue no less than 4 times, twice updating dependencies resolved it, twice a reboot resolved it. I’ve included the account and service status checks as given the nature of the error it’s reasonable to presume that those may also be potential causes. Hopefully, this has been helpful! If it wasn’t and you find a solution please let us know how you solved this error! If this was helpful please by all means come back at some point and have a read of our articles.