Fix Microsoft Account Sign-In Problems in Windows 11

The Problem

Windows refuses to sign in to your Microsoft account — with "We couldn't sign you in", "Something went wrong", or a code such as 0x80190001, 0x8000704ec, or 0x80070426. The account works fine in a browser, which is what makes it maddening.

The sign-in inside Windows is not the same path as the website. It depends on a specific service, a correct system clock, a working network stack, and a set of cached credentials that can go stale. When any one of those is wrong, Windows gives you a generic message that names none of them.

Signed in already but stuck at "PIN is not available"? Different problem, different fix — see fix Windows Hello "PIN is not available".

Symptoms

• "We couldn't sign you in" when adding or reconnecting a Microsoft account.
• Settings → Accounts shows "You need to fix your Microsoft account" with a banner that does nothing when clicked.
• Microsoft Store, OneDrive, or Xbox apps repeatedly ask you to sign in.
• Codes 0x80190001, 0x8000704ec, 0x80070426, or 0x800706d9.
• The same account signs in normally at account.microsoft.com in a browser.

Step 1: Fix the Clock and Time Zone

A system clock more than a few minutes out breaks the secure token exchange, and this is the single most common cause.

1. Settings → Time & language → Date & time.
2. Turn Set time automatically on, then click Sync now under Additional settings.
3. Set the correct Time zone, and turn Set time zone automatically on.
4. If the clock resets every boot, the CMOS battery on the motherboard is flat — replacing it is a few minutes' work and fixes this permanently.
5. Restart and try signing in again.

Step 2: Confirm the Account Itself Is Healthy

1. On a phone or another PC, sign in at account.microsoft.com with the same address.
2. If Microsoft asks you to verify your identity, complete that — an unverified or security-locked account fails silently inside Windows.
3. Check for an alert about unusual activity, and clear it.
4. If you changed the password recently, that is likely the whole problem: Windows is still presenting the old one. Continue to Step 5.
5. Make sure recovery options are current while you are there: set up account recovery options.

Step 3: Check the Network Path

1. Confirm the browser can reach login.live.com from this PC.
2. Disconnect any VPN or proxy and retry — sign-in frequently fails through a VPN: set up a VPN on Windows 11.
3. Turn off metered connection for the current network: Settings → Network & internet → Wi-Fi → your network → Metered connection off.
4. If name resolution is unreliable, switch to a public resolver: how to change DNS servers.
5. Temporarily disable third-party firewall or "web protection" modules and retry: fix Windows Firewall blocking apps.

Step 4: Restart the Sign-In Services

Windows uses a dedicated service for Microsoft account tokens, and it can end up stopped or set to manual.

1. Windows + R → services.msc → Enter.
2. Find Microsoft Account Sign-in Assistant. Set Startup type to Automatic (Trigger Start) and click Start if it is stopped.
3. Do the same for Windows Update and Background Intelligent Transfer Service — both are used by the account flow.
4. Or from Terminal (Admin):

   net start wlidsvc
   

5. Restart the PC and retry.

Step 5: Clear the Cached Credentials

Stale tokens after a password change produce exactly this failure.

1. Open Control Panel → Credential Manager → Windows Credentials.
2. Expand and Remove every entry beginning MicrosoftAccount: or SSO_POP_Device, plus any virtualapp/didlogical entry.
3. Then go to Settings → Accounts → Email & accounts, select the Microsoft account, and choose Remove.
4. Restart, then add the account again with Add a Microsoft account.
5. Have the current password to hand — this is where an out-of-date saved password stops being invisible: use a password manager safely.

Step 6: Handle Two-Factor and App Passwords

1. If the account has two-step verification on, complete the prompt on your phone or authenticator app when it appears — Windows sometimes shows it behind the Settings window.
2. Older apps that cannot show a second-factor prompt need an app password, created at account.microsoft.com/security under Advanced security options.
3. If you have lost access to your second factor, use a recovery code before doing anything else — without one, account recovery takes days.
4. Keep this working: set up two-factor authentication (2FA).

Step 7: Reset the Store and Repair System Files

1. Windows + R → wsreset.exe → Enter. A blank window sits for about 30 seconds, then the Store opens.
2. Settings → Apps → Installed apps → Microsoft Store → Advanced options → Repair, then Reset if repair does not help.
3. In Terminal (Admin):

   sfc /scannow
   

   DISM /Online /Cleanup-Image /RestoreHealth
   

4. Reboot and repeat sfc /scannow. Detail: how to run SFC and DISM.
5. More on Store failures: fix Microsoft Store not working.

Step 8: Switch to Local, Then Relink

Breaking the link and rebuilding it clears state that nothing else reaches.

1. Settings → Accounts → Your info → Sign in with a local account instead.
2. Set a local password, sign out, and sign back in as the local account.
3. Restart, then go to Settings → Accounts → Your info → Sign in with a Microsoft account instead and enter your credentials fresh.
4. If it still fails, test on a brand new local administrator account: Settings → Accounts → Other users → Add account. Success there means your profile is damaged — see fix "signed in with a temporary profile".
5. Before switching to local, note that BitLocker keys and some app licences are tied to the Microsoft account — save your recovery key first: fix the BitLocker recovery key loop.

What Not to Do

• Don't create a second Microsoft account to get past the error. You will split your licences, OneDrive files, and BitLocker keys across two accounts and make recovery harder later.
• Don't remove the account from Settings until you know the current password and, if BitLocker is on, have the recovery key saved elsewhere.
• Don't turn off two-factor authentication to simplify sign-in. Fix the prompt instead: set up two-factor authentication (2FA).
• Don't enter your credentials on a page you reached from an email link. Sign-in problems are a favourite pretext for phishing: spot and avoid phishing emails and scams.

Still Not Working?

If a new local admin account also cannot add the Microsoft account, and the clock, network, services, and credentials are all correct, the problem is on the account rather than the PC — sign in at account.microsoft.com and work through Microsoft's account recovery. If you suspect the account has been compromised, act on that first: recover a hacked email account.

Related: fix "User Profile Service failed the sign-in", reset a forgotten Windows password, and fix error 0x80070005.