Skip to content
runnerhut
Start building

Runners

Windows GitHub Actions runners

Dedicated Windows Server 2022 and 2025 runners with Visual Studio build tools preinstalled and a persistent NuGet and MSBuild cache.

Specifications

OS
Windows Server 2022, 2025
vCPU
4 – 32, dedicated
Memory
4 GB per vCPU
Visual Studio
2022 Build Tools, 2025 Build Tools
Price
50% below GitHub-hosted

Runner labels

  • runnerhut-4vcpu-windows-2022
  • runnerhut-8vcpu-windows-2022
  • runnerhut-16vcpu-windows-2025

Windows runners are the slowest to start anywhere in CI — the OS itself takes longer to boot, Defender scans everything the checkout writes, and NuGet restore is chatty. Most of that is fixable.

The three fixes that matter

  1. Exclude the workspace from Defender real-time scanning — often 30–40% off a checkout-heavy job
  2. Persist the NuGet package cache between runs rather than restoring from the network
  3. Use the MSBuild node reuse and incremental output cache instead of clean builds
yaml
jobs:
  build:
    runs-on: runnerhut-8vcpu-windows-2022
    steps:
      - uses: actions/checkout@v4
      - run: dotnet restore --locked-mode
      - run: dotnet build -c Release --no-restore

Your next build could be twice as fast, at half the price

Start free. Migrating away is the same one line, and we publish that diff too.

Start buildingSee pricing

Related

Visual Studio images on Windows runnersWhich Visual Studio workloads and SDK components are preinstalled on runnerhut Windows runners, and how to add your own.Nested virtualization on runnersKVM and Hyper-V exposed inside the runner for Android emulators, Firecracker microVMs and VM-based integration tests.