MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: ARM64EC not linking

Open
#5,452 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

When building using the ARM64EC platform using dynamic linking of WebView2, see various LNK2019 errors like the following:

error LNK2019: unresolved external symbol CreateCoreWebView2EnvironmentWithOptions referenced in function #CreateCoreWebView2EnvironmentWithOptions$exit_thunk (EC Symbol)

Traced to "build\Common.targets" in the NuGet package:

<EffectivePlatform Condition="'$(PlatformTarget)' == 'arm64'">arm64</EffectivePlatform>

This, overrides EffectivePlatform back to arm64 and thus the linker uses "build\native\arm64\WebView2Loader.dll.lib" instead of the intended "build\native\x64\WebView2Loader.dll.lib".

According to Visual Studio 2026 macro browser, for the ARM64EC solution platform:

  • $(Platform): ARM64EC
  • $(PlatformArchitecture): ARM64
  • $(PlatformName): ARM64EC
  • $(PlatformTarget): ARM64

Using this information, a simple workaround:

<EffectivePlatform Condition="'$(PlatformTarget)' == 'arm64' And '$(Platform)' != 'arm64ec'">arm64</EffectivePlatform>
Importance

Low. My app is not very affected, or this only affects development.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

142.0.3595.94

SDK Version

1.0.3595.46

Framework

Win32

Operating System

Windows 11

OS Version

26200.7093

Repro steps

Use WebView2 SDK to build Win32 WebView2APISample using the ARM64EC solution platform.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

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.

Research direction

Start with build\Common.targets in the WebView2 SDK package and inspect how EffectivePlatform is selected for ARM64 and ARM64EC. Build the Win32 WebView2APISample using the ARM64EC solution platform, then verify that ARM64EC links against the x64 WebView2Loader library while ARM64 still uses the arm64 library.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, desktop
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.