Automate Windows on Arm builds with GitHub Arm-hosted runners
Introduction
Introduction to GitHub Arm-hosted Runners
Automate the Build of Windows Applications
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  20 min
Last updated:  29 Jul 2026
Skill level:
  Introductory
Reading time:
  20 min
Last updated:
  29 Jul 2026
Author:Pareena Verma, Arm
Arm IP:Cortex-A
Tags: CI-CD Windows GitHub Visual Studio MSBuild Arm Performance Libraries
Author:
  • Pareena Verma, Arm
Arm IP:
Cortex-A
Tags:
CI-CD Windows GitHub Visual Studio MSBuild Arm Performance Libraries

Who is this for?

This introductory tutorial is for software developers looking to automate Windows application builds on Arm architecture using GitHub Actions.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Describe GitHub Arm-hosted Windows runners.
  • Configure workflows to run on Arm-hosted runners.
  • Automate Windows application builds with GitHub Actions.

Prerequisites

Before starting, you'll need the following prerequisites:

  • A GitHub account
  • Familiarity with GitHub Actions

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll use GitHub-hosted Arm Windows runners to automate a Windows application build with GitHub Actions. You’ll configure a workflow and choose Visual Studio or MSBuild for the rotating 3D cube sample. You’ll then trigger the job, inspect logs, and verify the build outputs from an Arm-hosted Windows environment.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I target an Arm-hosted Windows runner in my workflow?
Configure the job to run on a GitHub Arm-hosted Windows runner. Update the workflow so the job selects the Arm-hosted Windows environment instead of a different runner type.
How do I know the job actually ran on an Arm-hosted Windows runner?
Open the workflow run and check the job details, which list the runner that executed the job. The logs and summary page identify the runner environment so you can verify it used an Arm-hosted Windows runner.
Which build tool should I configure, Visual Studio or MSBuild?
Use the toolchain that matches the project’s existing build files. To choose the correct build step, follow the guidance for the rotating 3D cube application referenced in the Learning Path.
Where can I find the sample application and detailed build steps?
The Optimize Windows applications using Arm Performance Libraries Learning Path provides the rotating 3D cube application and its build instructions. Use that resource for detailed build steps.
What result should I expect after a successful workflow run?
The workflow shows a successful job status and the logs indicate a completed build. The run contains the Windows build outputs for the sample application. Any configured artifacts appear on the run’s summary page.
Next