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

[DevRenJD]

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

[ParadoxZero]

Please share logs/ info to facilitate debugging - https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/diagnostics/install.md

[CyberSkyler]

@DevRenvio Thank you for posting your workaround. This has been affecting us for a month or so now and I've tried every solution under the sun and nothing worked except this. I also found that the arm64 folder was missing but once that was created and the DLL added, our Outlook issue was resolved.

[DevRenJD]

I have attached the files, CyberSkyler, i am glad you were able to get the solution. It is a bit annoying if there are frequent updates to Edge, but sometimes it seems an upgrade fixes the problem and all of the sudden i am using the ARM verison.

The logs are attached.

EdgeFiles.txt
edgeinstallersystemTem.msedge_installer.log
EdgeRegistryMachine.txt
EdgeRegistryUser.txt
MicrosoftEdgeUpdate.log
msedge_installer.log

[dhveerap]

@DevRenvio Could you please help me understand whether the issue is that x64 binary is being loaded instead of an arm64 binary, or if it's trying to load an arm64 binary but it isn't available?

Could you also share the Runtime Version in which it got regressed?

[DevRenJD]

@dhveerap The issue seems to be that ARM64 versions of Teams and Outlook (new) install and update without issue. Then some updates to Edge get installed that push the Edge x64 version, not the ARM64 version. This last time it happened for two releases in a row, those versions were 132.0.2957.127 and 132.0.2957.140. At the end of November/early December it also happened the first time, but I do not have that build number. It was at this time that I used process monitor on Teams or Outlook, sorry I don't remember which, to see that it was attempting to load the ARM64 dll, but it was missing from the installed paths for Webview and Edge.

[dhveerap]

@DevRenvio Thanks for the explanation.
Please confirm that the logs shared by you are before applying the mitigation (of downloading and manually creating ARM64 folder)? If not, could you give us the logs without any mitigation in place.

[DevRenJD]

Some of the logs seem to have the full history, going back to before the fix was applied, but they are from after I migrated the .dll's. I do not have an environment that I can revert back to earlier versions of edge. Unfortunately, this is my primary workstation.

[DevRenJD]

@dhveerap just happened again with the latest version of Edge. I dumped the files here before fixing. Also here is a screenshot, whenever I get an edge update this is what the about page shows, not the Edge x64 not Edge arm.

EdgeRegistryUser.txt
MicrosoftEdgeUpdate_LocalAppData.log
MicrosoftEdgeUpdate.log
msedge_installer.log
EdgeFiles.txt
EdgeRegistryMachine.txt

[dhveerap]

Tracking internally - https://microsoft.visualstudio.com/Edge/_workitems/edit/56105699

[quarin28]

I've found this thread while looking for a solution to this exact issue. I can confirm I'm on a Surface Laptop 7 ARM, and have this exact issue. Also confirming the updates in November/December caused the same problem. I've got a ticket open with MS support as well - TrackingID#2502120040013173

After finding this thread, I was able to validate the ARM64 folder and required dll was missing from the EBWebView folder.

I've resolved the problem by (somehow) getting edge in a state where it allowed me to revert back to the ARM version.

[DevRenJD]

Just to keep records. Version 134.0.3124.51 just installed on my system reverted back to the appropriate arm64 version.

[jaumealg]

I do not know if its related but version 134.0.3124.68 crashed our Drive and Lenovo Vantage in our ARM
LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
How were you able to revert the situation?

[DevRenJD]

@jaumealg interestingly enough my computer is now running Edge 134.0.3124.72 and Webview 134.0.3124.68. Generally speaking, these have always been equal. The 134.0.3124.68 version of webview is causing errors, so the solution is the same, manually download the ARM64 version of webview, create a "arm64" folder under ${env:ProgramFiles(x86)}\Microsoft\EdgeWebView\Application$Version\EBWebView. Then manually copy the EmbeddedBrowserWebView.dll to that folder from the .cab download available here:
https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH

The error in Edge, in my experience, fixes itself. Even though it says checking for updates is broken, it is still able to install updates when they come out.

@ambikakunnath / @soumamazu is there any update to the fix for this? It is extremely frustrating and limits us from deploying new ARM based systems.

[jaumealg]

Thank you very much. It worked we have to check all folders down c:\progam files(x86)\Microsoft and fill the missing ones
we have Edge, EdgeCore, EdgeUpdate and EdgeWebView

[DevRenJD]

To continue with tracking, version 134.0.3124.83 has the same problem. I would also like to note that my computer is significantly slower in Teams, Outlook, and Edge when the x64 version runs. Even after the 'fix' to allow them to work, it is painful.

[quarin28]

Updating that I've had the same issue again after running fine for a month. Edge 134.0.3124.93 has again installed as the x64 emulated version.

[ryanreid22]

There is a preview version 135.0.3179.41 that does install the arm version. It does NOT install the WebView, that is still on 134.0.3124.93.

I am running Global Protect VPN and it fails with WebView 134.0.3124.93 (works with 134.0.3124.72). To fix this, I have manually copied the 134.0.3124.72 folder and changed the registry to claim that the version is 72.

[DevRenJD]

@ryanreid22 and @quarin28 are either of you using software to automatically push updates? I noticed that we had an Intune policy that was pushing Edge x64 and WebView x64 updates through our PatchMyPC product and Intune. I filtered the ARM systems and am waiting for updates to see what happens.