Update Visual Studio 2022 to 17.13

[0x5bfa]

Tool name

Visual Studio 2022

Tool license

https://visualstudio.microsoft.com/license-terms/vs2022-ga-proenterprise

Add or update?

• Add
• Update

Desired version

17.13

Approximate size

No response

Brief description of tool

This is the latest Visual Studio, which has .NET 9.0.200 SDK.

URL for tool's homepage

No response

Provide a basic test case to validate the tool's functionality.

Platforms where you need the tool

• Azure DevOps
• GitHub Actions

Runner images where you need the tool

• 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

Can this tool be installed during the build?

Tool installation time in runtime

No response

Are you willing to submit a PR?

No response

[lakshminarayana02]

Hi,
we are working on it.

[hemanthmanga]

Hi @0x5bfa, We will update you once the v17.13 is updated, Thanks.

[Sergio0694]

@lakshminarayana02 @hemanthmanga VS 17.13 also has the new Windows SDK 26100.2454 ingested into it. As part of updating VS to 17.13, will the runner image also get access to this latest Windows SDK 26100 revision? Thank you! 🙂

Update: I see the changelog now and it does indeed have the new Windows SDK, awesome!

[Galkon]

This started breaking our builds on windows, for code that has not changed in 7+ months.

Last successful action:
VS2022 (17.12.35707.178)

Ones that fail to build:
VS2022 (17.13.35818.85)

Please either provide a means of configuring this or provide a solution to resolve issues.

We already moved our github actions for macOS to self hosted runners because of the major instability and lack of reliability in github hosted runners. You're going to give us no choice but to move to our own hosted windows runners as well.

Being in the middle of a release and having workflows completely break because of something we cannot control and without a means of targeting older runner images is incredibly frustrating.

[0x5bfa]

We verified it works on our workflows, thanks.