You’re in a Zoom call with the finance team. Your screen share shows an email you just sent — but the recipient says they never got it. You refresh your Sent Items folder. Nothing. You try sending again. The 'Sending...' animation hangs for 47 seconds. Then — silence. No error. No bounce. Just… gone. You glance at the clock: 4:58 PM. Your quarterly report goes out at 5:00. This is when most people assume ‘Outlook has issues today.’ And sometimes — yes, it does. But more often? It’s something quieter, fixable, and already sitting in your cache.
Most Common Cause
It’s not Microsoft’s servers. It’s your local Outlook profile stuck in offline mode — even though you swear you’re online. This happens silently, without warning banners, and affects every version of desktop Outlook (365, 2019, 2016). You’ll see the status bar say 'Connected' — but look closer: it actually reads 'Connected to Exchange (Offline Mode)'. That tiny phrase changes everything. I’ve seen this trip up even experienced users who’d been using Outlook since Exchange 2007.
The quick fix? Press Ctrl+Shift+O. That toggles offline/online mode instantly. If Outlook was faking connectivity, this forces a full reconnection. Try it now — before you restart, before you clear cache, before you ping IT.
Diagnostic Steps
Don’t guess. Diagnose. Open Outlook and do these four things — in order:
Check the bottom-right status bar. Is it showing 'Working Offline', 'Connecting...', or 'Connected to Exchange'? Hover over it. A tooltip will appear with exact connection details.
Go to File > Account Settings > Account Settings..., select your account, click Change, then click More Settings > Connection. Is 'Connect to Microsoft Exchange using HTTP' checked? If you're on a corporate network, this should be unchecked — internal connections use MAPI, not RPC-over-HTTP.
Open Windows Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and check 'Network'. Is usage spiking at 100% when you send mail? That points to antivirus or firewall interference — not Outlook itself.
Open Outlook Web App (outlook.office.com) in an Incognito window. Can you send/receive there? If yes, the issue is local to your desktop client — not Microsoft’s service.
Fix #1: Reset Outlook’s Connection State
This isn’t about restarting Outlook. It’s about resetting how it talks to Exchange.
Close Outlook completely — right-click the Outlook icon in the system tray and choose Exit.
Hold Ctrl while double-clicking the Outlook shortcut. A dialog appears: 'Choose Profile'. Click OK to start with a clean profile load.
If that works, go to File > Options > Advanced > Outlook Data File Settings. Select your mailbox, click Settings, then Repair. This rebuilds the local OST file’s index — not the data itself.
Wait 90 seconds after repair finishes. Don’t rush it. Outlook needs time to resync headers before attempting sends.
Note: This fix works identically across Outlook 365, 2019, and 2016. The new Outlook for Windows (the one installed via Microsoft Store) handles this differently — it auto-repairs every 4 hours if sync fails. So if you’re using the new Outlook and seeing delays, wait — don’t intervene.
Fix #2: Clear Cached Credentials
Here’s the counterintuitive part: Outlook doesn’t always tell you when your saved password is outdated. It just stops syncing quietly. You’ll get no pop-up. No warning. Just missing emails and grayed-out Send buttons.
Open Windows Settings → Accounts → Access work or school. Remove any listed account tied to your company email.
Go to Control Panel > User Accounts > Credential Manager > Windows Credentials.
Under 'Generic Credentials', look for entries starting with 'MicrosoftOffice16' (for Outlook 365/2019) or 'MicrosoftOffice15' (for 2016). Delete all of them — even the ones that look harmless.
Reopen Outlook. It will prompt for your password — and ask you to approve modern authentication (if your org uses it). Say yes. Let it finish the full handshake.
This step matters most for hybrid environments — where your company uses both on-prem Exchange and cloud identity. I once spent three days chasing a phantom 'server timeout' until I realized the cached token had expired 11 days earlier.
Fix #3: Disable Add-ins That Break Sending
Add-ins are useful — until one hijacks the Send process. The most frequent offenders? Grammar checkers, CRM sync tools, and legacy compliance scanners. They don’t crash Outlook — they just delay or cancel sends without logging it.
Start Outlook in safe mode: Press Win+R, type outlook.exe /safe, press Enter.
Try sending a test email to yourself. If it works instantly, an add-in is blocking it.
Go to File > Options > Add-ins. At the bottom, change 'Manage' dropdown to COM Add-ins, click Go....
Uncheck everything. Restart Outlook normally. Then re-enable add-ins one-by-one, testing send each time.
Pro tip: In Outlook 365, go to File > Options > Add-ins > Manage: Office Add-ins. Look for anything labeled 'Mail' or 'Compose' — those run during send and are the usual suspects.
Still Not Working?
If all fixes fail, escalate — but give IT the right data first. Don’t say 'Outlook isn’t working.' Say this:
'I can receive but not send — tested in both desktop Outlook and OWA.'
'Status bar shows “Connected to Exchange” but hovering reveals “Last synced: 2 hours ago.”'
'I cleared credentials and disabled all COM add-ins. Safe mode sends fine.'
Then include this table — copy-paste it into your ticket:
