Microsoft Store/Xbox sign-in fails with 0x800704cf despite working internet

Roko Perković 25 Reputation points
2026-08-06T10:09:44.4+00:00

I am unable to sign in to my personal Microsoft account in Microsoft Store, Xbox app, Minecraft Launcher, or other Windows components that use Microsoft account authentication.

The main error is: 0x800704cf – “You’ll need the Internet for this.”

My internet connection works normally. I can browse the web and sign in to the same Microsoft account successfully through a web browser. Microsoft Office apps such as Word and PowerPoint can also access the account.

The issue appears to be related specifically to Windows Microsoft account authentication/WAM.

Troubleshooting already performed:

  • Reset/repaired Microsoft Store and Xbox app
  • Ran WSReset
  • Checked Microsoft Account Sign-in Assistant service
  • Checked Microsoft Cloud Identity Service
  • Confirmed Microsoft.AAD.BrokerPlugin and Microsoft.Windows.CloudExperienceHost are installed and report Status: OK
  • Re-registered both WAM packages using Add-AppxPackage
  • Restarted Windows after re-registering them
  • Tested AAD.BrokerPlugin directly: the Work or School Account window opens but keeps loading
  • Tested Microsoft.Windows.CloudExperienceHost directly: the Microsoft Account window briefly opens and immediately closes
  • Re-registering CloudExperienceHost did not change this behavior
  • Tested network-related fixes, but the issue remains

At one point the sign-in dialog also returned 0x80860010 (“This application made too many requests”), but it normally returns 0x800704cf.

This problem existed before I installed my current third-party antivirus/security software.

Could this be a corrupted WAM/CloudExperienceHost, TokenBroker, IdentityCache, or Windows user-profile authentication issue? I would appreciate guidance on diagnosing or repairing the underlying Microsoft account authentication components rather than general network troubleshooting.

Windows for home | Windows 11 | Accounts, profiles, and login
0 comments
Answer accepted by question author
Thomas4-N 21,440 Reputation points Microsoft External Staff Moderator
2026-08-06T15:48:33.49+00:00

Hello Roko Perković,

You have already done a thorough job checking the Store, Xbox app, services, WAM packages, and network components, so I would not repeat those steps.

Because web sign-in works but Windows-based Microsoft account dialogs fail, the next useful test is whether the issue follows your Windows profile.

Create a temporary local account under Settings > Accounts > Other users > Add account, select I don’t have this person’s sign-in information, and then choose Add a user without a Microsoft account. Sign in to that profile and test Microsoft Store sign-in there.

  • If it works, the original Windows profile’s authentication state is damaged, and moving to the new profile is the practical fix.
  • If it fails there as well, the issue is system-wide. The next step would be Settings > System > Recovery > Fix problems using Windows Update > Reinstall now, which repairs Windows while keeping your files, settings, and installed apps.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-08-06T10:10:13.13+00:00

    The supported guidance points to a Windows-side sign-in component issue rather than an actual internet outage, because browser sign-in works while Store/Xbox-style app sign-in fails.

    Based on the available guidance, use this order:

    1. Confirm the account works on the web
      • Sign in to the Microsoft account in a browser.
      • If web sign-in works, the problem is not the account itself and is more likely local Windows app/authentication state.
    2. Reset Microsoft Store cache again
      • Press Windows + R.
      • Run wsreset.exe.
      • Wait for the blank command window to close and for Microsoft Store to reopen automatically.
      • Then try Store/Xbox sign-in again.
    3. Perform a full Windows network reset
      • Since Winsock/IP reset was already tried, the remaining supported network step is Settings > Network & Internet > Advanced network settings > Network reset.
      • Restart Windows after the reset.
      • This is broader than netsh winsock reset and netsh int ip reset.
    4. Test on a different network
      • Use a mobile hotspot or another network.
      • This helps rule out proxy, DNS, or boundary filtering issues even when normal browsing works.
    5. Check basic connectivity used by Microsoft sign-in components
      • In a browser, try opening http://www.msn.com.
      • From Command Prompt, run:
        • ipconfig
        • ping
        • nslookup www.msn.com
      • This verifies IP connectivity and DNS resolution.
    6. Check proxy or authentication firewall requirements
      • Verify proxy settings in Internet Options match the network configuration.
      • If the network uses an authenticating proxy/firewall, Microsoft 365 sign-in guidance says exceptions may be needed for Microsoft sign-in endpoints and ports 80/443.
      • This is especially relevant when browser access works but embedded/non-browser sign-in fails.
    7. Try a new local Windows user profile
      • The available guidance supports testing with a new local profile to determine whether the issue is isolated to the current Windows user profile.
      • Open Run with Windows + R, enter Netplwiz, select Add, then choose Sign in without a Microsoft account, create a local account, sign out, and test Microsoft Store sign-in in that new profile.
      • If sign-in works there, the issue is likely tied to the original Windows profile state.
    8. If the issue affects support.microsoft.com sign-in loops or account picker loops, check cookie/security-zone behavior
      • Ensure these sites are not inconsistently placed in Trusted Sites:
        • microsoft.com
        • support.microsoft.com
        • login.live.com
        • login.microsoftonline.com
      • If any must be in Trusted Sites by policy, all of them should be there together.

    What is supported from the available material:

    • Browser sign-in working while app sign-in fails usually indicates a local app/system sign-in problem, not a true internet outage.
    • A network reset, Store cache reset, different network test, and new local profile test are the directly supported next steps.
    • The available material does not provide a documented repair procedure specifically for WAM, CloudExperienceHost, TokenBroker, or IdentityCache beyond those broader Windows-side troubleshooting steps.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.