Outlook Keeps Asking for Your Password? Here's the Two-Minute Fix That Usually Works

There's a particular flavor of frustration that only Outlook delivers: you type your password — the same one you've used for months — and Outlook politely asks for it again. And again. By the third repeat you're checking the caps lock key. By the sixth, you're wondering if you've actually forgotten your own password. You haven't. The password is fine. The problem lives somewhere else, and it's almost always the same somewhere.

I've fixed this loop on dozens of machines — my own laptop the morning before a client meeting, a friend's brand-new work computer that hadn't survived its first week, an accountant's setup that ran perfectly for years until one random Wednesday in March. The pattern repeats: a stuck token somewhere in Windows quietly refuses to refresh. Outlook keeps trying to renew it silently, keeps failing, falls back to the password prompt — and the password prompt itself can't fix the broken token. So you type forever.

Why your password isn't the actual problem

Here's what modern Outlook doesn't tell you. The first time you signed in, your password wasn't what kept you logged in. Outlook traded it for an authentication token, stored that token securely on your machine, and from then on used the token for silent background renewals. You probably haven't typed your real password to Outlook in months.

That arrangement works beautifully — right up until the stored token breaks. After that, every silent renewal attempt fails. Outlook does the one thing it knows how to do in that situation: it falls back to the manual password prompt. You type the password. Outlook tries to use it to get a fresh token. Whatever broke the original stored token is still broken. The loop continues. You age.

So when you're staring at that prompt for the eighth time, remember: you are not solving a "wrong password" problem. You are solving a "broken token" problem. Different problem, different fix.

Five things tend to cause it. In rough order of how often I see them in the wild:

• A stale entry in Windows Credential Manager. Easily the most common — somewhere around 70% of cases.
• An expired modern authentication session Outlook can't refresh silently.
• A misbehaving Outlook add-in stepping into the auth flow.
• An MFA prompt Outlook isn't being given a chance to surface.
• A Conditional Access policy at work silently blocking the device.

Work down the list. The moment the prompt stops appearing, you can stop reading. You don't need every fix here — you need the right one.

Fix 1: Wipe stored Outlook credentials

This is the fix that solves it for the majority of people. You're going to delete the stuck credential so Outlook has to ask properly, once, and store a fresh working token.

1. Close Outlook completely. Not just minimize it. Quit.
2. Open Task Manager (Ctrl + Shift + Esc). Under Background processes, look for any leftover OUTLOOK.EXE and end them. There's almost always at least one.
3. Open Control Panel → User Accounts → Credential Manager. If you don't see "User Accounts," switch the Control Panel view in the top-right to Small icons.
4. Click Windows Credentials.
5. Scroll the list. Delete anything starting with MicrosoftOffice16_Data:, MS.Outlook, MicrosoftOfficeIdentity, or your email address. All stale at this point.
6. Reopen Outlook. When it prompts for the password, type it and check Remember me if offered.

Quick heads-up: some Office builds put Outlook credentials under Generic Credentials instead of Windows Credentials. If the Windows Credentials list looks suspiciously short, scroll up and check Generic. Same labels, same cleanup, same result.

Fix 2: Reset Office's shared identity

If wiping credentials didn't take, the next layer up is Office's own identity store — the bit that keeps you signed into Word, Excel, Outlook, and OneDrive all at once with a single sign-on. Sometimes credentials clean out fine but the upper-level identity is still broken.

1. Open Word. Any Office app works; Word loads fastest.
2. Click File → Account.
3. Under User Information, click Sign out.
4. Close every Office app.
5. Open Outlook. Sign in fresh. Complete any MFA prompts.

Under the hood, you've cleared %LOCALAPPDATA%\Microsoft\Office\16.0\Licensing and the identity cache below it. Outlook has to do a complete fresh sign-in instead of trying to refresh a token that's already dead.

Fix 3: Disable add-ins to test for interference

Some Outlook add-ins step right into the middle of the auth flow and break it. Old antivirus mail scanners are notorious. PDF toolbars too. Ancient CRM connectors that haven't been updated since the Obama administration. Outlook tries to talk to Microsoft's servers, the add-in intercepts the conversation, and authentication fails in a way that just looks like a password prompt.

Test in about thirty seconds:

1. Press Win + R.
2. Type outlook.exe /safe and press Enter.
3. Pick your profile.

Safe mode loads Outlook with every add-in disabled. If the prompt is gone there, an add-in is your problem and you now need to find which one. Close safe mode, open Outlook normally, go to File → Options → Add-ins, and disable add-ins one at a time, restarting Outlook between each, until the prompt stops. The last add-in you disabled is the culprit.

If the prompt still appears in safe mode, add-ins aren't your problem — move on.

Fix 4: Repair the Outlook data file

A corrupted local OST file can confuse Outlook into thinking authentication failed when it didn't. There's a built-in repair tool that ships with Outlook and it does exactly what you'd want, without losing a single email.

1. Close Outlook.
2. Open File Explorer. Navigate to C:\Program Files\Microsoft Office\root\Office16. On the newest builds the path may end in Office19.
3. Find SCANPST.EXE. Double-click it.
4. Click Browse and point it at your OST or PST. Default location: %LOCALAPPDATA%\Microsoft\Outlook.
5. Click Start. Wait. If errors appear, click Repair.

SCANPST is unglamorous, reliable, and has been around forever. It does what it says.

Fix 5: Build a fresh Outlook profile

When everything above fails, the next step is a fresh Outlook profile. Sounds nuclear. Isn't. You don't lose any email — Outlook just re-syncs everything from the server. The new profile is a clean container for all the settings that have accumulated quirks over the years.

1. Close Outlook.
2. Open Control Panel. Switch view to Small icons.
3. Click Mail (Microsoft Outlook).
4. Click Show Profiles.
5. Click Add. Name it anything ("Fresh" works). Follow the prompts.
6. At the bottom of the Mail dialog, set Always use this profile to your new one.
7. Open Outlook. It signs in, takes a few minutes to rebuild the OST file, and you're back.

If everything's now smooth, come back in a week and delete the old broken profile. It's just clutter at this point.

Fix 6: The MFA and Conditional Access angle (work accounts)

This one's mostly for work or school accounts. If you've worked through everything above and the loop keeps coming back, check whether a Conditional Access policy is silently blocking you. Common triggers:

• Your device fell out of compliant status in Intune — maybe BitLocker got disabled, or the OS is now behind a required version.
• You're connecting from a new location and the policy demands MFA, but Outlook isn't surfacing the prompt cleanly.
• Your password silently expired but the prompt looks identical to a normal one.

The quick test that proves it: try signing in to outlook.office.com in a browser, with the same credentials. If browser sign-in works fine but desktop Outlook loops, the problem is on the device-trust side. That's IT's job. Send them a ticket with the URL of the page that works, a screenshot of the desktop loop, and a note about which network you're on. They'll sort it out faster than you'd expect — usually within an hour.

The one-sentence version

Nine times out of ten, Outlook's password loop is just Credential Manager hanging onto a token that needs to die. Delete it. Sign in fresh. That single step fixes the bulk of cases. Everything else here is for the stubborn 10%.

And next time it happens to a coworker — and it will — you get to be the person who fixes it in two minutes flat. Worth the read.