Dear Mohan,
This is a known issue that some users have experienced, where the update conflicts with existing search indexing configurations.
You can follow the steps below carefully on one of the affected servers to test the solution.
Workaround: Modify Registry to Mitigate Search Issue
This procedure involves adding a registry key to revert a change introduced in the update that is causing the conflict.
- Open Registry Editor: Press
Win + R, typeregedit, and press Enter. Make sure to run it as an administrator. - Navigate to the Correct Path: In the Registry Editor, copy and paste the following path into the address bar and press Enter:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Search - Create a New DWORD Value:
- Right-click on an empty space in the right-hand pane.
- Select New > DWORD (32-bit) Value.
- Name the new value exactly:
DisableSearchBoxSuggestions
- Modify the New Value:
- Double-click on the
DisableSearchBoxSuggestionsvalue you just created. - Set the Value data to
1. - Click OK.
- Double-click on the
- Restart the Server: For the changes to take full effect, please restart the server. After restarting, the search functionality should be restored.
I recommend deploying this change via Group Policy (GPO) for easier management across all your servers. If you find this answer helpful, please don't hesitate to hit "accept answer" 😉.