Google Search Stopped Working in Microsoft Edge (Build 154.0.4258.37)

Since Microsoft Edge build 154.0.4258.37 (released September 24, 2026), Google Search has stopped working for a lot of people. Set it as your default search provider, type a query into the address bar, hit Enter, and nothing useful happens.

I ran into this myself. Type a search term, hit Enter, and nothing happens at all. No navigation, no error, no fallback page. Interestingly, it only fails for actual search terms. Start typing the beginning of a URL that’s already in your history, and Edge’s address-bar autocomplete still works fine. It’s specifically the “build a search query from the default provider” path that silently dies.

Other people are seeing variations of the same problem:

• The address bar returns a blank or broken results page, or silently falls back to Bing.
• The query string gets mangled. A search for hello turns into hellooq=hello, because an extra oq= parameter gets appended instead of handled correctly.
• Google disappears entirely from Settings → Privacy, search, and services → Address bar and search → Search engines, so it can’t even be re-selected as default.

It shows up most consistently where Google is configured via Intune/MDM policy (DefaultSearchProviderSearchURL). Manually configured setups aren’t fully immune either.

Table of Contents

Open Table of Contents

• The cause: a stricter URL pattern check
• Workarounds
• Conclusion

The cause: a stricter URL pattern check

Here’s the theory that fits best. Edge has been tightening validation of the OpenSearch URL template search providers use. Recent builds enforce a stricter, more literal match on the %s / {searchTerms} placeholder in a provider’s search URL.

In practice, that means a Google search URL with extra query parameters (tracking params, region codes, anything beyond a bare q={searchTerms}) is now more likely to get rejected or mishandled than it was a few builds ago.

Intune/MDM-managed setups get hit hardest. Those policy-pushed URLs are exactly the ones that tend to carry extra parameters. And a rejected or corrupted entry can also damage Edge’s local Web Data store, which is why Google sometimes vanishes from the list entirely instead of just searching wrong.

I’m not guessing at this. It’s the pattern that shows up consistently across multiple Microsoft Q&A threads describing this exact failure throughout 2026, in both consumer and MDM-managed Edge installs.

Workarounds

None of these are a real fix. They’re what’s actually worked for people until Microsoft addresses it properly.

1. Use Google’s full OpenSearch template instead of a trimmed-down one.

Counterintuitively, going more complete rather than less is what fixed it for me. Instead of a stripped-down q={searchTerms} URL, use Google’s actual OpenSearch template with all of its macros:

{google:baseURL}search?q={searchTerms}{google:RLZ}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchboxStats}{google:searchFieldtrialParameter}{google:language}{google:prefetchSource}{google:searchClient}{google:sourceId}{google:searchSource}{google:contextualSearchVersion}ie={inputEncoding}

This is the template Chromium-based browsers ship internally for Google. Using it verbatim, instead of a hand-simplified version, avoids whatever the stricter validation is tripping over.

A plain, minimal URL works for some people too. If the full template doesn’t stick, try:

https://www.google.com/search?q={searchTerms}

2. Check your Intune/MDM policy.

If Google is pushed via DefaultSearchProviderSearchURL, review the exact URL value. Strip out any query parameters beyond q={searchTerms}. If you can’t fix it centrally right away, temporarily back off the policy and let affected users configure Google manually as a stopgap.

3. Reset Edge’s search-provider data.

If Google has vanished from the list entirely, Edge’s local Web Data file is probably corrupted. With Edge fully closed:

taskkill /im msedge.exe /f
ren "%localappdata%\Microsoft\Edge\User Data\Default\Web Data" "Web Data.bak"

Restart Edge. It regenerates the file, and the default search engine list, including Google, should be selectable again.

Conclusion

This looks like Edge tightening search-provider URL validation and catching Google configurations off guard, especially policy-managed ones, rather than anything Google changed on their end.

Until Microsoft confirms a root cause or ships a fix, using Google’s full OpenSearch template, and cleaning up your Intune policy if you manage one, is the most reliable way to keep Google search working in Edge.