Outlook Search Not Working: Why It Breaks and How to Fix It (2026 Guide)

Quick answer

Outlook search breaks for one of four reasons: the local search index is incomplete or corrupted, the Office install is damaged, the Outlook profile or data file is broken, or there’s a server-side outage you can’t fix locally. The right fix depends on which version of Outlook you’re running. Classic Outlook uses Windows Search; new Outlook and Outlook on the web search server-side and never touch your local index.

Before you start

Two things to check first, because both will save you from wasting time on the wrong fix:

Which Outlook are you using? Classic Outlook (the desktop app you’ve used for years) and new Outlook (the rebadged Outlook for Windows that Microsoft is force-migrating users into) handle search completely differently. The toggle for “New Outlook” is in the top-right of the window. If it’s on, you’re using new Outlook. The fixes below are split accordingly.
Has Microsoft confirmed an outage? Open Outlook on the web in a browser and run the same search. If web search also fails, it’s a server-side problem and nothing you do locally will help. Check the Microsoft 365 Service health dashboard (work account required) or the public Microsoft 365 Status feed.

Don’t run “Outlook PST repair” tools you’ve found via search ads. Most are paid wrappers for Microsoft’s free scanpst.exe and several are flagged by SmartScreen. The native repair option is in this guide and it’s the one you want.

What “Outlook search not working” actually means

There are three distinct symptoms that all get filed under the same complaint:

No results returned for a query you know should match. Most common.
Stale results. Search returns emails from last year but not last week. This is an indexing-behind problem, not a search-broken problem.
Search box greyed out, won’t accept input, or returns “Something went wrong.” This is usually a Windows Search service problem, not Outlook.

Knowing which symptom you have changes the fix order. If search works for old mail but not new mail, you don’t need to rebuild anything — you need to wait or kick the indexer. If search returns nothing for any query, the index is empty or pointing at the wrong data file.

Where this error appears

Outlook version	Search engine used	Local index involvement
Classic Outlook (Windows desktop)	Windows Search	Full — relies on Windows Search Indexer
New Outlook for Windows	Server-side (Microsoft 365 cloud)	None
Outlook on the web (OWA)	Server-side	None
Outlook for Mac	Spotlight (macOS)	Full — different system
Outlook mobile	Server-side	None

This matrix matters more than any other diagnostic step. If you’re on new Outlook and search fails, rebuilding the Windows Search index does nothing — the index isn’t part of the problem. If you’re on classic Outlook and search fails, it’s almost always Windows Search.

Common causes

For classic Outlook:

Windows Search index is incomplete because Outlook hasn’t finished indexing a recently-created or recently-rebuilt OST/PST file.
Windows Search service is stopped or set to disabled.
Outlook is not in the indexed locations list (this happens after Windows feature updates).
The OST file is corrupted.
A third-party PDF iFilter is stalling the indexer on attachments — Microsoft has a specific support note on this.
Group Policy is blocking Outlook from being indexed (managed devices).
A corrupted Outlook profile.

For new Outlook and Outlook on the web:

Microsoft 365 service-side issue.
Mailbox migration in progress (search returns nothing during a tenant move or mailbox region change).
Search scope is set to a folder you didn’t intend.
Newly-added shared mailbox hasn’t been indexed server-side yet (this can take up to 24 hours).

For classic Outlook on Windows 11 specifically: there’s been a documented bug since late 2025 where the search indexer rebuilds the catalog repeatedly after each Outlook restart on systems with a local PST file. Microsoft confirmed the bug in September 2025; it has not been fully resolved as of this writing. If you see Search Indexer churning through 5–10GB of database changes after each Outlook launch, that’s the bug, not your setup.

Fixes to try first

Run these in order. Stop when search starts working.

1. Check your search scope. This is embarrassing but it’s the actual cause about a third of the time. In classic Outlook, click in the search box, look at the dropdown to its right, and check whether it says Current Folder, Subfolders, Current Mailbox, or All Mailboxes. Switch to All Mailboxes and try the search again. If results appear, the search wasn’t broken; the scope was just narrower than you thought.

2. Force a Send/Receive. In classic Outlook, press F9. This forces Outlook to download anything pending and tells the indexer there’s new content. Solves the “search returns old emails but not today’s” symptom about half the time.

3. Check Indexing Status. In classic Outlook, click in the search box, then go to Search > Search Tools > Indexing Status. You’ll get a dialog showing how many items are still being indexed.

“Outlook has finished indexing all of your items. 0 items remaining.” → indexing isn’t the problem. Skip to step 5.
“X items remaining.” → wait. On a fresh install or after a rebuild, indexing a 10GB mailbox can take 30–90 minutes. Leave Outlook running.
The number doesn’t decrease over 10 minutes → indexing is stuck. Continue to step 4.

4. Verify Windows Search service is running. Press Win + R, type services.msc, press Enter. Find Windows Search in the alphabetical list. Right-click → Properties. Set Startup type to Automatic (Delayed Start). If Service status shows Stopped, click Start. Apply and close. Restart Outlook.

5. Verify Outlook is indexed. Press Win + S, type indexing options, press Enter. The Indexing Options dialog opens. Microsoft Outlook should be in the Included Locations list. If it isn’t, click Modify, tick the Microsoft Outlook checkbox, click OK. Wait for indexing to complete (it’s a background task — let it run).

6. Restart Outlook with the indexing reset. Close Outlook completely (Task Manager → End Task on OUTLOOK.EXE if it lingers). Open Outlook again. Microsoft’s own recommendation is to leave Outlook running and the laptop awake until Indexing Status shows zero items remaining. On a managed device, this can take an hour or more; live with it.

For new Outlook and Outlook on the web, steps 1–6 don’t apply because there’s no local index to fix. Try this instead:

Sign out of new Outlook (top-right account picture → Sign out), close it, reopen, sign back in.
If search still fails, open Outlook on the web in a private browser window and run the same search. If web search works, it’s a new Outlook client cache problem — uninstall and reinstall new Outlook from the Microsoft Store.
If web search also fails, it’s server-side. Check tenant service health.

Advanced fixes

If steps 1–6 didn’t work, search is genuinely broken at the system level. These are more invasive — work down the list.

Rebuild the Windows Search index. Press Win + S, type indexing options, press Enter. Click Advanced → Rebuild. Confirm. This deletes the index and forces Windows to recreate it from scratch. On a typical machine with a 10GB mailbox, expect 30–60 minutes; on a slower machine or larger mailbox, allow several hours. Don’t shut down or sleep the machine until it finishes — interrupting a rebuild leaves the index in a worse state than before.

Run Online Repair on Office. This is heavier than Quick Repair and the one that actually fixes search problems. Open Settings > Apps > Installed apps, find Microsoft 365 (or Microsoft Office), click the three-dot menu → Modify. Choose Online Repair. Allow 15–30 minutes and an internet connection. If you’re not sure what Online Repair does or whether it’s safe, the full process is documented in our guide to repairing Microsoft 365.

Recreate the OST file. This forces a full re-sync from the server, which rebuilds the data the indexer depends on. Close Outlook. Find your OST file (usually at C:\Users\<username>\AppData\Local\Microsoft\Outlook). Rename it (e.g., outlook.ost.old). Reopen Outlook — it will create a fresh OST and start re-downloading mail from the server. On a large mailbox, this is a multi-hour operation. Use Outlook on the web meanwhile.

Create a fresh Outlook profile. Go to Control Panel > Mail (Microsoft Outlook). Click Show Profiles, then Add. Set up a new profile pointing at the same account. In the Mail dialog, set “Always use this profile” to the new one. Open Outlook. If search works in the new profile, the old profile was corrupted. You can copy any local PST data over manually.

Check for the PDF iFilter problem. If search works for everything except text inside PDF attachments, the third-party PDF iFilter (typically Adobe Reader’s) is stalling the indexer. Update Adobe Reader or your PDF viewer first, then rebuild the index again.

If you are on a work or school device

Two things change. First, the indexing rebuild may be blocked by Group Policy, in which case you’ll see a permissions error when you click Rebuild. That’s not something you can fix locally. Second, the OST file may be encrypted or stored in a managed location, and renaming it can trigger Defender for Endpoint or your DLP solution. Coordinate with your admin before recreating the OST.

If your tenant has just migrated mailboxes between regions, search will be unavailable until the mailbox is re-indexed server-side. Microsoft documents this as up to 24 hours. If it’s been longer than that, your admin needs to open a tenant support ticket — there’s nothing the user can do.

If multiple users are reporting the same issue at the same time, it’s a tenant-side problem. Stop troubleshooting locally.

When to stop

There’s a point where rebuilding things in sequence stops being the answer. Stop and escalate to your IT team or the mailbox owner if any of these apply:

You’ve run Online Repair and rebuilt the index, and search still returns nothing.
Search is broken across multiple machines for the same user account.
Search is broken across multiple users in the same shared mailbox.
The mailbox is being migrated and the migration banner is visible in Outlook.
You’re seeing “Search results may be incomplete because items are still being indexed” persistently for more than 24 hours.

Don’t recreate Outlook profiles or OST files on a managed device without telling someone first. Don’t install third-party “Outlook search repair” tools — there’s nothing they do that the native Office repair tool doesn’t do better, and several of them ship with bundled junk you don’t want.

If Outlook is also showing as disconnected from the server, fix the connection problem first — search depends on the underlying mailbox sync.

Outlook Disconnected From Server — connection issues that can cause stale search results.
How to Repair Microsoft 365 Without Losing Files — the proper way to run Online Repair.

Official references

FAQ

Why does Outlook search return some results but not others? Almost always indexing scope. The index covers what Windows knows about — if a folder, archive, or shared mailbox isn’t in the indexed locations list, items in it won’t be found. In classic Outlook, check Search Tools > Locations to Search and make sure every mailbox you want searched is selected.

Will rebuilding the index delete my emails? No. Rebuilding the index only deletes the search catalog (a separate database that lives at C:\ProgramData\Microsoft\Search\Data). Your emails sit in the OST or PST file and aren’t touched. The catalog gets recreated from scratch by re-reading your mail.

The Search and Indexing troubleshooter from older guides doesn’t exist on my Windows 11 machine. Why? Microsoft retired the built-in Search and Indexing troubleshooter in Windows 11 version 23H2. Older articles still recommend it. Use the manual indexing rebuild (Indexing Options > Advanced > Rebuild) instead.

Why is search slower since I upgraded to Windows 11? Classic Outlook on Windows 11 has a documented indexing bug confirmed by Microsoft in September 2025. The Search Indexer reorganizes the index every time Outlook restarts and after each new email batch arrives. There’s no user fix yet — it’s a Microsoft bug. Reduce its impact by limiting the time period your mailbox keeps locally (File > Account Settings > double-click account > Use Cached Exchange Mode > set to 3 or 6 months instead of “All”).

My search works fine in Outlook on the web but fails in classic Outlook. What does that tell me? The mailbox is fine; the local indexing or Outlook profile is the problem. Skip server-side troubleshooting and start with rebuilding the Windows Search index, then Online Repair, then a new Outlook profile.

Should I switch to new Outlook to avoid these issues? New Outlook removes the local indexing problem because it searches server-side. It also removes a long list of features classic Outlook still has (PST support, granular rules, several add-ins). The right answer is “switch when new Outlook supports the features you need” — not “switch because search is broken.” See our analysis of new Outlook vs classic Outlook for the full picture.

↑ Back to top