Skip to content

(Public Beta) Windows Server 2022 with Visual Studio 2022 is now available #3949

@maxim-lobanov

Description

@maxim-lobanov

Windows Server 2022 availability 🚀

Hello everyone!

We are happy to announce that Windows Server 2022 is available for GitHub Actions and Azure DevOps users 🥳
You can use windows-2022 image label in your YAML to select this image.

GitHub Actions

jobs:
  jobName:
    runs-on: windows-2022

Azure DevOps

jobs:
- job: jobName
  pool:
    vmImage: 'windows-2022'

"Beta" status

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.
Known issues:

  • Some build software is not compatible with Visual Studio 2022 yet (For example: Bazel)
  • Some Azure DevOps tasks don't work on the new platform properly yet: VSBuild, MSBuild, UsePython (PyPy only)

Please report any problems with the new image to this repository.
Any issues related to Azure DevOps tasks should be reported to https://github.com/microsoft/azure-pipelines-tasks.

Software differences

The full documentation of Windows Server 2022 image can be found in image README.
The software set is different between Windows Server 2019 and 2022. We have deprecated some legacy software with low usage and temporarily disabled software that is not supported on the new platform yet. Also, for tools with multiple installed versions we have reconsidered the list of versions based on usage.

Please find differences in the table below:

Tool name Windows 2019 Windows 2022 Notes
Windows Server 2019 (10.0.17763 Build 2061) 2022 (10.0.20348 Build 112)
Visual Studio 2019 (16.10.31515.178)
Workloads: recommended + custom + wix components
2022 Preview (17.0.31521.260)
Workloads: recommended set
Our policy is installing one VS version per platform. On Windows Server 2022, we install only VS 2022 (it is in Preview for now but will be released in future).
If your use-case requires using VS 2019, continue using Windows Server 2019 image. We don't have plans to deprecate it in near future.
Python Default version: 3.7.x
Architectures: x64 & x86
Pre-cached versions: 2.7, 3.5, 3.6, 3.7, 3.8, 3.9
Default version: 3.9.x
Architectures: x64
Pre-cached versions: 3.7, 3.8, 3.9
On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users
PyPy 2.7, 3.6, 3.7 2.7, 3.7 Version 3.6 is officially deprecated in favor of 3.7 and is not updated anymore.
Ruby Default version: 2.5.x
Pre-cached versions: 2.4, 2.5, 2.6, 2.7, 3.0
Default version: 3.0.x
Pre-cached versions: 2.7, 3.0
On GitHub Actions, ruby/setup-ruby can install any version on-flight so this change doesn't impact users
Go Default version: 1.15.x
Pre-cached versions: 1.13, 1.14, 1.15, 1.16
Default version: 1.16.x
Pre-cached versions: 1.15, 1.16
If your use-case requires using any of these versions, consider using tasks to install Go on-flight:
- actions/setup-go (GitHub Actions)
- Go Tool Installer (Azure DevOps)
Java Default version: 8
Pre-installed versions: 8, 11, 13
Default version: 8
Pre-installed versions: 8, 11
Our policy is pre-installing only LTS versions of Java. if your use-case requires using non-LTS Java version, please consider using tasks to install it on-flight:
- actions/setup-java (GitHub Actions)
- Java Tool Installer (Azure DevOps)
Android Build-tools: >= 19.x
Platforms: >= 19.x
CMake: 3.10.2, 3.18.1
Google APIs: 21, 22, 23, 24
NDK: 21, 22
Build-tools: >= 27.x
Platforms: >= 27.x
CMake: 3.18.1
Google APIs: -
NDK: 21, 22
.NET Core SDK 2.1, 3.1, 5.0 3.1, 5.0 .NET Core 2.1 End Of Support is scheduled on August 21, 2021.
Please consider using tasks to install any version on-flight:
- actions/setup-dotnet (GitHub Actions)
- Use .NET Core (Azure DevOps)
Az modules Installed: 6.1.0
Zipped: 1.0.0, 1.6.0, 2.3.2, 2.6.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.7.0, 5.5.0, 5.9.0, 6.1.0
Installed: 6.1.0
Zipped: -
If your use-case requires using any of these versions, consider using tasks to install Az modules on-flight:
- azure-powershell-action (GitHub Actions)
- Azure PowerShell (Azure DevOps)
MSYS2 A lot of pre-installed msys packages Only pure MSYS2 is installed. No additional packages On Windows Server 2016 and 2019 we had a lot of pre-installed MSYS2 packages. We had a long discussion about "pre-installing them" vs "installing in runtime and caching". Our recommendation is using official setup-msys2 action to install packages on-flight and cache them.

The following software were not installed on Windows Server 2022 images by default: Miniconda, Google Cloud SDK, InnoSetup, NSIS, Perl, sbt, Cloud Foundry CLI, BizTalk Server and Client, WebPlatformInstaller, Windows Driver Kit

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions