Bing Chat, now powered by the latest ChatGPT-based model and integrated across Microsoft Edge and Windows, is drawing strong adoption, but users frequently report that it stops responding, fails to load, or throws generic “Something went wrong” errors. The good news is most issues are routine and fixable with a handful of browser, network, and account checks that work for both Edge and Windows Search surfaces.
1. Quick checks first
Start with simple steps before deep troubleshooting: refresh the Bing Chat pane a few times, sign out and back into the Microsoft account, and try a new InPrivate window to rule out profile conflicts. If this is a first‑time glitch, a clean reload often resolves transient session errors.
2. Verify service status
Sometimes the problem is not local at all. Check outage trackers like Downdetector for Bing/Copilot service disruptions to confirm if it’s a wider issue. Large, short‑lived outages have impacted Bing and Copilot globally in the past, so validating status can save time.
3. Test the internet
Bing Chat requires a stable, low‑latency connection. Run a quick speed test and try switching networks or disabling metered connections to remove bandwidth constraints. If on a VPN or proxy, turn it off temporarily to rule out geolocation or routing blocks that can break chat sessions.
4. Restart Edge cleanly
Fully close Microsoft Edge via Task Manager and relaunch to clear stuck processes and memory‑resident sidebars. Then open the Bing button in the sidebar to start a fresh chat session, or use an InPrivate window to isolate extensions and cached credentials.
5. Clear cache and cookies
Corrupted cache or cookies commonly break sign‑in flows and chat loading. In Edge, clear “Cached images and files” and “Cookies and other site data,” then restart the browser and try Bing Chat again. This step resolves many cookie/session desync issues reported by users.
6. Disable conflicting extensions
Ad‑blockers, script filters, or AI add‑ons can interfere with the Bing sidebar and chat runtime. Temporarily disable all extensions, test the chat, then re‑enable selectively to identify the culprit. Keep tracking prevention at Balanced to avoid over‑blocking.
7. Update Edge to latest
Feature rollouts and compatibility fixes land frequently. Update Edge from Settings > About to ensure the Bing sidebar and Copilot components are current, then restart the browser. This eliminates bugs seen in older builds affecting the Discover/Bing button.
8. Try alternate entry points
If the Edge sidebar misbehaves, try bing.com/chat or the Copilot web entry to bypass sidebar integration. If Windows Search integration is flaky, launch Edge directly and open the chat from the toolbar to avoid OS‑level caching issues. Beginners’ guides can help with correct entry points and navigation.
9. Reset or repair Edge (advanced)
If problems persist, reset Edge settings to defaults to undo policy or flag changes, or create a new Edge profile to isolate account/profile corruption. As a last resort, repair Edge from system app settings to restore core components without losing data.
10. When it’s server‑side
If multiple clean environments fail and status pages report no outage, it may still be an account‑scoped or region‑scoped server issue. Microsoft’s community threads show cases where only certain accounts or regions are impacted temporarily, which typically resolves without client changes.
FAQs
-
Why does Bing Chat say “Something went wrong”?
Common causes include corrupted cookies, conflicting extensions, VPN/proxy routing, or temporary server issues; clearing cache, disabling extensions, and checking outage status usually fixes it. -
How do I check if the problem is widespread?
Look at outage trackers for Bing/Copilot and Microsoft advisories; recent incidents show global disruptions that temporarily affect many users. -
Which Edge settings should I change first?
Update Edge, clear cache/cookies, disable extensions, and test in an InPrivate window to rule out profile and extension conflicts quickly. -
Can VPNs or ad‑blockers break Bing Chat?
Yes, VPNs can trigger region or authentication quirks, and ad‑blockers can block scripts and sidebar components; turn them off and retry. -
What if it only fails on my account?
Account‑ or region-scoped glitches occur; sign out and back in, try a new profile, or wait for server‑side fixes if others can use it normally.