windows-2022 runner drive changed from D to C #12386
Description
Description
On June 6 all of my workflows running on GitHub's windows-2022 runners used the D: drive for the RUNNER_TEMP and GITHUB_WORKSPACE. Since Monday morning June 9, the runners have been changed to use the C: drive instead.
As a result of this our workflows have slowed down 40-50%. I see delays of 8-10 seconds every 30 seconds in the log timestamps. There has been a discussion on using D over C in the past -- #8755. What do you recommend I do to get this fixed?
Platforms affected
- Azure DevOps
- GitHub Actions - Standard Runners
- GitHub Actions - Larger Runners
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Image version and build link
June 6:
Current runner version: '2.325.0'
Operating System
Microsoft Windows Server 2022
10.0.20348
Datacenter
Runner Image
Image: windows-2022
Version: 20250602.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20250602.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20250602.1
Runner Image Provisioner
2.0.437.1
June 9:
Current runner version: '2.325.0'
Runner Image Provisioner
Hosted Compute Agent
Version: 20250508.323
Commit: 81b259f29879f73b4213d199e42d8c3465dae986
Build Date: 2025-05-08T19:40:08Z
Operating System
Microsoft Windows Server 2022
10.0.20348
Datacenter
Runner Image
Image: windows-2022
Version: 20250511.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20250511.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20250511.1
Is it regression?
No
Expected behavior
Use the D drive
Actual behavior
Uses C drive
Repro steps
Do an actions/checkout