runner-images icon indicating copy to clipboard operation
runner-images copied to clipboard
verified publisher icon actions

[Windows Server 2025] image will no longer have D:/ drive accessible to users from 2025-07-14

Open vidyasagarnimmagaddi opened this issue 6 months ago • 5 comments

Breaking changes

We are writing to inform you that as of 2025-07-14 all GitHub-hosted runners in public repositories using the Windows Server 2025 image will no longer have a D:/ drive accessible to users.

This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Target date

Image deployment will start on 2025-07-07 and will take 2-3 days

The motivation for the changes

  • Currently these hosted runners have both a C:/ and a D:/ drive. After the change only the C:/ drive will be accessible to Actions users. Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

  • This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Possible impact

Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

Platforms affected

  • [ ] Azure DevOps
  • [x] GitHub Actions

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
  • [x] Windows Server 2025

Mitigation ways

n/a

vidyasagarnimmagaddi avatar Jun 18 '25 09:06 vidyasagarnimmagaddi

Can we expect a similar change to Azure DevOps in the future? The notice in the latest release notes https://github.com/actions/runner-images/releases/tag/win25/20250617.1 is malformed

Image

Frulfump avatar Jun 19 '25 09:06 Frulfump

Is the C: drive going to be faster than it is now? I rely on D: because C: is too slow.

lmb avatar Jun 25 '25 09:06 lmb

Breaking changes

We are writing to inform you that as of 2025-07-14 all GitHub-hosted runners in public repositories using the Windows Server 2025 image will no longer have a D:/ drive accessible to users.

This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Target date

Image deployment will start on 2025-07-07 and will take 2-3 days

The motivation for the changes

* Currently these hosted runners have both a `C:/` and a `D:/ drive`. After the change only the `C:/ drive` will be accessible to Actions users. Users that are currently accessing the `D:/ drive` during their workflow runs may experience breakages.

* This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Possible impact

Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

Platforms affected

* [ ]  Azure DevOps[x]  GitHub Actions

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[x]  Windows Server 2025

Mitigation ways

n/a

/

signal-coder avatar Jun 25 '25 20:06 signal-coder

What will this change mean for disk space available to the job? Currently D: has 147GB of free space available, while C: only has 29GB.

lazka avatar Jun 27 '25 10:06 lazka

Why not use Add-PartitionAccessPath -DiskNumber <disknumber> -PartitionNumber <partitionnumber> -AccessPath $mount_path to mount some folder on C:\ as D:\ to maintain backward compatibility?

briansmith avatar Jun 27 '25 16:06 briansmith

Breaking changes

We are writing to inform you that as of 2025-07-14 all GitHub-hosted runners in public repositories using the Windows Server 2025 image will no longer have a D:/ drive accessible to users.

This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Target date

Image deployment will start on 2025-07-07 and will take 2-3 days

The motivation for the changes

  • Currently these hosted runners have both a C:/ and a D:/ drive. After the change only the C:/ drive will be accessible to Actions users. Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

  • This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Possible impact

Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

Platforms affected

  • [ ] Azure DevOps
  • [x] GitHub Actions

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
  • [x] Windows Server 2025

Mitigation ways

n/a

Art39print avatar Jul 01 '25 02:07 Art39print

Критические изменения

Мы пишем, чтобы сообщить вам, что с 14.07.2025 все средства выполнения, размещенные на GitHub в публичных репозиториях, использующих образ, больше не будут иметь диска D:/, доступного пользователям.Windows Server 2025

Это изменение связано с причинами производительности. Для того, чтобы сделать наши бегуны более производительными, мы меняем способ управления дисками на них. Кроме того, это изменение улучшит время запуска для наших бегунов.

Целевая дата

Развертывание образа начнется 2025-07-07 и займет 2-3 дня

Мотивация изменений

  • В настоящее время эти размещенные средства выполнения тестов имеют как , так и . После изменения пользователям Actions будут доступны только те пользователи. У пользователей, которые в данный момент обращаются к рабочему процессу во время выполнения рабочего процесса, могут возникнуть сбои.C:/``D:/ drive``C:/ drive``D:/ drive
  • Это изменение связано с причинами производительности. Для того, чтобы сделать наши бегуны более производительными, мы меняем способ управления дисками на них. Кроме того, это изменение улучшит время запуска для наших бегунов.

Возможные последствия

У пользователей, которые в данный момент обращаются к рабочему процессу во время выполнения рабочего процесса, могут возникнуть сбои.D:/ drive

Затронутые платформы

  • [ ] Azure DevOps[x] Действия GitHub

Затронутые изображения бегунов

  • [ ] 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[x] Windows Server 2025

Способы устранения рисков

н/д

signal-coder avatar Jul 04 '25 22:07 signal-coder

e latest re

As of now we do not have any plan to implement this in ADO.

subir0071 avatar Jul 14 '25 19:07 subir0071

Closing this announcement as the implementation is completed successfully. Thanks.

subir0071 avatar Jul 16 '25 18:07 subir0071

What will this change mean for disk space available to the job? Currently D: has 147GB of free space available, while C: only has 29GB.

I filed a dedicated follow-up issue in https://github.com/actions/runner-images/issues/12609, because this is causing build failures for us due to significantly less available disk space.

jieyouxu avatar Jul 17 '25 13:07 jieyouxu

Breaking changes

We are writing to inform you that as of 2025-07-14 all GitHub-hosted runners in public repositories using the Windows Server 2025 image will no longer have a D:/ drive accessible to users.

This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Target date

Image deployment will start on 2025-07-07 and will take 2-3 days

The motivation for the changes

  • Currently these hosted runners have both a C:/ and a D:/ drive. After the change only the C:/ drive will be accessible to Actions users. Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.
  • This change is due to performance reasons. In order to make our runners more performant, the way we manage the disks on our runners is changing. In addition this change will improve startup times for our runners.

Possible impact

Users that are currently accessing the D:/ drive during their workflow runs may experience breakages.

Platforms affected

  • [x] Azure DevOps[x] GitHub Actions

Runner images affected

  • [x] 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[x] Windows Server 2025

Mitigation ways

n/a

r1hr6pr1hr6p avatar Jul 19 '25 09:07 r1hr6pr1hr6p