-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Server 2025 is now available #11228
Comments
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 |
Breaking changes
Windows Server 2025 is now available for GitHub Actions users.
You can use the windows-2025 image label in your YAML to select this image.
GitHub Actions
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: