Classic Outlook Search Stays Stale After Moving Mail: Registry Workaround as Hotfix Pending

What Microsoft has confirmed​

The issue is listed on Microsoft's support site under the title "Classic Outlook issues with service assisted search for shared mailboxes," and it applies to Outlook for Microsoft 365. Microsoft describes the problem plainly: Server Assisted Search against Online Mailboxes does not update as results change.

The title mentions shared mailboxes, but the problem isn't limited to them. Microsoft's own notes say this issue can be reproduced with a single mailbox in online mode. Someone working only in their own mailbox could hit it too, provided they're in online mode rather than Cached Exchange Mode.

Moving items isn't the only trigger. Microsoft adds that this issue may also occur for setting a category or marking an item as read / unread. Microsoft calls these possible extra symptoms, not required conditions.

Summary: Results from Server Assisted Search in classic Outlook can go stale after you move, categorize or mark a message. Microsoft's repro uses a single online-mode mailbox, so shared mailboxes aren't the only ones affected.

How to check whether you're affected​

Microsoft gives a short test. Help desks can use it to confirm the issue before changing anything:

1. Open a mailbox in online mode.
2. Pick a folder, do search for items within folder, "Current Folder" is scope.
3. Pick one of the search results and drag it to an adjacent folder.
4. Check the result. Per Microsoft: Expected result: Item vanishes from search Actual result: Item is still in search, we get errors trying to click on it.

If the message stays in the list after you move it, and clicking it gives an error, you're seeing this bug.

Some early coverage called this "broken search indexing," but Microsoft's wording is narrower. The documentation says Server Assisted Search results don't update after an item changes. It doesn't mention a corrupted or rebuilding local index. That matters for troubleshooting. Rebuilding the Windows Search index is the usual fix for Outlook search problems, but nothing in Microsoft's notes suggests it will help here.

Status: fix in progress, no ETA​

Microsoft's status line is short. This issue has been escalated as a hotfix to the Outlook Team, and a fix is in progress. There is no ETA yet. The company says we will update this topic when the fix is available.

The issue page shows a last-updated date of September 29, 2026. It also appears on Microsoft's main page of recent classic Outlook problems, where it is listed as [FIX IN PROGRESS] Classic Outlook issues with service assisted search for shared mailboxes under the heading for known issues in October 2026 updates.

The page may not be new. A Microsoft Q&A answer from about a year ago already linked to an article with the same title. A third-party search-troubleshooting blog also says Microsoft published a separate article on September 30, 2025 covering service-assisted search. So the September 29 date could be a revision of an existing topic rather than a first report. Microsoft hasn't said when the bug first appeared, and it hasn't listed affected builds or update channels.

The workaround: turn off Server Assisted Search​

Until the hotfix ships, Microsoft says to temporarily disable Server Assisted Search, which will fall back to the legacy Windows Desktop Search, with the following registry key:

HKEY_CURRENT_USER\software\policies\Microsoft\office\16.0\outlook\search
DWORD: DisableServerAssistedSearch
Value: 1

To apply it on a single machine (the usual registry warnings apply, and exporting the key first is a good idea):

1. Close Outlook.
2. Open Registry Editor and go to the key above. If the search key doesn't exist under outlook, create it.
3. Create a DWORD (32-bit) value named DisableServerAssistedSearch and set it to 1.
4. Start Outlook again and repeat the test steps above.

Microsoft's issue page doesn't say whether Outlook needs a restart. In a Microsoft Q&A answer about stale shared-mailbox search results, a responder recommended closing Outlook first, then restart Outlook and test searches (it falls back to local Windows Search, which might be faster for small mailboxes). The same answer suggests you revert to 0 if no improvement. That's community advice, not official guidance, but restarting Outlook is a safe step either way.

Check the registry path​

Older troubleshooting guides often show a different path. One widely shared guide tells readers to navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Search, without the Policies segment. For this bug, Microsoft specifies the policies path, which is where Group Policy settings live. If you copy a registry snippet from an older guide, check the path before you deploy it to a few hundred machines.

Trade-offs​

Turning off Server Assisted Search sends search back to the local Windows Desktop Search index. Microsoft doesn't describe the performance or coverage effects for this case. From general experience, though:

• Local search only finds what's indexed locally. How well it works depends on the Windows Search index being healthy and up to date.
• Online mode is the tricky case. Online mode was the condition that triggered the bug in the first place. If your users run in online mode because of shared mailboxes or VDI, test whether legacy search returns the results they need before rolling the change out widely.
• Remember to undo it. Because the value sits under the policies hive, it will stay in place after the fix ships unless someone removes it. Track which machines have it so you can delete the value later.

This has happened before​

Classic Outlook's move to Microsoft Search has caused a run of search problems, many involving the "Current Folder" scope and shared mailboxes. Microsoft's known-issues page lists several:

• From January 2024: [FIXED] Searching Current Folder of an auto-mapped shared mailbox in Outlook Desktop returns no results or results from other folders
• From June 2025: [FIXED] Shared mailbox folders flicker and move around when trying to move items to the folders

At the time of the 2024 issue, one Microsoft-focused blog reported that the problem arises due to ongoing changes related to the migration to Microsoft Search, a process currently in progress. Microsoft hasn't given a cause for the current bug, so don't assume it has the same origin. Still, server-side search in classic Outlook has been changing for several years, and odd edge cases around shared and online mailboxes keep showing up.

Microsoft is putting most of its effort into the new Outlook for Windows. Many enterprises still depend on classic Outlook, and a hotfix suggests Microsoft still treats breakage there as urgent.

What admins should do​

• Confirm the bug first. Run Microsoft's four-step test on an affected user's machine. If moved items don't stay in the results, you have a different problem.
• Apply the workaround only where it's needed. Use the policies path exactly as Microsoft gives it, preferably on a pilot group first.
• Record which machines you changed so you can remove the value once the fix arrives.
• Watch Microsoft's known-issues page. Microsoft says it will update the topic when the fix is available. Until then, all Microsoft has said is "fix in progress."

Bottom line: This bug is annoying, but it doesn't destroy data. Search results go stale and throw errors when clicked. Microsoft has confirmed it, a hotfix is in progress, and there's a one-value registry workaround. The fix has no date yet, so test the workaround before deploying it and plan to remove it later.