Microsoft Copilot Crashes Immediately Upon Launching

Hi Tim Chesnut,

Since the previous guidance suggested trying Copilot from a new Windows user profile, here are the step-by-step instructions in case you’d like to give that a try:

1. Go to Settings > Accounts > Family & other users.
2. Under Other users, select Add someone else to this PC.
3. Click I don’t have this person’s sign-in information.
4. Select Add a user without a Microsoft account.
5. Enter a username and password, then click Next.
6. Once the account is created, sign out of your current account and sign in to the new one.
7. Before signing into any Microsoft apps or syncing settings, try launching Copilot to see if the issue still occurs.

If Copilot opens normally in the new profile, it could point to something in the original user profile affecting the app.

Please let me know how it goes.

If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

You're already done most of the correct troubleshooting, so the issue is likely not a basic install or dependency problem—it looks more like a broken runtime or profile-level corruption specific to Copilot/Edge components.

A few targeted things I’d suggest (since generic fixes didn’t work):

1. Check Edge version alignment Copilot relies heavily on Edge + WebView2. Make sure Microsoft Edge is fully updated—not just WebView2. A mismatch can cause silent crashes like this.

Clear WebView2 user data manually Even after reinstall, corrupted runtime data can persist:

Go to: C:\Users\<YourUser>\AppData\Local\Microsoft\EdgeWebView

Delete the entire folder

Relaunch Copilot

Try a new Windows user profile Since there are no logs, this strongly suggests profile corruption:

Create a new local user

Launch Copilot there If it works → your main profile is the issue

Check GPU / hardware acceleration Some recent builds crash silently due to GPU issues:

Disable hardware acceleration system-wide (or via Edge flags if accessible)

Update or roll back graphics drivers

Roll back Copilot version (important) Since it worked on 9-Apr, this may be a bad update:

Use an older version if available (or wait for patch)

Many users see this exact behavior with broken rollout builds

Force reinstall WebView2 Evergreen Runtime (clean) Uninstall ALL WebView2 entries (including per-user installs), then reinstall fresh from Microsoft’s official installer—not Store.

Given there's zero Event Viewer trace, this is almost certainly:

runtime crash before logging (WebView2/Edge issue), or

user profile corruption

If it works in a new user account, don’t waste time—just migrate.

If not, it’s very likely a bad Copilot build, and waiting for an update is the practical fix.

Let me know if you want a quick script to fully clean WebView2 + Copilot residues—I can give a proper deep-clean sequence.You're already done most of the correct troubleshooting, so the issue is likely not a basic install or dependency problem—it looks more like a broken runtime or profile-level corruption specific to Copilot/Edge components.

A few targeted things I’d suggest (since generic fixes didn’t work):

Check Edge version alignment
Copilot relies heavily on Edge + WebView2. Make sure Microsoft Edge is fully updated—not just WebView2. A mismatch can cause silent crashes like this.

Clear WebView2 user data manually
Even after reinstall, corrupted runtime data can persist:

Go to:
C:\Users\<YourUser>\AppData\Local\Microsoft\EdgeWebView

Delete the entire folder

Relaunch Copilot

Try a new Windows user profile
Since there are no logs, this strongly suggests profile corruption:

Create a new local user

Launch Copilot there
If it works → your main profile is the issue

Check GPU / hardware acceleration
Some recent builds crash silently due to GPU issues:

Disable hardware acceleration system-wide (or via Edge flags if accessible)

Update or roll back graphics drivers

Roll back Copilot version (important)
Since it worked on 9-Apr, this may be a bad update:

Use an older version if available (or wait for patch)

Many users see this exact behavior with broken rollout builds

Force reinstall WebView2 Evergreen Runtime (clean)
Uninstall ALL WebView2 entries (including per-user installs), then reinstall fresh from Microsoft’s official installer—not Store.

Given there's zero Event Viewer trace, this is almost certainly:

runtime crash before logging (WebView2/Edge issue), or

user profile corruption

If it works in a new user account, don’t waste time—just migrate.

If not, it’s very likely a bad Copilot build, and waiting for an update is the practical fix.

Let me know if you want a quick script to fully clean WebView2 + Copilot residues—I can give a proper deep-clean sequence.