Windows-2022 Visual Studio License Expired

[Raxizh]

Description

Hello, we have a pipeline on Azure that uses the "windows-2022" build agent. We use it to build a .vdproj, and this requires the agent to have an available visual studio license, however; upon reaching the build step that requires us to have a license, we face this error:

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• 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

Image version and build link

Version: 20250527.1.0

Is it regression?

Yes

Expected behavior

There should be no error message for an expired visual studio license. This started on Friday, 06/27/2025.

Actual behavior

Build is failing

Repro steps

1. Ensure you have a pipeline.yml using the "windows-2022" image
2. Have a build-step that includes a call to "devenv.com"
3. Run it

[Prabhatkumar59]

Hi @Raxizh - Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.

[Prabhatkumar59]

@Raxizh - Also, In meantime, kindly share the repro steps and workflow links where you are facing the issue. It will help us debug the problem more effectively. Thanks!

[Raxizh]

@Prabhatkumar59 Thank you for the speedy response!

We switched build agents to "windows-2025" and this seems to fix the issue, however I will leave the post up for others who may be experiencing the same issue.

I am not entirely sure what you mean by workflow links, but I will post two screenshots below that show you the error and how we are getting it:

Starting: Build Installer
==============================================================================
Task : Command line
Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version : 2.250.1
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents: shell
"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\devenv.com" "D:\a\1\s\CSAutomation\CSAutomationWithInstaller.sln" /Build "ReleaseRhino8" /Project "D:\a\1\s\CSAutomation\CSAutomation-Installer\CSAutomation-Installer.vdproj"
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a_temp\b2f6e8d0-3149-4d74-9b6c-b56cf7fcac98.cmd""
Microsoft Visual Studio 2022 Version 17.13.2.
Copyright (C) Microsoft Corp. All rights reserved.
The license for Visual Studio has expired.
##[error]Cmd.exe exited with code '1'.
Finishing: Build Installer

This is the log of the failing build step.

• task: CmdLine@2
  displayName: Build Installer
  inputs:
  script: '"$(devCmd)" "$(solutionWithInstaller)" /Build "$(buildConfiguration)" /Project "$(vdproj)"'

This is the build step.

To reproduce, you would need to create an project-pipeline.yml file and attempt to build a project using the same format as above, where you access devenv.com which would require a visual studio license.

If you need any other information please let me know,

Thank you!

[Prabhatkumar59]

Hi @Raxizh - Thanks for follow up! We will look into this issue and and will update you accordingly.

[m-soltani]

FYI: This is the second time I’ve encountered this issue, and it appears to stem from the same root cause — the "runner images" in the Azure Pipelines pools are not up to date. The current image provided by the default pool is version 20250527.1.0, which is clearly outdated. As a result, the trial license required to use the devenv command in Visual Studio has already expired.

[m-soltani]

@Prabhatkumar59 : Please roll out the latest windows server 2022 image, If possible. This should solve the issue.

[Prabhatkumar59]

Hi @Raxizh - Once this week’s deployment is complete, the latest image version will begin rolling out. We will inform you of the new version, after which you can update your sync process accordingly and try using it.
Thank you!
Cc: @m-soltani

[m-soltani]

@Prabhatkumar59 : I already got a new version 20250617.1.0 and my pipelines are working again 👍🏻 Thank you!

[Prabhatkumar59]

Hi @m-soltani - That's great to hear! We will be closing this issue, thanks!