Microsoft fixes Windows 11 23H2 Start menu search broken by a Bing update

A server-side Bing change broke Start menu search on some Windows 11 23H2 PCs from 6 April 2026. Microsoft rolled it back; why web search policy matters.

TechLogHub Engineering Team
April 8, 2026
3 min read
0 views

Share Article

Microsoft rolls out fix for broken Windows Start Menu search

From 6 April 2026, Start menu search stopped working properly on some Windows 11 23H2 devices. Microsoft traced it to a server-side Bing update rather than a Windows patch, and rolled that update back. It isn't a security issue. It's a useful case study for developers in how a cloud dependency can break a core local feature, and for IT teams in why the fix may not reach locked-down machines.

What happened

Microsoft acknowledged the problem in a Windows release health entry (WI1273488), reported by BleepingComputer on 8 April 2026. It said a "server-side Bing update designed to improve search performance" caused the failures and affected only a small number of users. Reports described the Start menu returning blank search results that could still be clicked.

Microsoft rolled the Bing change back and said "reports of search failures are steadily decreasing". It added that the issue "will resolve automatically as the server-side fix is gradually rolled out". No Windows update or reboot is needed. Affected devices must be online to pick up the fix, and web search must not be disabled by Group Policy.

The Start menu has had other problems recently. In November 2025, Microsoft documented a workaround for a provisioning bug in updates released since July 2025, where XAML packages failed to register in time and the Start menu, taskbar, File Explorer and Settings crashed.

Who is affected

  • Some Windows 11 version 23H2 devices. Microsoft hasn't published counts beyond "a small number of users".
  • Managed fleets where web search in Start is disabled by Group Policy may not receive the server-side fix the normal way.
  • Help desks fielding "search is broken" tickets that a local reinstall or reset won't fix.

What it means for developers and engineering teams

The developer lesson is about coupling. Windows search mixes local results (apps, files, settings) with web results from Bing. Here a change on the web side was enough to break the whole results surface, including the local part users rely on most. If you build features that combine local and remote data, the remote half needs to fail safely: time out quickly, render the local results anyway, and never let a malformed server response blank the UI.

Server-side configuration changes are also deployments. They should go out to small rings first, be watched for client-side errors as well as server metrics, and be quick to roll back. Microsoft's quick rollback is the system working, but the incident shows that a "performance" tweak in a backend can surface as a functional outage on millions of clients.

For platform and IT teams, the detail about Group Policy matters. The policy that disables web search in Start is often set for privacy or compliance reasons. Those machines behave differently from the default configuration. Test vendor fixes and known issues against your hardened baseline, not only against a stock install.

What to do now

  1. Make sure affected PCs are online and give the fix time to arrive. Signing out and back in, or restarting the Windows search processes (SearchHost.exe, StartMenuExperienceHost.exe), can help it take effect.
  2. Check search policies on managed devices. Review the Search settings under Computer Configuration > Administrative Templates > Windows Components > Search, and the related Explorer setting for search box suggestions, so you know which machines are excluded from web search.
  3. Watch the Windows release health dashboard or the Microsoft 365 admin center message center for WI1273488 status changes.
  4. Don't reinstall Windows or reset the search index for this specific symptom on 23H2. The cause was server-side.
  5. If you ship apps that mix local and remote results, add a test where the remote API returns errors or malformed payloads, and assert that local results still render.

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.

Windows 11 Start Menu Search Fix (Bing Rollback) | Microsoft Rolls Out Fix For Broken Windows Start Menu Search