WebView2 Version 137.0.3296.52 + Surface Pro 11 (Snapdragon)

[davidhawkins78]

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

[davidhawkins78]

Just to update you - I've ripped everything out and upgraded to a system-wide version of 137.0.3296.52 and this is still an issue for me I'm afraid.

[EpiicOtiis]

Currently seeing this across multiple ARM computers. I have seen the issue on both version (137.0.3296.68) as well as version (137.0.3296.62). Teams and outlook (new) do not seem to detect that it is installed.

Have tried going as far as reinstalling the operating system. They will work for a short while until the auto updates kick in and then were dead in the water again.

[davidhawkins78]

@EpiicOtiis thanks for pitching in here and sorry you're suffering as well ...

I held off the re-image exercise as I have seen the same, with one device being my personal (business) device and I'm just not in a position to employ this as a fix, let alone across the estate.

Genuinely happy to be super "hands-on" with the group to find a fix and goes without saying, skilled enough to (I hope) add some value here.

[davidhawkins78]

So I have an update ... I made my Surface Pro 11 work again and I have found the culprit (I think).

We use PatchMyPC which drives automatic software updates in to MS Intune -> Windows Apps and there's just no concept of ARM in there, so it's been pushed x64 updates to my device :(

To make work I had to rip out Edge manually, plus WebView2, re-install the ARM version of Edge, re-installed MicrosoftEdgeWebView2RuntimeInstallerARM64.exe in the user context so the install end up here: C:\Users*userprofile*\AppData\Local\Microsoft\EdgeWebView

Finally, as part of my testing, I'd extracted the fixed CAB file and pointed the registry at this whilst using TeamViewer as my test product for could it detect WebView2 and it worked!

HKCR\CLSID{2C53C23F-F9C0-45F4-81DE-7610DCEBB6E1}\InprocServer32
(Default) = C:\WebView2Fixed\TeamViewer\EmbeddedBrowserWebView.dll

Given it's working, I'm not touching it for the moment, though I do need to point the reg key back where it should be, I'm just worried it'll break again and that's a task for another day!

Happy to share specific steps if anyone would like them, though Intune having no idea about architectures other than x86 and x64 seems to the culprit and pushing updated we just don't want / need.