Outlook search not working after installing Exchange Server 2019 CU14 SU1 (KB5036401)

Saeed Khalifi 46 Reputation points
2024-03-15T08:04:28.5266667+00:00

Hello everyone.

I recently installed SU1 (KB5036401) for CU14 on Exchange Server 2019.

It went smoothly with no issues.

After the update, users cann't search emails in Microsoft Outlook app, OWA works fine though.

Also envelope icon is showing for new mails received in Outlook app and it doesn't get cleared after opening that email, there's no issue in OWA.

There was no mention of these issues in "Known Issues" section.

Is there any workaround? Does uninstalling the update fix the issue for the time being?

Thanks in advance

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,171 questions
Office
Office
A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.
1,436 questions
Outlook
Outlook
A family of Microsoft email and calendar products.
3,331 questions
Office Management
Office Management
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Management: The act or process of organizing, handling, directing or controlling something.
2,058 questions
0 comments No comments
{count} votes

Accepted answer
  1. Andy David - MVP 144.2K Reputation points MVP
    2024-03-15T13:18:13.4266667+00:00
    3 people found this answer helpful.

6 additional answers

Sort by: Most helpful
  1. Amit Singh 4,866 Reputation points
    2024-05-22T03:45:54.1733333+00:00

    This workaround worked for many users-

    Set a field in registry to 0 and can re-enable it when fixed by putting it back to 1.

    Can confirm this workaround works.

    For on Premise Exchange:

    • Key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Search

    • Value name: DisableServerAssistedSearch

    • Value type: REG_DWORD

    • Value: 1

    setting it back to 0 presents the issue again, so can rolback once it's been fixed up.

    0 comments No comments