Copilot Missing in Windows 11: How to Get GitHub Copilot Working Again

Overview

You open VS Code on Windows 11, and the GitHub Copilot icon is gone. No inline suggestions. No chat panel. The extension might show as installed but greyed out, or it may have disappeared from the sidebar entirely.

This happens more often than you’d expect. Windows 11 updates, VS Code updates, and extension updates can all independently break the Copilot integration. The fix depends on which layer failed.

One critical distinction first: GitHub Copilot (the AI code completion tool from GitHub) and Microsoft Copilot (the Windows 11 OS-level assistant) are different products with different subscriptions. This article covers GitHub Copilot in your development environment. If the Windows 11 system Copilot button disappeared from your taskbar, that’s a different issue entirely.

Symptoms

The problem shows up in several ways depending on what broke:

• Extension gone from sidebar: The Copilot icon no longer appears in the VS Code activity bar or extensions list.
• Installed but inactive: The extension shows in your installed list but has a grey icon, no suggestions appear, and the status bar shows no Copilot indicator.
• “Not signed in” or auth errors: Copilot prompts you to sign in repeatedly, or fails silently after you authenticate.
• Ghost suggestions: Copilot was working, then stopped mid-session — no error, just silence.
• Extension crashes on load: VS Code’s Output panel shows Copilot extension errors or the extension host crashing.

If you see an explicit error message in the Output panel (Ctrl + Shift + U, then select “GitHub Copilot” from the dropdown), note the exact text. It tells you which fix path to take.

Why This Happens

GitHub Copilot on Windows 11 can go missing for reasons that fall into four buckets:

Authentication layer: Your GitHub session token expired, your organization revoked seat access, or VS Code’s credential store (which uses Windows Credential Manager) got corrupted. This is the most common cause.

Extension layer: A VS Code update shipped a new extension API version that temporarily breaks Copilot, the extension auto-update failed mid-download, or extension conflicts disabled it.

Platform layer: Windows 11 feature updates occasionally reset VS Code settings or clear the credential store. Network policy changes (corporate VPN, proxy, firewall) can silently block Copilot’s backend connections.

Subscription layer: Your GitHub Copilot trial expired, your organization admin changed policy, or you switched GitHub accounts without realizing the new account lacks a Copilot license.

$ Test-NetConnection -ComputerName api.github.com -Port 443
TcpTestSucceeded : True
$ Test-NetConnection -ComputerName copilot-proxy.githubusercontent.com -Port 443
TcpTestSucceeded : True

{
  "http.proxy": "http://your-proxy:port",
  "http.proxyStrictSSL": false
}

The Windows 11 System Copilot vs. GitHub Copilot Confusion

This deserves its own section because it catches people constantly.

Windows 11 Copilot (now called Microsoft Copilot) is an OS-level assistant built into the taskbar. It handles general questions, Windows settings, web search. It has nothing to do with code completion.

GitHub Copilot is a developer tool that runs inside your IDE. It requires a GitHub account with a Copilot subscription.

If you’re searching “Copilot missing Windows 11” because the taskbar icon disappeared, you need Windows settings, not this guide. Go to Settings → Personalization → Taskbar → toggle Copilot on.

If you’re searching because your code suggestions stopped in VS Code, you’re in the right place — follow the steps above.

The naming overlap is Microsoft’s doing. The products share a brand but share zero infrastructure, accounts, or functionality.

Edge Cases and Gotchas

A few scenarios that official docs don’t emphasize:

Windows 11 S Mode: If your machine runs Windows 11 in S Mode, you can only install apps from the Microsoft Store. VS Code from the Store works, but extension installation can behave differently. If Copilot won’t install, switch out of S Mode first (Settings → System → Activation → “Switch to Windows 11 Home/Pro”). This is a one-way switch.

Managed devices (Intune/Group Policy): Corporate Windows 11 machines may have policies that block specific VS Code extensions or restrict outbound connections. The Copilot extension installs but can’t phone home. Check with your IT department if you’re on a managed device and the network test from Step 03 fails.

Multiple VS Code installations: If you have both VS Code (User) and VS Code (System) installed, extensions are stored separately. Copilot might be installed in one but not the other. Run code --list-extensions from the terminal for each installation to verify.

WSL interactions: If you develop in WSL, VS Code’s Remote – WSL extension runs a separate extension host inside the Linux environment. Copilot needs to be installed in the WSL extension host, not just the Windows side. Open a WSL window in VS Code, then install Copilot from the Extensions panel — you’ll see “Install in WSL” as a separate button.

If It Still Fails

If you’ve worked through every step and Copilot is still missing:

1. Collect diagnostic info: Ctrl + Shift + P → “GitHub Copilot: Collect Diagnostics.” This generates a report with extension version, auth status, and network checks.
2. Check the GitHub Status page — Copilot outages happen and affect everyone.
3. Try a completely different machine or browser-based VS Code at vscode.dev to isolate whether the problem is your Windows install or your account.
4. Open an issue in the GitHub Community Discussions for Copilot with your diagnostics attached.
5. If you’re on an organization plan, contact your GitHub admin — seat assignment, policy settings, and SSO enforcement can all silently block access.

FAQ