Microsoft Search in Bing (microsoftsearchinbing.exe) v1.0 Crashes at an Increasing Rate

ControlUp has identified an upward crash trend affecting microsoftsearchinbing.exe, a background service associated with Microsoft Search in Bing.

Starting in the first week of August 2026, both the daily number of crashes and the number of affected devices increased significantly. Daily crashes rose by approximately 600%, while the number of affected devices increased by approximately 500%. The vast majority of observed crashes involve microsoftsearchinbing.exe version 1.0.0.0.

This behavior has been observed across more than 110 organizations and is classified as low severity.

Crashes of microsoftsearchinbing.exe may disrupt the display of internal Microsoft 365 search results for organizations that have enabled Microsoft Search in Bing. This may affect search results from sources such as SharePoint, OneDrive, internal contacts, organizational charts, and Teams messages.

Because the affected component is tied to search-result presentation rather than core endpoint operation, and because the expected risk of major end-user workflow disruption is limited, this finding is classified as low severity.

Microsoft has not published a specific advisory for this issue at this time.

Organizations experiencing crashes related to microsoftsearchinbing.exe version 1.0.0.0 should review affected endpoints, monitor crash frequency, and determine whether impacted users rely on Microsoft Search in Bing for internal Microsoft 365 content discovery.

Customers experiencing this crash are encouraged to contact Microsoft Support for further investigation. If a validated workaround or resolution is identified, sharing that information with the community may help others confirm scope and accelerate remediation.

This finding highlights how background Microsoft 365 integration components can show meaningful crash regressions even when the immediate end-user impact appears limited.

ControlUp will continue monitoring this crash pattern to determine whether the issue expands across more environments, correlates with specific Microsoft 365 tenant configurations, or is addressed in a future Microsoft update.