Fix "You Need to Fix Your Microsoft Account" Alerts

If Windows just told you that you need to fix your Microsoft account for apps on your other devices to keep working, the short version is: open Settings > Accounts > Your info, click the account that shows the warning, choose Fix now (or Manage), and sign in again with whatever password or passkey currently unlocks that Microsoft account. Here's the part almost nobody expects: this warning almost never means your account is broken. In the overwhelming majority of cases it means you changed something about the account somewhere else — a password, a two-step verification method, a security key — and this one PC just hasn't been told yet.

Jake had a customer standing at the counter with a laptop that wouldn't sync photos to OneDrive, and a little red exclamation mark sitting on the Start menu telling him to "fix" a Microsoft account he swore he never touched. He called it in a panic — had the laptop been hacked overnight, sitting in his back room? Was someone trying to get into this guy's account right now?

It hadn't been hacked. The customer had reset his Microsoft account password from his phone two weeks earlier, after a routine "let's tighten up your security" prompt, and never signed back in on the laptop. Windows had been quietly nagging him about it the whole time. That gap between "something changed" and "this device hasn't caught up" is the entire story behind this notification, and once you see it that way, the fix stops feeling scary.

Why does this warning show up in the first place?

Every Microsoft account is really two things at once: the identity itself (your email address and however you prove it's you), and a separate little "token" that each of your devices holds locally so it doesn't have to ask you to sign in every five minutes. When the identity changes and the token on one device doesn't, that device starts throwing this warning until you close the gap. It's not an accusation that anything is wrong with the account — it's the device admitting it's out of date.

The specific triggers we see most often:

You changed your password somewhere else

Phone, tablet, another PC, even a password reset done straight from Microsoft's account recovery page — any of these will leave this device holding a stale credential. This is the single most common cause, by a wide margin.

Your two-step verification method changed

Swapped phone numbers, set up a new authenticator app, added or removed a security key — Microsoft treats this as a security-relevant change and wants every device to re-confirm it's still really you.

The account moved toward passkeys

Microsoft accounts are passwordless-first now — new accounts can be created with no password at all, and existing accounts are steadily nudged toward passkeys, Windows Hello, or the Microsoft Authenticator app instead of typed passwords. If you accepted that switch on your phone, this PC may still be expecting the old password box and getting confused when it doesn't work.

The device sat unused too long

Security tokens expire on their own after enough idle time. A laptop that's been in a drawer for a couple of months can throw this warning purely from time passing, with nothing having changed on your end at all.

A family safety or approval setting changed

On child or family-managed accounts, a parent changing screen-time rules, content filters, or spending limits from a different device can also surface this same generic warning on the child's PC.

More than one person signs into this PC

If this PC has several Windows user profiles — a family computer, a shop demo unit, a shared desktop in a back office — the warning is tied to whichever Microsoft account signed a security change, not to the PC as a whole. It's completely normal for one profile to show the warning while a sibling or coworker's profile on the same machine looks perfectly fine. Sign into the affected profile and fix that one account; you don't need to touch anyone else's.

Your PC's clock or time zone is wrong

This one catches people off guard because it has nothing to do with the account at all. Windows Hello, passkeys, and Microsoft's sign-in service all rely on time-sensitive security certificates. If your system clock has drifted — a dying CMOS battery on an older desktop, a virtual machine that never synced, a laptop whose clock reset after sitting powered off for a long stretch — sign-in attempts can fail with this exact same wording, even though nothing about the account itself has changed. Before you touch a single password, check Settings > Time & language > Date & time and confirm "Set time automatically" is switched on.

Fixing it in Windows 11

In Windows 11, the fastest route skips the notification entirely and goes straight to the account itself.

Step 1 — Open your account settings

Press Win + I to open Settings (Win is the key with the Windows logo, usually near the bottom-left of your keyboard, and it's the fastest way into Settings from anywhere). Go to Accounts > Your info. If you'd rather click the notification itself, that works too — it drops you in the same place.

Step 2 — Find the account with the warning

The account showing the problem will have a small warning icon and a Fix now or Manage button next to it. Click it. Windows will explain, in a sentence or two, what it thinks changed — usually something like needing you to verify your identity again.

Step 3 — Sign in with whatever currently works

This is where people get stuck: Windows 11 will show you whatever sign-in method the account currently expects, which is not always a plain password box anymore. Since Microsoft accounts are passwordless-first, you might instead be asked to approve a prompt on your phone through the Microsoft Authenticator app, use a passkey, or enter a Windows Hello PIN. If a password field does appear, type your current password — not the one you remember from six months ago.

If it's a work or school account instead

Windows 11 also shows this same style of warning for accounts added under Accounts > Access work or school, not just personal Microsoft accounts. If that's the account flagged, the fix button there reconnects to your organization's identity system instead of a personal Microsoft account, and you'll usually need your work password or an authenticator app your IT department set up. If you're not sure which one is broken, check both sections — Your info for personal accounts, Access work or school for anything tied to an employer or school.

The Windows 11 fix, in one glance:

1. Open Settings > Accounts > Your info (or Access work or school for an organization account).
2. Click the account showing the warning and choose the sign-in / verify prompt.
3. Sign in with whatever currently works — password, authenticator approval, or code — and let the wizard finish.
4. Give it a minute, then check the warning has cleared under Your info.

Fixing it in Windows 10

The underlying steps are the same on both versions of Windows — sign back into the flagged account — but the menus you'll click through look different on Windows 10.

Step 1 — Open Email & app accounts

Go to Settings > Accounts > Email & app accounts, or Accounts > Your info if that's the section showing the warning. Both live under the same Accounts hub in Windows 10's Settings app.

Step 2 — Click Fix, then sign in

Same as Windows 11: click the flagged account, click Fix, and complete whichever sign-in step Windows presents — password, PIN, or an approval prompt on another device.

If the Microsoft Store shows a separate sign-in problem

Older guidance for this warning — including our own original coverage of it — pointed people toward the Store app and checking that it was signed in with the right Microsoft account. That's still worth a quick look if apps specifically aren't updating: open the Store, check the account icon in the top-right corner, and make sure it matches the account you just fixed in Settings. But it's no longer the main fix path; the Settings > Accounts route above resolves the notification itself in nearly every case.

Windows 10, in one glance:

1. Open Settings > Accounts > Email & app accounts.
2. Click the account marked with the warning, choose Fix, and sign in.
3. If the Microsoft Store still complains, sign out and back in there separately as described above.

What if "Fix now" doesn't actually fix anything?

Sometimes the straightforward fix doesn't stick. Before you assume it's broken, try it once more from a fresh Settings window rather than the notification shortcut — occasionally the notification itself is holding onto a stale version of the account state even after the underlying problem is already gone. If it still won't clear, here's what each variation usually means.

It keeps rejecting a password you're sure is correct

You may be typing the password that's correct on one device but not the current one. Go to a browser, sign in at account.microsoft.com directly, and confirm that exact password works there first. If it doesn't, that's your real answer — the password changed and you need the new one, not a Windows bug.

You sign in successfully and the warning comes right back

This usually points to a two-step verification method Windows can't complete unattended — for example, an authenticator app on a phone you don't have with you, or a security key sitting in a drawer. Go to account.microsoft.com > Security, and check which verification methods are currently listed as active. Removing an old, unreachable method (once you've confirmed a working one exists) often stops the loop.

You genuinely don't know the current password anymore

Use the "I forgot my password" link on the Microsoft sign-in screen rather than guessing repeatedly — repeated wrong guesses can trigger a temporary account lockout. If you don't know the password and can't get to the recovery email or phone tied to the account either, that's a harder problem this fix can't solve for you: you're not getting back in without going through Microsoft's account recovery process, which can take a few days for accounts with limited recovery info on file.

It's a child or family-managed account

On a family account, the "fix" sometimes needs to happen from the parent's device, not the child's. If a parent recently approved or changed a family safety setting, have them check their own account's notifications first — the underlying change may need to be confirmed there before the child's PC will clear itself.

Is this a real Windows message, or could it be a scam?

Fair question, and worth taking seriously given how many fake "your account has a problem" popups exist. The notification we're describing here — the one built into the Action Center and Settings > Accounts — is legitimate. Here's how to tell the difference from something fake:

It's also worth saying plainly: a lot of well-meaning advice online tells people to "just reset your PC" or "reinstall Windows" the moment this warning appears. That's overkill for what is, in the vast majority of cases, a five-minute sign-in issue. Save the drastic options for problems that are actually drastic.

Different account situations, briefly

The core fix — sign back in through Settings — stays the same everywhere. The table below is just a quick way to check you're looking in the right corner of Settings for your specific situation before you start clicking around.

One thing worth flagging if you manage several devices for family or for a small shop like Jake's: it's common for the Xbox app, Office, and Windows itself to each be signed into a slightly different Microsoft account on the same PC, especially on a machine that's changed hands. If fixing the account in Settings doesn't clear a warning inside a specific app, check that app's own sign-in status separately — it may be a different account than the one Windows just fixed.

On a work-managed PC, a VM, or over Remote Desktop

The steps above cover the ordinary case — one person, one physical PC. A few setups need a small adjustment.

Company-managed devices

If this PC is enrolled in an organization's device management (Intune or similar), the fix button may fail repeatedly even when you're typing the right password. That's often not a Windows problem at all — it's a compliance policy on the organization's side, such as a newly required multi-factor registration or a device check that hasn't reported in yet. Contact IT before spending more time troubleshooting locally; they can usually see exactly what the device is being asked to satisfy.

Virtual machines and Remote Desktop sessions

Windows Hello and passkey prompts generally need a fingerprint reader, camera, or security key that a VM or an RDP session often can't pass through. If the account keeps offering a sign-in method you have no way to complete inside that session, look for a "use a password instead" or "more sign-in options" link on the prompt, or go fix the account from the physical machine instead of over Remote Desktop.

Tablets and 2-in-1 devices

Same Settings path, just a touch-friendly version of the same menus — nothing about the fix itself changes on a tablet or 2-in-1.

Offline or airplane mode

This fix needs an active internet connection to actually reach Microsoft's sign-in service — it can't complete while a laptop is in airplane mode or genuinely offline. If you're troubleshooting on a flight or somewhere without a signal, the warning will simply reappear once you're back online, which is expected and not a sign the fix failed.

Should you use a third-party "account repair" tool?

A search for this exact warning turns up plenty of third-party "Windows repair" utilities that promise to fix account sign-in problems for you. Skip them. This particular warning has no moving parts that a general-purpose repair tool can reach — it isn't corrupted system files or a broken registry key, it's simply a credential on this device that's out of sync with the account in the cloud. The only thing that actually resolves it is signing back in through Settings, which means every one of those tools is, at best, doing nothing useful, and at worst asking for permissions and account details it has no reason to need. If you want a built-in second opinion instead, Windows' own "Get Help" app can walk through basic account diagnostics without asking you to install anything from outside Microsoft.

The same caution applies to browser extensions and toolbars that promise to "monitor" or "protect" your Microsoft account sign-in. None of them can see or influence the token exchange happening between Windows and Microsoft's servers — that conversation happens below the level any browser add-on can reach, so an extension claiming to fix this is making a promise it structurally can't keep.

What actually stops working if you ignore it

Plenty of people click the notification away and keep using their PC for weeks with nothing dramatic happening — which is exactly why it's easy to ignore. But the account being "unfixed" quietly breaks a handful of things:

• OneDrive sync stalls — new files stop uploading, and files you add on other devices stop arriving on this one.
• Store apps stop updating automatically, even though they still open and run.
• Settings and browser sync — passwords, favorites, some app settings — drift out of date across your devices.
• "Continue on PC" features that hand off a webpage or document from your phone stop working.
• Xbox multiplayer and cloud saves can fail with a generic connection error that has nothing to do with your internet.

Ethan puts it this way when Jake asks why any of this matters if the PC "still works fine": "It works fine right up until the day you actually need one of those synced files and it isn't there. This is the kind of maintenance that's invisible until it isn't." For a shop that leans on cloud backup and password managers as part of what it sells customers, that's not an abstract point — a customer who loses photos because sync silently stopped is a customer Jake has to have an uncomfortable conversation with.

Keeping it from coming back

A few habits make this warning rare instead of routine:

Set up a passkey or Windows Hello PIN

Since these don't rely on a password you have to remember and manually retype after every change, they tend to stay in sync across devices with far less friction than an old-style password.

Keep recovery info current

A working recovery email and phone number on the account, checked once in a while, is what makes every other step in this article fast instead of painful.

Sign in on each device after a security change

If you change your password or verification method on your phone, take thirty seconds to open Settings on your PC afterward and confirm it's still happy. Waiting for the warning to appear on its own just means dealing with it later, cold.

Use a password manager for the account itself

The single biggest cause of "which password is current" confusion is not having one reliable source of truth for it. A password manager removes that guessing game entirely.

Frequently asked questions

Does this warning mean my account was hacked?

Almost never on its own. It means this device's saved credentials are out of date compared to the account, which is far more often caused by you (or a family member) changing something than by an intruder.

Why does it say "apps on your other devices" specifically?

That phrasing is Microsoft's generic wording for "this account's sign-in state needs refreshing so everything that depends on it — across every device signed into it — keeps working." It's not saying another specific device is broken.

I don't see a "Fix now" button anywhere. Where did it go?

Check both Accounts > Your info and Accounts > Access work or school — the button only shows up under whichever section holds the flagged account. If it's genuinely gone, the account may have already resolved itself after a background sync.

Can I just ignore it forever?

You can, and Windows will keep running. You'll just lose the background conveniences — sync, automatic Store updates, some cross-device handoff features — a little at a time, without necessarily noticing right away.

Will fixing it delete any of my files?

No. Signing back in doesn't touch local files. The one thing to be careful about is resetting the account's password itself if you're on Device Encryption — save your recovery key first, just in case.

I fixed it once and it came back a week later. Is that normal?

It can happen if you're regularly changing security settings on other devices, or if a verification method on file (like an old phone number) keeps failing silently. Check account.microsoft.com > Security and remove anything outdated.

Does this affect a local account too, or only Microsoft accounts?

Only accounts signed into Microsoft's identity system — personal Microsoft accounts and work/school accounts. A purely local account with no Microsoft sign-in doesn't get this notification, because there's no cloud identity for it to fall out of sync with.

I use a local account on purpose. Can I still get this warning?

Not from the local account itself, but if you've also signed into the Store, Xbox app, or Office with a Microsoft account on top of your local Windows account, that Microsoft account can still throw this warning independently.

What if I'm locked out and don't have the recovery phone anymore?

Use Microsoft's account recovery form and fill in as much history as you can — old passwords you remember, when you created the account, recent activity. It's slower without current recovery info, sometimes taking several days, but it's the only route in.

Does this warning ever show up right after a Windows update?

It can, indirectly — not because the update itself broke anything, but because a device that's been offline downloading and installing updates for a while is also a device that's been offline long enough for its account token to go stale.

My kid's PC shows this and I haven't changed anything on my end. What now?

Check your own Microsoft Family Safety notifications first — sometimes an automatic policy update (like a new screen-time period rolling over) triggers this on the child's device even without you actively changing a setting.

Is there a way to check if my password is current without risking a lockout?

Yes — sign in at account.microsoft.com in a browser first. A browser sign-in won't lock you out the way repeated failed attempts inside Windows eventually will, and it confirms which password actually works before you try it on the PC.

Should I remove and re-add the account instead of fixing it?

Only as a last resort. Removing a Microsoft account from a PC can affect app licenses, OneDrive file placeholders, and saved settings tied to that account on that device. Try every fix step above first.

Is there a PowerShell command or script that fixes this faster?

Not a reliable one. Account re-authentication for Microsoft accounts goes through Windows' sign-in service and isn't something a command-line script can safely complete on your behalf — it needs your actual interactive sign-in. The Settings app is the fastest legitimate route, script or no script.

Can a VPN or work proxy cause this warning?

Indirectly, yes. If a VPN or corporate proxy blocks or heavily filters traffic to Microsoft's sign-in servers, the periodic background check that keeps your account token fresh can fail silently, and the warning appears even though nothing about your account changed. Try the fix with the VPN briefly disconnected to see whether that's what's happening.

Does restarting the PC clear the warning on its own?

Sometimes, if the underlying cause was a token that just needed a fresh background refresh — but a restart isn't a reliable fix on its own. If the warning is still there after a restart, go through the sign-in steps above rather than restarting again and hoping.

I have two Microsoft accounts on one PC and only one shows the warning. Is that normal?

Yes. Each Microsoft account signed into a device holds its own separate token, so it's completely normal for one account to need re-authentication while another, added later or changed more recently, stays fine.

Revision note. Originally published December 16, 2016. Rewritten August 27, 2026 for Windows 11 and Windows 10. Back then, the fix involved a standalone downloadable diagnostic tool; Microsoft has since folded that kind of automated repair directly into Settings, and Microsoft accounts themselves have moved toward passkeys and passwordless sign-in instead of relying on a typed password alone. If that little red warning brought you here at 11pm worried something was wrong with your account, take a breath — it almost never is, and you're two minutes from clearing it.