MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Webview2 doesn't work after last Edge update

Open
#5,476 6 comments 0 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since Jan 5, 2026.

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

Description

What happened?

I am finding a bug with WebView2 and Edge. And I'm not the only one. There is another user who started the help ticket.
BUG Webwies2 search works outside of App container

This person knows more than me. I just know what works and doesn't work. I'm getting tired of not being able to play my games.

I found 3 WebView2 files on my computer - 3/21/24, 11/11/25 and 12/9/25. And I have not found any file labelled WebView runtime

Edge 143.0.3650.96 was updated on 12/19/25 (released 12/18/25).

On Thursday 12/18 everything worked just fine when I cut my laptop off to go to bed.

On Friday morning 12/19, Edge downloaded new update. After that, my widgets don't work, WhatsApp doesn't work right, and I can't get any of my G5 games to work.

I don't think the WebView2 is broken, I think the problems are caused by the Edge update. But I don't know why or how. There must be some code in Edge that causes these problems.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

Did not find one

SDK Version

I don't know how to do this

Framework

Other

Operating System

Windows 11

OS Version

25H2

Repro steps

I don't know any more than what's written above. Before I retired, I could tell what was wrong, but not how to fix it. And things have changed in the last 10 years.

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.