MicrosoftEdge / MicrosoftEdge/WebView2Feedback

WebView2 Version 137.0.3296.52 + Surface Pro 11 (Snapdragon)

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

@KomalPrasadMSPM is already working on this.

Since Jun 3, 2025.

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

Description

What happened?

So this might be nothing to do with the ARM element of this Surface Pro, though since version 136 and now 137.0.3296.52 I cannot get Webview2 to run. Teams is the main culprit stating, "We can't find a required component to run Teams. Download and install it, and then try opening Teams again." though Outlook (new) and a few other apps that use this cannot detect it's installed.

I'm running a fully patched Windows 11 image (24H2 build 26100.4061), Edge 137 too.

I've tried just about every permutation of running MicrosoftEdgeWebView2RuntimeInstallerARM64.exe as a "normal" user, plus "admin" elevated for a system-wide install to C:\Program Files (x86)\Microsoft\EdgeWebView versus user profile, then MicrosoftEdgeWebview2Setup.exe having fully flushed the file system, registry and rebooted after removal before a fresh install.

I did notice using MicrosoftEdgeWebView2RuntimeInstallerARM64.exe seems to put MicrosoftEdgeWebview_X64_137.0.3296.52.exe in this location:

C:\Program Files (x86)\Microsoft\EdgeUpdate\Download{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\137.0.3296.52

Whereas using MicrosoftEdgeWebview2Setup.exe puts MicrosoftEdge_ARM64_137.0.3296.52.exe

C:\Users*profile*\AppData\Local\Microsoft\EdgeUpdate\Download{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\137.0.3296.52

I've honestly tried just about everything I can to make this work and just had no luck ...

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

137.0.3296.52

SDK Version

N/A

Framework

Other

Operating System

Windows 11

OS Version

26100.4061

Repro steps

See main comments

Repros in Edge Browser

Yes, issue can be reproduced 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.