How to Fix Outlook Search Not Updating in Shared Mailboxes

A user searches a shared mailbox in classic Outlook, drags one of the results to a different folder, and the result stays put in the search list anyway, pointing at an email that’s no longer there. Mark it read, mark it unread, or change its category, and the same thing happens: the search results freeze at whatever state they were in when the search ran, regardless of what’s actually changed since.

This is Outlook search not updating to match what’s actually in the mailbox, and Microsoft confirmed it on its classic Outlook known-issues page, under the title “Classic Outlook issues with service assisted search for shared mailboxes.” It’s listed as fix in progress as of the October 2026 update cycle, with no release date given yet.

What’s Actually Broken

The bug sits in Server Assisted Search, classic Outlook’s server-side search against online mailboxes. It’s reproducible against a delegate or shared mailbox with Download Shared Folders turned off, and Microsoft notes it also reproduces on a single mailbox running in online mode, so this isn’t strictly a shared-mailbox-only problem, just one where it surfaces most often.

The repro is simple: search a folder, pick one of the results, drag it to an adjacent folder. The email moves. The search result referencing it doesn’t go anywhere. Clicking that stale result can throw an error, since Outlook is trying to open something that, as far as the actual mailbox is concerned, isn’t where the search index still thinks it is.

It’s Not Limited to Moving Emails

Microsoft’s documentation lists the same stale-results pattern triggered by marking an item read or unread, or changing its category. None of those actions remove or update the item in the search results the way they should.

A related, separate failure shows up specifically when searching Current Folder scope while results are sorted by category: Server Assisted Search can simply return nothing. And searching a shared calendar with Server Assisted Search active has been reported to crash Outlook outright rather than just showing wrong results, a more disruptive version of the same underlying search path misbehaving.

The Registry Workaround

Microsoft’s documented fix for now is disabling Server Assisted Search, which drops Outlook back to the legacy Windows Desktop Search for that machine:

Registry path: HKEY_CURRENT_USER\software\policies\Microsoft\office\16.0\outlook\search
DWORD name: DisableServerAssistedSearch
Value: 1Code language: CSS (css)

Create the key if it doesn’t already exist, set the DWORD value to 1, and restart Outlook. Search then runs against the local Windows index instead of the online service-assisted path, and Outlook search not updating after a move, a read-status change, or a category change stops happening, because the search that was breaking isn’t the one running anymore.

For a handful of affected users, setting this manually through Registry Editor is fine. Across a fleet, it’s a one-line Group Policy preference or a script pushed through whatever configuration management you’re already using, since this is a per-user registry value under HKEY_CURRENT_USER rather than a machine-wide setting.

What the Workaround Breaks

Microsoft’s own documentation flags a side effect worth knowing before rolling this out broadly: disabling Server Assisted Search can cause replies sent from search results to stay stuck in the Outbox instead of sending. If anyone on an affected mailbox regularly replies directly from a search results list rather than opening the item first, that’s a workflow this registry change can quietly break while fixing the original complaint.

Local Windows Desktop Search also depends on the local index being current and complete, which cached-mode shared mailboxes with limited sync windows don’t always guarantee. On a very large shared mailbox, falling back to local search can mean slower results or results that lag further behind the live mailbox than Server Assisted Search did when it was actually working correctly.

A Second Option If the Registry Fix Doesn’t Fit

Disabling Download Shared Folders is Microsoft’s other documented option. This turns off Cached Mode for the shared mailbox, so Outlook queries the server directly instead of working from a local copy. It sidesteps the Server Assisted Search bug, but the shared mailbox becomes noticeably slower to browse and work in day to day, which is exactly the tradeoff Cached Mode exists to avoid in the first place.

Neither workaround is free. Pick based on which cost the affected users can tolerate better: slightly stale local search results with the registry fix, or a generally slower shared mailbox with Cached Mode off.

Checking Whether You’re Affected

Reproduce the exact repro Microsoft describes before rolling out either workaround tenant-wide: open a shared or delegate mailbox, search a folder, move one of the results to another folder, and see whether it disappears from the results the way it should. If it does, this specific Outlook search not updating bug isn’t what’s hitting your users, and a workaround aimed at it won’t fix whatever actually is.

Since this is marked fix in progress rather than closed, it’s worth checking Microsoft’s known-issues page periodically rather than treating the registry change as permanent. Once the service-side fix ships, there’s no reason to keep Server Assisted Search disabled, and re-enabling it (deleting the key or setting the value back to 0) restores the faster, more current search behavior it was designed to provide.

Read more: Corrupted External Drive: How to Recover Your Data Safely

References

Microsoft: Classic Outlook Issues With Service Assisted Search for Shared Mailboxes https://support.microsoft.com/en-us/office/classic-outlook-issues-with-service-assisted-search-for-shared-mailboxes-40f3e46f-97ab-43ec-9fa2-6d16c0477751