Xbox Live Sign In Forgotten From One Session to Another

:arrow_forward: GAME INFORMATION

  • BUILD #: 100.12.1529.0
  • PLATFORM: Steam
  • OS: Windows 10

:arrow_forward: ISSUE EXPERIENCED

My sign into Xbox Live is lost after each session, requiring me to sign into Xbox Live each session.

Here is the problem I’m experiencing…

:arrow_forward: FREQUENCY OF ISSUE

:question: How often does the issue occur? CHOSE ONE; DELETE THE REST.

  • 100% of the time / matches I play (ALWAYS)

:arrow_forward: REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

  1. Start the game.
  2. Click sign into Xbox Live.
  3. Complete signing into Xbox Live until your Xbox Live gamertag is shown on the sign in button.
  4. Quit the game to Windows.
  5. Restart the game.
  6. Observe that the game does not automatically log you back into Xbox Live.

:arrow_forward: EXPECTED RESULT

I excepted that the game would remember my Xbox Live sign in from one game session to another.

:arrow_forward: ACTUAL RESULT

When starting a new session after having signed in the previous session, the game shows that I am not signed into Xbox Live.

:arrow_forward: GAME FILES

:question: Include a OneDrive or Google Drive link to a SAVE GAME or REPLAY FILE (.aoe2record) of the match where you encountered the issue.


Hey there @anon63664082,

Thanks for the report! Clarifying the issue, is it that you have to re-enter your sign-in credentials for Xbox Live each time? Or just that you have to press the Sign-In button each time?

1 Like

@Licidy, I am not automatically signed in so I have to press the button to sign in. It does not ask me for my credentials again.


:arrow_forward: GAME INFORMATION

  • **BUILD : 100.12.1529.0
  • PLATFORM: Steam
  • OS: Windows 10

:arrow_forward: ISSUE EXPERIENCED

When launch AOE 3 DE asking re sign in my XBOX LIVE profile

:arrow_forward: IMAGE & ATTACHMENTS



I’m having this issue too. I hope they fix it

The launch of this DE was a mess, the developers clearly didn’t have enough time to polish the game

This issue still persists after update 10807.