Windows runners do not show operating system or EC2 details in the “Set up job” output

[Quindrix]

Problem

Windows runners created by this module do not show the Operating System or EC2 sections in the GitHub Actions Set up job output. Equivalent Linux runners show both sections.

We observed this with the multi-runner module on v7.10.1 and GitHub Actions runner v2.336.0.

A Linux runner displays:

Current runner version: '2.336.0'
Runner name: 'ubuntu-2404-x64-ephemeral_i-...'
Runner group name: 'default'
Machine name: 'ip-...'
Operating System
Runner Image
EC2
GITHUB_TOKEN Permissions

The equivalent Windows runner displays:

Current runner version: '2.336.0'
Runner name: 'servercore-2025-x64-ephemeral_i-...'
Runner group name: 'default'
Machine name: 'EC2AMAZ-...'
Runner Image
GITHUB_TOKEN Permissions

The runner operates normally, but the missing information makes it harder to confirm the Windows version, architecture, instance type and availability zone from a workflow log.

Cause

The Windows start script creates .setup_info with only a Runner Image entry:

$jsonBody = @(
    @{
        group='Runner Image'
        detail="AMI id: $ami_id"
    }
)
ConvertTo-Json -InputObject $jsonBody | Set-Content -Path "$pwd\.setup_info"

This is in modules/runners/templates/start-runner.ps1.

In comparison, modules/runners/templates/start-runner.sh adds three entries to .setup_info:

• Operating System
• Runner Image
• EC2

The GitHub Actions runner displays the entries provided in .setup_info, so the missing Windows entries are not generated automatically.

Expected behaviour

Windows and Linux runners should provide equivalent diagnostic information in the Set up job output.

For Windows, .setup_info should include:

• The Windows edition, version and architecture
• The AMI ID
• The EC2 instance type and availability zone

[edersonbrilhante]

@Quindrix Good point. I would even increase the scope to also fix osx. Osx is missing info about AMI id modules/runners/templates/start-runner.sh