MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Edge/WebView2 Beta 149.0.4022.8 crashes with c0000005 in ntdll.dll, breaking Teams, Outlook, Widgets

Open
#5,591 10 comments 2 reactions 1 assignee View on GitHub

@ambikakunnath is already working on this.

Since May 20, 2026.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Microsoft Edge Beta/WebView2 Beta 149.0.4022.8 appears unstable on Windows Insider Beta build 26220 / OS component set 26100.7934.

Observed crashes:

  • msedge.exe 149.0.4022.8 crashes with 0xc0000005 in ntdll.dll
  • msedgewebview2.exe 149.0.4022.8 crashes with 0xc0000005 in ntdll.dll
  • WebView2 crashes occur under New Teams, New Outlook, Windows Widgets/WebExperience, and LinkedIn for Windows

Recovery blockers:

  • WebView2 uninstall is blocked: “Browser/WebView is sticky, uninstall not allowed”
  • Stable Evergreen WebView2 installer refuses because a newer version is already installed
  • Edge uninstall is unavailable/greyed out
  • Removing local Beta channel markers did not recover the machine
  • Reimage is required to return to a stable OS/browser/WebView2 baseline
Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

149.0.4022.8

SDK Version

No response

Framework

Other

Operating System

Windows 11

OS Version

No response

Repro steps

After installing the May 14 updates. App Crashes any time you try and use anything edge related.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.