Windows Server 2025 is now available #11228
Comments
shamil-mubarakshin
added
OS: Ubuntu
Announcement
OS: Windows
and removed
OS: Ubuntu
labels
|
Is Windows SDK 10.0.22621 included in the Windows Server 2025 image? This issue says it is not but the README says it does. |
|
WSLv2 on GitHub Actions is now supported. vedantmgoyal9/setup-wsl2#3 Is there any possibility WSLv2 can be enabled by default, instead of WSLv1? |
|
Will you consider adding WMIC Feature on Demand to the For Microsoft Windows Servers, wmic has been deprecated since 2016 and it is not installed by default on Windows Server 2025 (see Features we're no longer developing). Unfortunately there are some npm packages which rely on this deprecated facility and which have so far not followed migration advice from Microsoft. The following issues have been raised for the respective npm modules:
Although it is theoretically possible to execute the following, it is a massively sized package that would be installed, so it is not really a practical workaround: DISM /Online /Add-Capability /CapabilityName:WMIC~~~~ |
|
Is there any possibility of having the ARM64 version in a separate image? (just like |
|
I believe there should be only one default Python, not two, right?
|
@dongle-the-gadget, @janbrasna, thanks for highlighting the typos, updated software difference
@vedantmgoyal9, image rollout with WSLv2 starts this week and will take a few days to complete.
@MikeMcC399, we have no plans on adding this particular deprecated feature to the image. The workaround you mentioned works in runtime via
@ifarbod, there are no current plans on introducing Windows Server ARM64 images. |
|
Any possibility of enabling WSLv2 on Windows 2022 runners as well? |
Many thanks for your response. 🙂 I think this is the right decision not to support this deprecated feature, however I needed to ask you guys before going back to the owners of the packages which need updating. |
|
Well people will not stop using windows 7 I think the past few years without updates made that clear enough. Besides Sandboxie is not only for security, its also for compartmentalization, why junk your OS full of crappy software that will leave garbage behind, if you can instead install it in a sandbox and dispose of it in its entirety once you no longer want to use it. PS: Just leave the old obsolete stuff in as is no updates no nothing, no work, and HDD space costs virtually nothing. |
|
When can we expect |
|
I just created microsoft/msquic#4898 to try to move to using windows-2025 for our BVTs, but it's failing to build kernel mode drivers. Looking at your docs, I believe this is because of these missing components:
What's the status on these? This is blocking us from moving our builds (I will try to just move test execution for now). |
For us, it became available yesterday. |
@sharpjs,
@DavidXanatos, per support policy we keep 2 latest Windows Server images as GA.
@nibanks, could you open a separate issue, providing all the usual details and repro steps for us to check? |
|
I noticed wsl2 was installed in the windows-2025 agent in Azure DevOps pipelines and was hoping I could use it to run the Azure service bus emulator in my integration tests. I tried installing and setting up podman, but I'm getting an error when it tries to create the wsl distro. Do the agents not support nested virtualization? For context, here's the error I'm getting:
|
|
When will Windows 2025 and Ubuntu 24.04 be available in Azure Managed DevOps Pools? |
ghost
mentioned this issue
|
To pickup the question from above: Is there any estimate, when windows-2025 will be available in Azure Managed DevOps Pools? Or is this not even planned? |
Ubuntu 24.04 is now available in MDP as of yesterday. |
|
Do we have a timeline of when this will replace |
|
|
When will it be available on Managed DevOps Pools? Will it also support Gen2 VMs like the new v6 series ? |
|
Also in Managed DevOps pool it doesn't show the image sizes, yet they define the disk size which is then used for pricing in Managed DevopsPool - is there a way to see the size of the image? So in terms of pricing and performance, would you all here agree that this applies: Standard HDD S4 32GB £1.18 (has no 16GB size) 500IOPS, 60MB/s So really in managed DevOps Pool for Performance I should select Standard SSD as a disk if I use the provided runner images, right? Normally the requirement for Win 2022 Server is at least 32GB, so normally I would choose at least 64GB disk image, so if Microsoft cut things down really to a bare minimum than this would be great but would be nice to know where to see it so I can get my costs for a Managed DevOps Pool clear. |
|
Would you consider adding RabbitMq Message broker to the runner ? |
|
Can we have a minimal version of the Windows Server 2025 where only what is by default in the Windows Server 2025 ISO file exists and none of the 3rd party stuff is there? I don't want to expose my build process to 3rd party programs installed on the runner. I always install my requirements and dependencies through Winget. A default Windows Server 2025 runner would be really useful, pretty much just like how you get a pure Windows Server 2025 VM on Azure. Offering such runner costs less than what is available now since it has less maintenance. |
|
Now that WSL2 is the default Linux subsystem, will it finally be possible to run Linux containers using Docker, or to switch to Linux containers in Docker? This has been a frustrating limitation of the current Windows Server 2022-based image, which has forced DevOps engineers to build hacky integration test pipelines just to run integration tests relying on Linux-based containers like MySQL. |
|
Can the |
I have this step in my workflow that takes care of it - name: Updating Winget
shell: pwsh
run: |
Write-Host -Object "The version of the pre-installed Winget on the Runner:"
Write-Host -Object (winget --version)
# Retrieve the latest Winget release information
$WingetReleases = Invoke-RestMethod -Uri 'https://api.github.com/repos/microsoft/winget-cli/releases'
$LatestRelease = $WingetReleases | Select-Object -First 1
# Direct links to the latest Winget release assets
[string]$WingetURL = $LatestRelease.assets.browser_download_url | Where-Object -FilterScript { $_.EndsWith('.msixbundle') } | Select-Object -First 1
[string]$WingetLicense = $LatestRelease.assets.browser_download_url | Where-Object -FilterScript { $_.EndsWith('License1.xml') } | Select-Object -First 1
[string]$LatestWingetReleaseDependenciesZipURL = $LatestRelease.assets.browser_download_url | Where-Object -FilterScript { $_.EndsWith('DesktopAppInstaller_Dependencies.zip') } | Select-Object -First 1
[hashtable]$Downloads = @{
# 'Winget.msixbundle' = 'https://aka.ms/getwinget' This is updated slower than the GitHub release
'DesktopAppInstaller_Dependencies.zip' = $LatestWingetReleaseDependenciesZipURL
'Winget.msixbundle' = $WingetURL
'License1.xml' = $WingetLicense
}
$Downloads.GetEnumerator() | ForEach-Object -Parallel {
Invoke-RestMethod -Uri $_.Value -OutFile $_.Key
}
Expand-Archive -Path 'DesktopAppInstaller_Dependencies.zip' -DestinationPath .\ -Force
# Get the paths to all of the dependencies
[string[]]$DependencyPaths = (Get-ChildItem -Path .\x64 -Filter '*.appx' -File -Force).FullName
# Required to update the Winget
Stop-Process -Name WindowsTerminal -Force -ErrorAction Ignore
Add-AppxProvisionedPackage -Online -PackagePath 'Winget.msixbundle' -DependencyPackagePath $DependencyPaths -LicensePath 'License1.xml'
Add-AppPackage -Path 'Winget.msixbundle' -DependencyPath "$($DependencyPaths[0])", "$($DependencyPaths[1])" -ForceTargetApplicationShutdown -ForceUpdateFromAnyVersion |
Even though I would be just as excited about this change as you are, I’m afraid it’s not gonna happen because of the difference between Docker Desktop (that is capable of running Linux containers using WSL2) and Docker Engine (that only supports Windows containers natively and apparently is installed on the runner).
Since I’m struggling with a similar issue right now, do you have any examples or workarounds maybe?.. |
You can use docker inside a WSL distro with the help of https://github.com/marketplace/actions/setup-wsl |
Windows Server 2019 has been scheduled for deprecation and will be removed by end of June.¹ I moved the build job to the next oldest version, Windows Server 2022. Windows Server 2025 was released in December 2024,² so test on it. ¹ <actions/runner-images#12045> ² <actions/runner-images#11228>
Windows Server 2019 has been scheduled for deprecation and will be removed by end of June.¹ I moved the build job to the next oldest version, Windows Server 2022. Windows Server 2025 was released in December 2024,² so test on it. ¹ <actions/runner-images#12045> ² <actions/runner-images#11228>
and others
Uh oh!
There was an error while loading. Please reload this page.
Breaking changes
Windows Server 2025 is now available for GitHub Actions and Azure DevOps users.
You can use the windows-2025 image label in your YAML to select this image.
GitHub Actions
Azure DevOps
The image is marked as "beta" for now. It means some software can be unstable on the new platform. Also, there could be queueing issues as the capacity will be balanced only throughout the next weeks.
Please report any problems with the new image to this repository.
Platforms affected
Runner images affected
Software difference between Windows Server 2022 and Windows Server 2025
Miscellaneous:
The text was updated successfully, but these errors were encountered: