Breaking changes
Windows 11 Arm64 with Visual Studio 2026 is ready to become the default image for the windows-11-arm label in GitHub Actions.
The windows-11-arm label in GitHub Actions will be migrated to use Visual Studio 2026 by default. Customers who need an image without Visual Studio can use the windows-11-arm image label only until the migration is complete; after that, use a self-hosted runner or an alternative supported image that meets your tooling requirements.
Target date
This change will be rolled out over a week beginning September 21, 2026 and will complete by September 30 2026.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Windows 11 Arm64 with Visual Studio 2026 and, starting from August 19, 2026, the image is generally available for all customers.
We have monitored customer feedback to improve the Windows 11 Arm64 with Visual Studio 2026 image stability and are ready to make it the default for the windows-11-arm label.
Possible impact
During this period, workflows using windows-11-arm will gradually switch to the image with Visual Studio 2026 as the default.
If you want to test before the migration, use the windows-11-vs2026-arm label.
Software difference between Windows 11 Arm64 and Windows 11 Arm64 with Visual Studio 2026
| Tool name |
Windows 11 Arm64 |
Windows 11 Arm64 with VS 2026 |
Notes |
| Visual Studio |
Visual Studio Enterprise 2022 (17.14.37516.0) |
Visual Studio Enterprise 2026 (18.8.12023.21) |
Updated to the recent version |
| CMake |
4.4.2 |
4.4.2 |
Supports the Visual Studio 2026 generator |
| Android Command Line Tools |
N/A |
19.0 |
Installed with Visual Studio 2026 |
Platforms affected
Runner images affected
Mitigation ways
To test this image before the migration, use the windows-11-vs2026-arm label in your workflow:
jobs:
jobName:
runs-on: windows-11-vs2026-armPlease report any problems with the new image to this repository.
Breaking changes
Windows 11 Arm64 with Visual Studio 2026 is ready to become the default image for the
windows-11-armlabel in GitHub Actions.The
windows-11-armlabel in GitHub Actions will be migrated to use Visual Studio 2026 by default. Customers who need an image without Visual Studio can use thewindows-11-armimage label only until the migration is complete; after that, use a self-hosted runner or an alternative supported image that meets your tooling requirements.Target date
This change will be rolled out over a week beginning September 21, 2026 and will complete by September 30 2026.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Windows 11 Arm64 with Visual Studio 2026 and, starting from August 19, 2026, the image is generally available for all customers.
We have monitored customer feedback to improve the Windows 11 Arm64 with Visual Studio 2026 image stability and are ready to make it the default for the
windows-11-armlabel.Possible impact
During this period, workflows using
windows-11-armwill gradually switch to the image with Visual Studio 2026 as the default.If you want to test before the migration, use the
windows-11-vs2026-armlabel.Software difference between Windows 11 Arm64 and Windows 11 Arm64 with Visual Studio 2026
Platforms affected
Runner images affected
Mitigation ways
To test this image before the migration, use the
windows-11-vs2026-armlabel in your workflow:Please report any problems with the new image to this repository.