How to Resolve Copilot Edge WebView2 Runtime Crash

Copilot in Windows 11 and Microsoft 365 apps relies on the Edge WebView2 runtime to render interactive responses. When this runtime crashes, the Copilot pane freezes, turns gray, or shows a message that Copilot is unavailable. The crash occurs because the runtime process becomes corrupted, outdated, or conflicts with system-level memory or security settings. This article explains why the crash happens and provides a clear set of fixes to restore Copilot functionality.

Why the Edge WebView2 Runtime Crashes When Copilot Runs

The Edge WebView2 runtime is a separate component from the Edge browser itself. It provides a web rendering engine that Copilot uses to display HTML content, charts, and interactive controls inside the Copilot pane. When the runtime crashes, Copilot cannot load its interface or respond to queries.

The root cause is usually one of three things:

• Corrupted runtime files: A Windows update, disk error, or incomplete installation can damage the WebView2 DLLs or manifest files.
• Version mismatch: Copilot may require a newer version of the runtime than what is installed. Automatic updates sometimes fail or are delayed by group policy.
• Memory or resource conflict: Antivirus software, third-party firewall, or memory-integrity settings (Core Isolation) can block the runtime process from spawning child processes.

Understanding these causes helps you apply the correct fix without unnecessary steps. The following solutions address each of these scenarios.

Steps to Fix the Copilot Edge WebView2 Runtime Crash

Follow these methods in order. Start with Method 1, because it resolves most crashes without modifying system settings.

Method 1: Repair or Reinstall the Edge WebView2 Runtime

This method replaces corrupted runtime files without affecting your Edge browser profile or bookmarks.

1. Open Windows Settings
   Press Windows + I to open Settings. Go to Apps > Installed apps.
2. Locate Microsoft Edge WebView2 Runtime
   In the search box, type “WebView2”. Click the three dots next to Microsoft Edge WebView2 Runtime and select Modify.
3. Run the repair tool
   In the installer window that appears, select Repair. Allow the process to complete. Restart your PC when prompted.
4. Test Copilot
   Open Copilot in Windows or Microsoft 365 and verify the pane loads without the crash message.

If the repair option is unavailable or the crash persists, uninstall the runtime entirely and reinstall it from the official Microsoft Learn page. Search for “Microsoft Edge WebView2 Runtime download” and select the Evergreen Standalone Installer. Run the installer, restart your PC, and test Copilot again.

Method 2: Update Edge and WebView2 Together

Sometimes the runtime version is tied to the Edge browser version. Updating Edge forces a runtime update as well.

1. Open Microsoft Edge
   Launch Edge and click the three-dot menu (top right) > Help and feedback > About Microsoft Edge.
2. Check for updates
   Edge will automatically check and download any available updates. Wait for the update to finish and click Restart.
3. Verify WebView2 version
   After restart, type edge://settings/help in the address bar. The version number shown should match the latest stable release on the Microsoft Edge release notes page.
4. Test Copilot
   Open Copilot and confirm the pane is responsive.

Method 3: Disable Conflicting Security Software Temporarily

Third-party antivirus or firewall software can block WebView2 child processes. To test this, disable your antivirus for a few minutes and check if Copilot works.

1. Disable real-time protection
   Open your antivirus dashboard and turn off real-time scanning or web protection. Do not disable the firewall unless you are on a trusted network.
2. Test Copilot
   Open Copilot and verify it loads. If the crash goes away, add an exception for the WebView2 runtime in your antivirus settings. The runtime executable is typically located at C:\Program Files (x86)\Microsoft\Edge\Application\msedgewebview2.exe.
3. Re-enable protection
   Turn real-time protection back on after testing.

If Copilot Still Has Issues After the Main Fix

Copilot shows a blank white or gray pane

This indicates the WebView2 runtime started but failed to render content. Clear the Copilot cache by opening File Explorer and deleting the folder %localappdata%\Packages\Microsoft.Windows.Copilot_cw5n1h2txyewy\LocalCache. Restart your PC and try again.

Copilot crashes immediately on launch

If the crash happens right when you open Copilot, the runtime may be blocked by memory integrity settings. Go to Windows Security > Device Security > Core Isolation > Memory Integrity and turn it off. Restart your PC and test Copilot. If the crash stops, re-enable Memory Integrity and add an exception for WebView2 in the Windows Security exclusion list instead.

Copilot works in Edge but not in Windows or Microsoft 365 apps

When Copilot works inside Edge but not in standalone apps, the runtime installation path may be misconfigured. Run the WebView2 runtime installer again and select the option “Evergreen Standalone Installer”. This ensures the runtime is available system-wide, not only inside Edge.

Item	Edge WebView2 Runtime (Evergreen)	Edge WebView2 Runtime (Fixed Version)
Description	Updates automatically with Windows Update	Requires manual version pinning by IT admins
Best for	Consumer PCs and most business users	Enterprise environments with app compatibility testing
Impact on Copilot	Always compatible with latest Copilot features	May cause crashes if version falls behind
How to identify	Runtime folder contains msedgewebview2.exe with no version subfolder	Runtime folder contains a version number subfolder like 120.0.2210.91

If your PC uses the fixed version, contact your IT admin to update the runtime to the latest evergreen release.

You can now resolve the Edge WebView2 runtime crash by repairing the runtime, forcing an update, or checking for software conflicts. Start with the repair tool in Windows Settings because it fixes most cases without additional downloads. If the crash continues, clear the Copilot cache and verify that no security software is blocking the runtime process. For persistent crashes, check whether your runtime is the evergreen or fixed version and update accordingly. This targeted approach saves time and avoids unnecessary system changes.