You're in Outlook, you type a keyword into the search bar, and nothing comes back. No results, maybe a spinning wheel, then an error toast: 0x80040D05. This usually hits after a big mailbox import, a crashed Outlook session, or a botched Windows update that interrupted the indexing service. It's not a mailbox problem — your emails are still there. The index Outlook uses to search is toast.
What 0x80040D05 Actually Means
That hex code is a Windows Search error. It translates to "the index is corrupt or inconsistent." Outlook doesn't search your PST or OST files directly — it queries the Windows Search service, which maintains a separate database of your emails. When that database gets out of sync, Outlook can't find anything, even though the data is fine. The fix isn't to repair Outlook or your mailbox. It's to rebuild the index from scratch. Skip the built-in "Search Tools" repair option — it rarely works because it tries to patch the same broken index. Nuke it and start over.
The Fix: Rebuild the Index (Works in 99% of Cases)
Do this in order. Don't skip ahead. It takes about 10 minutes of hands-on time, plus indexing time afterward.
- Close Outlook completely. Make sure it's not running in the background — check the system tray for the Outlook icon and right-click to exit if it's there.
- Open Indexing Options. Press Win + R, type
control /name Microsoft.IndexingOptions, and hit Enter. On Windows 11, it's under Settings > Privacy & Security > Searching Windows, but the control panel command still works. - Change the index location. This forces a full rebuild. Click Advanced > Index Location, then change the path (e.g., from
C:\ProgramData\MicrosofttoD:\IndexBackup). If you don't have a second drive, just add a folder name likeC:\IndexRebuild. Click OK — Windows will ask to rebuild. Confirm it. - Wait for the rebuild to start. You'll see "Indexing complete" or a progress bar. This can take 30 minutes to a few hours depending on mailbox size. Don't stress — you don't need to watch it.
- Restart Outlook. Once indexing is done, open Outlook and try searching again. The error should be gone.
This works because changing the location kills the old corrupted index file and creates a fresh one. If you want to be extra clean, you can also stop the Windows Search service first — but that's rarely necessary unless the rebuild fails.
If It Still Fails: Check These Two Things
Rebuilding didn't fix it? You're in the unlucky 1%. Two culprits left:
- Third-party antivirus locking the index files. Some AV suites (looking at you, McAfee and Norton) interfere with the Windows Search service. Temporarily disable real-time scanning, repeat the rebuild, then re-enable. If that works, whitelist the Outlook data folder and the index location.
- Outlook itself has a broken add-in. A bad add-in can trigger the error even after a clean index. Start Outlook in safe mode (
outlook.exe /safe) and test search. If it works, disable add-ins one by one via File > Options > Add-ins > Manage COM Add-ins.
One more thing — if you're on a corporate machine with a roaming profile, the index can get corrupted every time the profile syncs. That's an admin problem. Push your IT team to exclude the index location from roaming profile sync.
Prevention: Stop This From Happening Again
Most folks never see this error twice, but if you do, knock on wood. To reduce the odds:
- Keep Windows and Office updated — Microsoft has patched several index corruption bugs over the years.
- Don't force-kill Outlook during a large import or sync. Let it finish or close gracefully.
- If you use a PST file on a network drive, move it locally. The index hates network latency.
That's it. Rebuild, restart, search. If you're still stuck after that, you're dealing with something else entirely — open a support ticket with Microsoft and reference the error code. They'll ask you to do exactly what you just did, so you can skip ahead.