Git and choco on Windows

[liquidcarbon]

Description

Per windows-latest readme, git and choco are available on Win runners.

But these workflows are failing:

• git clone (example)
• choco install git (example)

What am I doing wrong? What might be missing from documentation?

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 12
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022

Image version and build link

Runner Image
  Image: windows-2022
  Version: 20241021.1.0
  Included Software: https://github.com/actions/runner-images/blob/win22/20241021.1/images/windows/Windows2022-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F2024[10](https://github.com/liquidcarbon/puppy/actions/runs/11801850154/job/32876134788#step:1:11)21.1

Is it regression?

unknown

Expected behavior

should work?

Actual behavior

not working

Repro steps

choco install git on windows runner

[vidyasagarnimmagaddi]

Hi @liquidcarbon ,Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating

[hemanthmanga]

Hi @liquidcarbon, Your patience is appreciated. Kindly update your workflow file, Please look into this https://github.com/hemanthmanga/puppy/actions/runs/12159242869/job/33908947994, Hope it will resolve your issue.Thanks

[liquidcarbon]

Thank you for looking into this.
So it's just a matter of adding all the needed tools to PATH at the outset?
PATH: "C:\\Users\\runneradmin\\.pixi\\bin;C:\\ProgramData\\chocolatey\\bin;C:\\Program Files\\Git\\bin"

[hemanthmanga]

In some instances, you may need to include the path. We are closing this issue. Thank you.

[shamil-mubarakshin]

Hey @liquidcarbon,
Runners come with predefined PATH variable, which includes directories for most tools.
It looks like you are manipulating machine level $env:PATH variable in your workflow. Unless it is your intention to completely overwrite PATH, appending might be preferable. You could you use something like below to make directories available in subsequent actions:

- name: append env
  run: |
    "c:\temp" | Out-File -FilePath "$env:GITHUB_PATH" -Append

You could also check if the following would do the job:

- name: append env
  run: |
    $currentPath = [System.Environment]::GetEnvironmentVariable("PATH", "Machine")
    $newPath ="c:\temp" + ';' + $currentPath
    [Environment]::SetEnvironmentVariable("PATH", $newPath, "Machine")

[liquidcarbon]

@shamil-mubarakshin sounds like the right thing to do would've been appending to PATH, but instead I initially overwrote it: PATH: C:\Users\runneradmin\.pixi\bin . Thank you!