Copilot WebView2 Crash: Diagnose the Runtime Without Disabling Security

Official documentation checked October 14, 2026.

If a Copilot window freezes or closes and the failure mentions msedgewebview2.exe, investigate the WebView2 runtime and the app hosting it. A blank pane alone is not proof of a runtime crash. Keep antivirus, firewall and Memory Integrity enabled while you establish what actually failed.

Identify the app and collect evidence of the crash

Record whether this happens in a Microsoft 365 desktop app, the standalone Copilot app or a browser. Those are different clients; do not assume every version uses the same embedded components. Microsoft documents WebView2-dependent features in Microsoft 365 Apps, but installing or repairing that component is not a universal fix for all Copilot errors.

1. Save your work. Reopen the affected app and reproduce the problem once, noting the time and exact message.
2. Open Windows Event Viewer > Windows Logs > Application and look for a matching application failure. Record the faulting application and module. A failure in the host app and a failure naming msedgewebview2.exe require different investigation.
3. Observe the app in Task Manager without ending processes. Record whether its WebView2 processes appear and then disappear, or remain running while content fails to load.
4. If permitted, compare the same account in an approved browser with a non-sensitive test. Browser success narrows the client investigation; it does not prove a damaged runtime installation.

Give these observations to IT. Microsoft’s WebView2 security-tools guidance identifies useful application, process and security evidence. Avoid posting crash dumps publicly: they can contain sensitive application data.

Update or repair the affected component, not every browser component

Install approved updates for the affected app and Windows, then restart the app after saving your work. Evergreen WebView2 has its own servicing, separate from the Microsoft 365 Apps update channel. The version on edge://settings/help is the Edge browser version, not proof of the runtime version used by Copilot.

Check the Microsoft Edge WebView2 Runtime entry under Control Panel > Programs > Programs and Features, where Microsoft’s Office deployment guidance documents it. If support confirms the runtime is missing, use the official WebView2 download page. On a managed computer, let IT select and deploy the installer.

The Evergreen Bootstrapper downloads the runtime appropriate to the device; the Standalone Installer supports offline deployment. Both can install per-user or per-machine depending on how they are run. A Standalone Installer is not inherently a system-wide installation. See Microsoft’s runtime distribution documentation.

For an installed app that exposes a repair option, follow its supported repair workflow. Do not force-uninstall the shared runtime first: other applications may depend on it. If installation fails, record the installer error and use Microsoft’s Edge/WebView2 installation troubleshooting with IT.

Evergreen and Fixed Version are deployment choices, not labels you can reliably infer from the presence of a numbered folder. Fixed Version is bundled and maintained by the app’s publisher. Do not replace its files with an arbitrary Evergreen or preview build, or downgrade a shared runtime to test a Copilot symptom.

Resolve verified security or profile conflicts without disabling protection

Ask the security team to correlate the crash with application-control denials, blocked child processes, folder-access failures or security-software hooks. Microsoft’s guidance favors evidence-based, scoped changes and warns against broad global exclusions. A rule should target the confirmed app/runtime and preserve its sandbox and normal folder permissions.

Do not turn off Memory Integrity, real-time protection or the firewall. Adding an antivirus exclusion does not replace Memory Integrity protection. Similarly, disabling every Edge extension is not a reliable test of an embedded WebView2 app’s environment.

Do not delete a guessed Copilot package cache path or all WebView2 user data. Different apps have different data locations. For a standalone app, Settings > Apps > Installed apps > its menu > Advanced options > Repair may be available; follow Microsoft’s app-repair instructions. Treat Reset separately because it may remove local app data.

After a targeted repair, repeat the original action and compare new failures with the recorded time and module. If the problem persists, send support the app/runtime versions, installation result and matching events. Do not claim the runtime is fixed solely because an unrelated browser page opens.