You clicked the Copilot icon and got that lovely “Something went wrong” screen. Or maybe even worse — the icon is just sitting there, completely ignoring you. No error, no response, nothing.
Good news: your PC is almost certainly fine. This usually isn’t a hardware problem or a sign that something is seriously broken. Nine times out of ten it’s a background licensing hiccup, a stale browser session, or a Windows update that quietly knocked something out of sync.
Here’s what we’d actually try if this happened in the office today — no padding, no obvious stuff you’ve already tried.
1. Don’t Just Sign Out — Actually Re-sync Your License
Generic troubleshooting guides tell you to sign out and back in. That’s not wrong, but it’s incomplete. The real issue is that Microsoft 365 apps — Word, Excel, Teams — sometimes cache your old license information in memory even after you sign out of Copilot itself.
Here’s the version that actually resets everything properly:
- Open Word (or any Microsoft 365 app).
- Go to File → Account.
- Click Sign Out from there — not from Copilot directly.
- Close the app completely. Not minimize — actually close it.
- Reopen it and sign back in.
This forces your machine to re-sync the license key with Microsoft’s servers rather than pulling it from a cached local copy. It’s a different process than signing out of Copilot in the browser, and it fixes situations the standard sign-out doesn’t touch.
Why this works: Copilot’s availability is tied to your Microsoft 365 license status at the application level, not just your browser session. When that cache goes stale — usually after updates — Copilot loses its authorization silently.
2. Your Region Settings Matter More Than You’d Think
This one surprises people. If your Windows region settings don’t match where you actually are — or if you’re in a region where Copilot has restricted availability — it can shut itself off as a security measure. No warning, no explanation, just nothing happening when you click.
Check yours: Settings → Time & Language → Region. Make sure the country matches your actual location.
And if you’re running a VPN, turn it off before testing Copilot. Microsoft’s servers notice location inconsistencies — if your IP says you’re in one country but your system settings say another, Copilot sometimes just refuses to connect rather than throwing an error. Disabling the VPN is a 10-second test that rules this out completely.
3. Clear Your Browser Cache — But Do It Properly
If you use Copilot through Edge, months of accumulated cookies and cached data can start conflicting with your session. Most guides tell you to clear everything — that works, but it also logs you out of every site you use.
A less disruptive approach: in Edge’s cache clearing settings, you can filter by site and clear only Microsoft-related cookies specifically. That’s usually enough.
But if you want to be thorough — or if the selective clear didn’t help — use Ctrl + Shift + Del, set the time range to the last 24 hours, and clear both cached files and cookies. Then reload the page with Ctrl + F5 rather than just F5. The difference matters — Ctrl + F5 forces a full reload from the server instead of pulling anything from local cache.
Similar cache issues show up across other AI tools too — we covered the same thing in our Gemini AI down guide and the Grok error fixes.
4. Don’t Ignore Optional Windows Updates
Microsoft ships Copilot-related patches almost weekly. Most people check for updates, see “You’re up to date,” and stop there. That’s not the whole picture.
Go to Settings → Windows Update → Advanced Options → Optional Updates. There’s often a .NET Framework patch or a driver update sitting there that Windows won’t install automatically. These sound unrelated to Copilot, but they’re sometimes exactly what’s blocking it — Copilot’s background processes depend on components that these patches fix.
Install anything pending there, restart, and test again before moving on to more complex troubleshooting.
If None of That Worked
For the smaller percentage of cases that survive all four fixes above, it’s usually one of two things.
Copilot broken inside Teams specifically
Teams has its own separate cache that corrupts independently of everything else — and frustratingly, it survives uninstalling and reinstalling the app. You have to clear it manually.
Need Something Working Right Now?
If Copilot is down and you can’t wait, these cover most of the same use cases:
- ChatGPT — no Microsoft account needed, free tier is genuinely useful for day-to-day tasks.
- Google Gemini — better fit if your work is in Google Docs or Gmail.
- Claude — handles long documents and complex writing tasks better than most alternatives.
- GitHub Copilot — completely separate infrastructure from Microsoft Copilot. Keeps working when everything else is down, if coding is what you need it for.
Full comparison at our AI tools overview.