MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]:Edge update not running as native ARM64 process after recent updates

Open
#5,075 23 comments 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

This is my first time reporting here, but I will do my best to make sure there is appropriate data. In the current version of Edge, 132.0.2957.127, as well as the previous production build my system is not running the ARM64 version of Edge, it is running the x64 version. In Teams and Outlook when this happens I get an error that says WebView is not installed, when it tries to install it just enters and endless loop. After using Procmon to find out what is going on I found that teams and outlook were trying to load the DLL in C:\Program Files (x86)\Microsoft\Edge\Application$version\EBWebView\arm64\EmbeddedBrowserWebView.dll, which was missing. In order to resolve the problem, I downloaded the redistributable webview components and manually create the ARM64 folder and put the ARM64 dll from the cab into the folder. I previously had this problem with the prod build from the end of November and now the last two builds have had the issue. My system performance seems to be impacted as well, primarily in Edge, Teams, and Outlook.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

132.0.2957.127

SDK Version

132.0.2957.127

Framework

Other

Operating System

Windows 11

OS Version

10.0.26100

Repro steps

Install current prod version of edge/webview on Windows 11 ARM system.

Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

Regression in newer Runtime

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.