The Copilot app on Windows 11 is not really a traditional app — its interface is a web experience rendered by the WebView2 runtime, Microsoft’s embedded browser engine. When that runtime is missing, corrupted, or version-mismatched, Copilot can’t draw its own window and throws a WebView2 runtime error instead. You click the app, and instead of Copilot you get an error dialog about a component you’ve never heard of.

The good news: this is one of the most fixable Copilot failures because the broken piece is a standalone, reinstallable component. Repair the runtime, clear the app’s cache, reinstall if needed — and it resolves the error in the large majority of cases without touching your data.

This guide walks through the repair in escalating order, from the non-destructive runtime repair to the full reinstall. If Copilot crashes for other reasons without a WebView2 message, Copilot app crashing covers the broader crash causes. If the app opens but its content area stays blank, Copilot web view not loading is the closer match. And two required companion reads for this batch: NPU exclusive mode app conflict for NPU-side interference, and Recall high disk IO fix if Recall is hammering the disk at the same time.

Why this happens

  • Corrupted WebView2 runtime installation: A failed update or interrupted install leaves the runtime in a broken state Copilot can’t load.
  • Missing WebView2 runtime: Some debloated or custom Windows installs strip the runtime that Copilot depends on.
  • Version mismatch after Windows updates: An update can leave Copilot expecting one runtime version while another is installed.
  • Copilot app cache corruption: Stale cached web content in the app’s data can trigger runtime errors on launch.
  • Antivirus quarantining runtime files: Overzealous security software occasionally flags WebView2 loader files.
  • Broken Microsoft Edge installation: WebView2 shares components with Edge; a damaged Edge install can take the runtime down with it.
  • Multiple conflicting runtime versions: Side-by-side installs of different WebView2 versions can confuse the loader.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Repair the WebView2 runtime

The least destructive fix is also the most likely to work: Windows lets you repair the WebView2 runtime in place, which re-registers its files and fixes corruption without removing anything. Always start here before reaching for uninstalls — there is no reason to nuke what a repair can heal.

  1. Open Settings > Apps > Installed apps.
  2. Find “Microsoft Edge WebView2 Runtime” in the list.
  3. Click the three-dot menu and choose Modify, then select Repair in the dialog.
  4. Let the repair complete, then restart the laptop.
  5. Launch Copilot and check whether the runtime error is gone.

Fix 2: Update WebView2 to the latest version

A runtime error can also mean the installed version is simply too old for the current Copilot app — Copilot updates through the Microsoft Store on its own schedule, and if the runtime lags behind, the app can refuse to load it. Updating WebView2 to the current release closes that gap.

  1. Visit the official Microsoft Edge WebView2 download page and get the evergreen standalone installer.
  2. Run the installer — it updates the runtime in place without removing Edge or your data.
  3. Restart the laptop after the installation completes.
  4. Open Copilot and confirm it launches without the runtime error.
  5. If the Store shows a pending Copilot update, install it too so app and runtime stay in sync.

Fix 3: Reset the Copilot app

When the runtime is healthy but the error persists, the problem is usually inside Copilot’s own cached data — corrupted web cache the runtime chokes on at launch. Resetting the app clears its data and returns it to a fresh-install state. Your Microsoft account sign-in will need to be redone, but that takes seconds.

  1. Go to Settings > Apps > Installed apps and find Microsoft Copilot.
  2. Click the three-dot menu, choose Advanced options.
  3. Under Reset, click Repair first and test — then click Reset if the error remains.
  4. Launch Copilot, sign back in, and test.
  5. If the error is gone, the app’s cached state was the cause.

Fix 4: Reinstall WebView2 cleanly

If repair and update both fail, the runtime installation is damaged beyond what in-place fixes can heal — time for a clean reinstall. Uninstalling removes the broken files completely, and the fresh installer lays down a known-good copy. Your Edge browser data is untouched; the runtime is a separate component.

  1. In Settings > Apps > Installed apps, uninstall “Microsoft Edge WebView2 Runtime”.
  2. Restart the laptop to clear any locked files.
  3. Download the evergreen WebView2 installer from Microsoft’s official download page.
  4. Run the installer and let it complete fully before opening anything else.
  5. Restart once more, then launch Copilot and verify the error is resolved.

Fix 5: Reinstall the Copilot app from the Store

With a healthy runtime in place, a Copilot installation that still errors has damage in the app package itself — possibly from a failed Store update. Uninstalling and reinstalling from the Microsoft Store gives you a clean app package matched to the current runtime.

  1. Uninstall Microsoft Copilot from Settings > Apps > Installed apps.
  2. Restart the laptop.
  3. Open the Microsoft Store, search for Copilot, and install it fresh.
  4. You can also grab the latest Windows 11 build from the Windows 11 download page if your system is behind on updates.
  5. Launch the freshly installed Copilot and confirm it opens cleanly.

Fix 6: Check antivirus and repair system files

In the stubborn remainder of cases, something outside both components is interfering — antivirus quarantining runtime loader files, or corrupted Windows system files the runtime depends on. Check your security software’s quarantine first, then run the system file checker. These are rare, but they explain errors that survive clean reinstalls.

  1. Open your antivirus quarantine/history and look for any WebView2 or Copilot files — restore and whitelist them.
  2. Open an elevated Command Prompt and run sfc /scannow to repair protected system files.
  3. After SFC completes, run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
  4. Restart the laptop and test Copilot again.
  5. If the error still persists, check the Microsoft support hub for current known issues with the Copilot app.

Closing

A WebView2 runtime error looks intimidating because it names a component most people have never heard of, but it is really one of the friendlier Copilot failures: the broken piece is standalone, reinstallable, and separate from your data. Repair the runtime, update it, reset the app, and reinstall — in that order — and Copilot is back. The one habit worth keeping is checking the runtime after major Windows updates, since that is when this error most likes to return.

Frequently asked questions

What is WebView2 and why does Copilot need it?
WebView2 is Microsoft’s embedded browser engine that renders Copilot’s interface inside the app. Copilot is essentially a web experience in a native shell — if the WebView2 runtime is missing or corrupted, the app cannot draw its UI and throws a runtime error.
Will reinstalling WebView2 delete my Edge data?
No. WebView2 is a separate runtime from the Edge browser itself. Repairing or reinstalling it does not touch your Edge profile, bookmarks, passwords, or history.
Why does the error return after every Windows update?
Some updates leave the WebView2 runtime in a half-updated state, or replace it with a version Copilot doesn’t expect. If the error recurs after updates, pin a post-update WebView2 repair into your routine.
Can I use Copilot in the browser instead while fixing this?
Yes — copilot.microsoft.com in Edge gives you full Copilot access without the app shell. Use it as a workaround while you repair the runtime underneath the app.