GitHub has made a Windows 11 ARM64 image with Visual Studio 2026 generally available on standard and larger hosted runners. Teams can select it now with runs-on: windows-11-vs2026-arm, before GitHub gradually migrates the existing image alias in September.

The short answer

QuestionAnswer
Which label should teams test?windows-11-vs2026-arm
When does migration begin?September 21, 2026.
When should it finish?September 30, 2026.
Is the change transparent?Not for builds tied to Visual Studio 2022 or its exact components.

Why an unchanged pipeline may break

A runner image includes the operating system, compiler, SDKs and many preinstalled tools. Even when YAML remains unchanged, replacing Visual Studio 2022 with 2026 can change MSBuild, C++ toolsets, paths and Windows SDK versions.

GitHub explicitly warns that workflows depending on Visual Studio 2022 may fail. Migration is gradual, so two nearby runs following a moving alias may not use exactly the same image generation.

Test before the switch

Temporarily add a parallel job targeting windows-11-vs2026-arm. Build the same configurations, execute native tests and compare artifacts. .NET projects should inspect the SDK actually selected. C++ projects should verify toolsets, dependency architectures and required Visual Studio workloads.

Record environment diagnostics in logs: dotnet --info, msbuild -version, compiler output and installed SDKs. That evidence turns a runner difference into an observable issue.

Remove implicit dependencies

A robust pipeline installs or pins critical tools rather than assuming their presence. global.json can select a .NET SDK, while vcpkg should use an identified commit or baseline. Third-party actions should also use controlled versions.

Pinning the entire managed image is not always possible. The practical goal is to make the build explicit, detect variation early and retain a compatibility matrix during transition.

ARM64 needs native tests

Building on x64 and running through emulation does not cover every difference. An ARM64 runner exposes dependencies without compatible binaries, scripts that assume an architecture and incorrectly packaged native extensions.

For a Windows ARM application, include compilation, installation, startup and native-component tests. Also verify signing and MSIX package creation.

General availability makes Windows ARM64 CI easier, but the automatic alias creates a deadline. Testing the Visual Studio 2026 label before September 21 is cheaper than debugging during migration.