Copilot stops responding on Windows 11: Complete guide to fix it

When Copilot freezes in Windows 11 and there is no way that Boot, the feeling is one of total helplessness. Many users report that the icon appears, but does not react, neither from the Start menu nor from the Edge sidebar.. Even after reinstalling from the Microsoft Store or repairing the system, the behavior does not change, which points to deeper causes: problematic updates, corrupted dependencies, or network crashes. In our Guide to common Copilot faults You will find more examples and symptoms reported by the community.

In recent weeks, very similar cases have arisen in teams with Windows 11 24H2 and even on Windows 10 Home Single Language 64-bit, with genuine licenses and up-to-date systems. After a certain September rollup (KB5065429 is cited in several reports), Copilot stopped starting and in some cases appeared to "disappear". Others only had one part fail: the voice in the Edge sidebar stopped working when they activated Vision. This article compiles all those symptoms and tried-and-tested solutions, ordered from least to most invasive, so you can get Copilot back without wasting time or data; also check out our Recommendations for activating and using Copilot if you need a complete review.

Why Copilot stops responding after updating Windows 11

The pattern repeats itself: after a major update, Copilot and Edge components start to fail. There are indications that certain patches may corrupt key system files or leave dependencies unfinished., especially UWP, .NET components, or the runtime Microsoft Edge WebView2, which is what drives much of the experience. If you need a step-by-step reference on how to reinstall and configure Copilot, Guide to setting up Windows 11 with Copilot it is useful.

Copilot's close relationship with Edge also comes into play. If the browser becomes corrupted or its supporting services (such as Microsoft Edge Elevation Service) stop working, the domino effect reaches Copilot.Something as simple as a disabled or stuck service can be enough to render the interface unresponsive.

Several investigations also cite environmental factors: Unsupported region and language, DNS/proxy blocking access to Microsoft servers, or antivirus/firewalls silently blocking. When you add a user profile with abnormal permissions or corrupted caches, the equation becomes even more complicated. If you suspect the regional or language settings, try change the Copilot language as a diagnostic test.

Finally, there have been cases where the problem came "from above": There was talk of Copilot being temporarily disabled at source and support recommended waiting for a patch for a few days.If this is your case, it's a good idea to check the status of Microsoft services before going crazy changing things.

Common symptoms and error messages

Identifying the case studies helps to choose the appropriate solution. These are the most common symptoms when Copilot stops responding.:

• Icon that does not open: You launch Copilot from Start or the sidebar and nothing happens, no visible errors.
• The Get Help app also won't start (“Get Help”), which suggests a UWP dependency or permissions issue.
• From Edge, Voice fails with Vision enabled: When you press the microphone, it says, “An error has occurred. That’s on me, something went wrong. Please try reconnecting.”
• In a new profile it does not change: Even after creating another local/administrator account, Copilot still won't start.
• WebView2 reinstalled without effect: You install the Evergreen x64 runtime manually and Copilot doesn't appear or enable.

On devices with Edge updated, the Voice/Vision pattern is very clear: If the Vision flag is active, Voice breaks; if you disable it, Voice returns, but you lose Vision. In the web version of Copilot (copilot.microsoft.com) Voice does work, which limits the bug to the integrated Edge sidebar; in the meantime, you can check how use Copilot Vision to assess whether to temporarily disable that option.

Quick checks before you get started

Before moving on to more sweeping changes, it's a good idea to get the basics out of the way. These quick checks solve more problems than you might think.:

• Connectivity: try other sites, restart the router and verify that you're not using the wrong proxy (Settings > Network & Internet > Proxy). If in doubt, temporarily disable it.
• Microsoft Services Status: Check the official status page and, if you want a second opinion, Down Detector for regional outages.
• Login successful: located on Microsoft 365Please verify that you are using a licensed Copilot account where applicable; an incorrect login may cause strange "silences."
• Region and language: Set a supported country/region (e.g., Spain or Mexico) and set English (United States) as the preferred testing language if you suspect a regional limitation. There are wave rollouts and features that arrive in phases..
• Cache/cookies: Clear your browser and try again; corrupted data causes strange behavior.
• Restart: It sounds like a cliché, but a full reboot brings up services and reestablishes connections. Sometimes it's a miracle cure.

A tangential note: don't confuse system health with web load metrics. Indicators such as FCP, LCP or CLS (time to first render and visual stability) do not explain by themselves why Copilot does not react; are useful for analyzing page performance, not the startup of apps UWP/Edge.

Solutions derived from real cases (from least to most intrusive)

Several people have followed similar paths and we have consolidated what works best. Apply the steps in order, checking after each one if Copilot revives..

1) Uninstall the problematic update and pause Windows Update

If the failure started right after a cumulative patch, try removing it. Go to Settings > Windows Update > Update History > Uninstall Updates and remove the latest package associated with the issue date (KB5065429 was reported in September). After verifying that Copilot starts, temporarily pause updates.
You can use the Windows Update pause to wait until the corrective patch arrives..

2) Repair the system image (DISM/SFC)

If system files are corrupted, DISM and SFC can recover them. Open Command Prompt as administrator and run in batches:

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

In some environments, they have needed to repeat the sequence several times until it is "clean." Running it 3–5 passes can ensure a complete repair if you still see damage at first..

3) In-place (non-destructive) repair with Windows 11 ISO

When DISM/SFC aren't enough, in-place repair can often fix components without touching your files. Download the official ISO, mount the image and run setup.exe. In the wizard:

1. Select “Change how the installer downloads updates” and choose “Not now.”
2. Under “Select what to keep,” select “Keep personal files and apps.”
3. Complete the installation. If it asks for a key, the ISO does not match your edition.; download the correct one.

This fix will restore UWP/Edge dependencies without deleting anything. It is one of the most effective methods without forma tear.

4) Re-register UWP packages with PowerShell

To rebuild logs from modern apps, use PowerShell (admin) and run:

Get-AppXPackage -AllUsers | Foreach { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }

This command re-registers each AppX, which can reactivate Get Help and Copilot dependencies. Useful when the app does not open and does not show any error.

5) Check and restart critical services

Open services.msc and make sure it is “Running” and “Automatically” started: Microsoft Edge Elevation Service, Web Account Manager and Windows UpdateIf any of them fail, set it to Automatic and restart it. One stuck service is enough to crash Copilot..

6) Check Microsoft Edge and WebView2

Copilot relies heavily on Edge and its runtime. In Settings > Apps > Installed apps > Microsoft Edge, first use "Repair" and if the problem persists, "Reset". Next, reinstall the “Microsoft Edge WebView2 Runtime (Evergreen)” x64 runtime and verify that it is listed under Applications. If it doesn't appear, repeat the installation as administrator..

7) Reset the network and check firewall, antivirus, DNS and proxy

From CMD (admin), resets the TCP/IP stack and DNS:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns
netsh int ip reset
netsh winsock reset
netsh winhttp reset proxy

Then try alternative DNS (reports suggest 4.2.2.1 and 4.2.2.2) to improve resolution to Microsoft services. Temporarily disable third-party firewalls and antivirus; some block silently.If they continue to bother you in the background, temporarily uninstall them and restart. Remember to reactivate your protection when you're done.

8) Region and language support

Go to Settings > Time & language > Language & region. Choose a country supported by Copilot and set English (United States) as your preferred test language.. Restart and check. Some Copilot features arrive in waves and may be limited by region/language, especially for new features.

9) Create a clean user profile

To rule out corruption of the current profile, create a local administrator from CMD (admin):

net user NUEVOUSUARIO NUEVACONTRASEÑA /add
net localgroup administrators NUEVOUSUARIO /add

Sign in with that account and try Copilot. If it works there, the origin is in the previous profile (caches, permissions, etc.).

10) Clean boot

Configure a clean boot with minimal services and drivers by following Microsoft's official clean boot guide. It is used to isolate third-party software conflicts.Avoid disabling network services or Copilot/Edge-related services during testing, or the results will be falsified.

11) Copilot Connectivity Solver

Open “Get Help” and search for “Copilot Connectivity Troubleshooter.” Follow the guided steps to detect firewall rules, proxies, or blockers.. It is a specific assistant that speeds up network diagnostics for Copilot.

Edge: Voice vs. Vision conflict in sidebar

Several users have described a very precise conflict: When the #edge-copilot-vision flag was active, the “Talk to Copilot” mode in the sidebar failed with the error mentioned above.When you disable the flag, Voice works again, but Vision disappears. On the Copilot website, Voice does work fine, which narrows the problem down to the sidebar integration.

What you can do until the fix arrives: Temporarily disable the experimental flag for Vision in Edge and prioritize Voice stability if you use it daily.. Also, create a new Edge profile and test there; in some cases, the profile+flag combination was the trigger. Keep Edge updated to the latest stable version.

Vision and Voice availability may advance in waves and by region. It is reasonable to think of a phased deployment in Spain/Europe and that there may be temporary incompatibilities.Microsoft should improve the error message to make the cause explicit (conflict, unavailability, etc.), but in the meantime, the most solid workaround is to disable Vision if you need Voice in the sidebar.

Copilot key behaves like Right Ctrl (MSI and others)

After a clean install, there are some computers where the "Copilot key" doesn't invoke anything and is mapped as Right Ctrl. This usually depends on the manufacturer's firmware/utility and native Windows support for that key.If your OEM doesn't expose the feature, you can resort to remapping.

Two practical paths: use Microsoft power toys (Keyboard Manager) to remap the key to a combination that opens Copilot or create a shortcut that invokes the Copilot protocol and assign a hotkey to it.

• power toys: Remap Right Ctrl to "Win + C" (the classic Copilot shortcut on Windows). If your build uses another shortcut, remap it to that one. It's reversible and quick.
• Direct access: create a desktop shortcut targeting ms-copilot: (or the current command/URI for your build), assign a shortcut key to it, and if your keyboard/OEM utility allows you to bind the Copilot key to an executable/shortcut, point to that.

Also check your brand's software (MSI Center, etc.). Some OEM utilities allow you to assign functions to special keys, including the Copilot key.. If native support isn't yet deployed on your model, remapping with PowerToys is a clean workaround until it arrives. You can also check out the ways to access Copilot from the keyboard for alternative options.