Outlook not responding — frozen on “Processing” or just refusing to open — is one of those problems that eats 30 minutes if you approach it wrong. The right approach depends on whether Outlook hangs on launch, hangs during normal use, or hangs when doing something specific (sending, searching, loading a calendar). You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The 30-second test that tells you the most: hold Ctrl and click the Outlook icon. This launches Outlook in Safe Mode, which disables all add-ins. If Outlook opens fine in Safe Mode: an add-in is causing the problem. That covers perhaps 40% of cases right there.
Add-ins — fix for Safe Mode stability
File → Options → Add-ins → at the bottom, “Manage: COM Add-ins” → Go → uncheck all of them → OK → restart Outlook normally. If it opens, re-enable add-ins one at a time, restarting after each, until the hang returns. The last one enabled is the culprit.
Common troublemakers: Adobe Acrobat PDFMaker, Grammarly, Teams Meeting add-in (when Teams itself is having issues), DocuSign, any old SharePoint or CRM integration that hasn’t been updated in years. Keeping only add-ins you actually use regularly — and removing the rest — prevents this class of problem recurring.
Outlook hangs on “Processing” after send/receive
This specific pattern — Outlook opens, starts processing, then freezes — is often an OST file problem. The OST (Offline Storage Table) is Outlook’s local cache of your mailbox. When it becomes corrupted or oversized, processing requests time out and Outlook locks up.
Close Outlook. Navigate to %localappdata%MicrosoftOutlook → find the .ost file for your account → rename it to .ost.old. Reopen Outlook — it creates a fresh OST and re-downloads your mailbox from the server. With a fast internet connection this takes 10–30 minutes for a typical mailbox. The old .ost.old file can be deleted after Outlook is working correctly.
This isn’t as scary as it sounds — nothing in the OST is your actual data. Everything syncs from the mail server. You’re just clearing the local cache.
Outlook profile corruption
The Outlook profile is distinct from the OST file. The profile stores account settings, server configuration, and preferences. A corrupted profile causes Outlook to hang on startup without ever reaching the “Processing” stage.
Control Panel → Mail → Show Profiles → Add → create a new profile → set it up with your email account → set it as the default profile → launch Outlook. If it works with the new profile, the old one was corrupted. The new profile downloads fresh from the server just like the OST rebuild does.
The SCANPST repair tool
Microsoft includes a built-in repair utility for PST and OST files. Find it at: C:Program Files (x86)Microsoft OfficerootOffice16SCANPST.EXE (path varies slightly by Office version). Close Outlook first → run SCANPST → browse to the .ost file → Start. It scans, reports errors, and repairs them. Run it twice if it finds errors — the first pass sometimes misses things the second pass catches.
SCANPST doesn’t always fix severe corruption, but it’s free, built-in, and fast enough to try before rebuilding the OST entirely.
Office Quick Repair
Settings → Apps → Microsoft 365 → Modify → Quick Repair. Five minutes, no internet required, fixes the most common Office installation issues. If Outlook is hanging due to corrupted installation files rather than data issues, Quick Repair resolves it. Try this before Online Repair — Online Repair is more thorough but takes 30–45 minutes and requires internet.
Large mailbox and calendar performance
Outlook slows dramatically with very large mailboxes — tens of thousands of emails in the inbox, years of calendar items, large attachments saved locally. This isn’t a crash but can feel like one if response times stretch to 10–20 seconds per action.
Archive older email: File → Cleanup Tools → Archive → set a date to archive email older than that point. Outlook creates a local .pst archive file and removes the older items from the main mailbox. After archiving, Outlook responsiveness typically improves significantly. Also check: File → Account Settings → Data Files → look for the OST file size. Files over 10 GB sometimes cause performance issues even on fast hardware.
When Outlook hangs specifically on calendar or contacts
If Outlook opens fine but hangs when switching to Calendar or Contacts: those specific data stores (separate from mail) may have corruption. For Calendar: File → Options → Advanced → Export → export the calendar as an ICS file → import it into a new Outlook Calendar folder → delete the original → check stability. This is more involved but preserves all calendar data.
Antivirus scanning Outlook attachments
Antivirus that scans email attachments in real time can cause Outlook to hang when processing emails with attachments, because the antivirus holds the file lock while scanning and Outlook waits indefinitely for it to finish. Add the Outlook data file location (%localappdata%MicrosoftOutlook) to the antivirus scan exclusions — this prevents real-time scanning of the OST/PST files themselves while still scanning attachments when they’re saved or opened elsewhere.
Related Microsoft 365 authentication issues that sometimes accompany Outlook hangs are covered in our Microsoft account authentication guide — the Azure AD token issues affect Outlook alongside Teams when they go wrong. For cases where Outlook is responding but sending is failing, our broader Outlook troubleshooting guide covers the send/receive configuration and server connection diagnostics. Microsoft’s Outlook performance documentation covers the OST cleanup tool and the advanced MAPI debug logging that Microsoft support uses for persistent hang issues.
Windows Search integration causing Outlook hangs
Outlook search uses the Windows Search index. When the Windows Search service is stopped, crashed, or rebuilding its index, Outlook’s search integration can cause the application to hang — particularly when starting up, as Outlook initialises its search connection. Task Manager → look for SearchIndexer.exe → if it’s consuming high CPU or disk, the index is rebuilding. Outlook will recover on its own once the rebuilding completes.
If SearchIndexer.exe isn’t the issue and Outlook hangs specifically when search is involved: Outlook → File → Options → Search → uncheck “Include search suggestions from the Outlook Address Book” and “Improve search speed by limiting the number of results shown.” These reduce the search integration complexity and often improve responsiveness for the search feature.
Shared mailboxes and permissions
On Exchange and Microsoft 365 accounts, shared mailboxes added to Outlook can cause hangs when the permissions for those mailboxes change. If your account loses permission to a shared mailbox that Outlook is still configured to load, Outlook repeatedly tries to connect to it, times out, and appears to hang.
Check: File → Account Settings → Account Settings → your Exchange account → Change → More Settings → Advanced → look at the Mailboxes list. Remove any shared mailboxes that you no longer have access to. After removing them, Outlook stops trying to connect to inaccessible mailboxes and the hangs during startup resolve.
Outlook and OneDrive sync conflicts
Saving Outlook attachments or PST/OST files to a OneDrive-synced folder causes conflicts — OneDrive tries to sync the file while Outlook has it open, creating a write lock conflict that manifests as Outlook becoming unresponsive. This is particularly common when a PST file is stored in Documents (which OneDrive syncs by default).
Move the OST and any PST files to a local folder outside OneDrive’s sync scope (e.g., C:OutlookData). File → Account Settings → Data Files → shows where the current data files are stored. Right-click → Open File Location to see the current path. If it’s inside the OneDrive folder structure, close Outlook, move the file to a local path, and update the path reference in Account Settings.
Memory usage and Outlook over time
Outlook’s memory usage increases during a session — each email opened, each attachment loaded, each calendar event rendered adds to the working set. After 8+ hours of continuous use, Outlook’s process can reach 1–2 GB of RAM, at which point page faults (reading from the page file) become frequent and responsiveness degrades noticeably.
The simplest fix: close Outlook and reopen it once or twice a day. This restarts the process and releases accumulated memory. Setting a scheduled lunch break Outlook restart is a reasonable practical solution for people who use Outlook heavily all day. Alternatively, upgrading system RAM from 8 GB to 16 GB gives Windows enough room to keep Outlook’s full working set in memory without paging.
Exchange server connection issues
Outlook hangs that are specifically connected to sending, receiving, or loading the address book may be caused by the Exchange server being slow or temporarily unreachable. When Exchange is slow: Outlook waits for server responses with no timeout by default, creating apparent hangs that resolve when the server responds.
Check: File → Office Account → connected services → your Exchange account → Connection Status. This shows the server connection state and latency. If the server shows high latency or disconnected status during the hang, the Exchange server is the bottleneck. This is typically an IT issue rather than a user-side fix — report it with the connection status information.
Outlook’s hardware graphics acceleration
Like other Office applications, Outlook uses hardware graphics acceleration for rendering emails with complex HTML formatting. When the GPU driver has issues with Outlook’s rendering pipeline, Outlook hangs when loading or displaying HTML emails.
File → Options → Advanced → scroll to Display → check “Disable hardware graphics acceleration.” After enabling this option, Outlook uses CPU for rendering rather than the GPU — which is slower but more stable when GPU driver conflicts are present. Update the GPU driver to resolve the underlying issue, then re-enable hardware graphics acceleration afterward.
SFC for system file corruption affecting Outlook
Outlook depends on shared Windows DLLs for file I/O, network communication, and cryptography. If any of these DLLs are corrupted, Outlook may hang during operations that invoke them — most commonly during send/receive (network/crypto) and during attachment handling (file I/O). Running SFC addresses this without reinstalling Office:
sfc /scannowAdministrator Command Prompt. Restart after completion. If SFC reports “found corrupt files and repaired them,” the corruption was the cause of Outlook’s hangs. If SFC shows no issues, the problem is more likely within Office’s own files — at which point Quick Repair or Online Repair is the appropriate tool.
Third-party Outlook add-ins vs COM add-ins distinction
Outlook supports two types of add-ins: COM add-ins (loaded locally, the classic type) and web add-ins (loaded from the internet through the Microsoft Add-ins store). COM add-ins are the ones disabled in Safe Mode. Web add-ins are not disabled in Safe Mode and can still cause issues even when the Safe Mode test passes.
Disable web add-ins: Outlook → Home tab → Get Add-ins (or Manage Add-ins) → the list shows installed web add-ins → disable any that aren’t necessary. If Outlook is stable in Safe Mode but still hangs in normal mode after disabling all COM add-ins: a web add-in is likely responsible, and this is the place to check. Web add-ins that contact external servers during startup can cause apparent hangs when those servers are slow or unreachable.
For particularly stubborn Outlook issues that survive all these approaches: the Outlook Process Monitor diagnostic (running Microsoft’s Process Monitor while reproducing the hang) captures the exact file or registry access that’s causing the hang, providing actionable information for Microsoft support. It’s technical, but for an Outlook hang that has resisted all standard fixes, the 10 minutes it takes to run is more efficient than continuing to try fixes that have already been exhausted. The Microsoft documentation for using Process Monitor with Outlook is available through their support site and walks through the configuration needed to filter for relevant Outlook events.
A practical order for this problem: Ctrl+click (Safe Mode test) → if stable in Safe Mode, disable add-ins. If still hangs: rename OST file → rebuild from server. If still hangs: SCANPST repair → if found errors, run twice. If still hangs: create new Outlook profile. If still hangs: Quick Repair. That sequence covers probably 85–90% of cases. The more specific causes (OneDrive sync conflict, shared mailbox permissions, Exchange server latency) apply when the profile and OST are clean and Office is installed correctly, and the hang is specific to one operation or one account rather than Outlook generally.
And one more thing worth saying: a “not responding” label in the title bar doesn’t always mean Outlook is truly frozen. When Outlook is processing a large sync operation — downloading thousands of emails after reconnecting, processing a meeting invite with a large attendee list, indexing search after an OST rebuild — it temporarily goes “not responding” while it completes the batch operation. These false alarms typically resolve within 60–90 seconds without intervention. The genuinely broken hangs don’t resolve, require force-closing, and happen repeatedly. Patience for a minute before force-closing saves many unnecessary SCANPST runs. If this sounds familiar, Outlook Not Receiving Emails is worth a look.
