Repository navigation
The Windows 2019 Actions runner image will begin deprecation on 2025-06-01 and will be fully unsupported by 2025-06-30 #12045
Description
Breaking changes
We will soon start the deprecation process for Windows 2019. While the image is being deprecated, you may experience longer queue times during peak usage hours. Deprecation will begin on 2025-06-01 and the image will be fully unsupported by 2025-06-30.
To raise awareness of the upcoming removal, we will temporarily fail jobs using windows 2019. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
- June 3 13:00 - 21:00 UTC
- June 10 13:00-21:00 UTC
- June 17 13:00-21:00 UTC
- June 24 13:00-21:00 UTC
For Azure DevOps users, more information can be found in this blog post: https://aka.ms/azdo-windows
Target date
Final retirement date:
2025-06-30
The motivation for the changes
We maintain the latest two stable versions of any given OS version. Windows 2025 is moved to GA on 2025-04-07 so we start deprecating the oldest image at that time.
Possible impact
Workflows using the windows-2019 image label should be updated to windows-2022 or windows-2025.
Platforms affected
- Azure DevOps
- GitHub Actions
Runner images affected
- Ubuntu 20.04
- 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
Mitigation ways
N/A
Activity
replace windows-2019 runner image with windows-2022
wip: update windows runner to 2019 -> 2022
Avasam commentedon May 2, 2025
Hey looks like you got a spam issue.
Anyway, I wanted to ask: Migrating to
windows-2022I noticed that some headers are now missing. Looking at #9701 and #9873 there's a solution offered (which I managed to shrink down to: #9873 (comment) )But there's still a few open questions:
Microsoft.VisualStudio.Component.VC.14.29.16.11exactly, and how did @mikhailkoliada found that's the exact version number that was needed?2.1. If so, what should be the targets?
vs_installerneed to be run twice? Each run takes ~4 minutes. So that makes every run job take an extra ~8 minutes.3.1. Can this be cached between runs ?
Move to vs2022 runner
Move to vs2022 runner
Move to vs2022 runner
Move to vs2022 runner
Update Windows runners
Update Windows runners
Update Windows runners
234 remaining items
Github actions: upgrade windows-2019 to windows-2022 (facebookresearc…
Github actions: upgrade windows-2019 to windows-2022 (facebookresearc…
{Build} CI - Windows Github Infra migration (#202)
{Build} CI - Windows Github Infra migration (#241)
Github actions: upgrade windows-2019 to windows-2022 (facebookresearc…
Upgrade workflows from `windows-2019` to `windows-2022`
packages windows: drop support for windows-2019 (#2409)
Switch to `windows-latest` image
Github actions: upgrade windows-2019 to windows-2022 (#4417)
subir0071 commentedon Jul 2, 2025
Closing this, as Windows-2019 deprecation is completed successfully.
patrycja-bachleda commentedon Jul 16, 2025
Will there be any support for legacy apps that use dotnet 4? windows 2022 does not have dotnet 4 included and the dotnet-setup action also does not support dotnet framework
mlcruz commentedon Jul 24, 2025
Great, i have some windows containers that are fixed on a window-2019 server build using legacy sdks that cannot be updated, and now there is no way i can build projects in github, even as a paying github actions customer.
My life would be so much happier if i never had to deal with a single service microsoft provides
Danielv123 commentedon Oct 26, 2025
Well, darnit - I am trying to setup CI for an application supporting windows xp to windows 11, and the later versions of the windows image no longer provides dotnet 4.0 support, and later versions of dotnet no longer supports windows XP.
JoshMolyneux commentedon Jan 6, 2026
Hi, what's happening with this? Has the 1st Jan deadline been extended again?