-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Closed
Copy link
Labels
Description
Description
When calling devenv
, I am seeing a message about an invalid MSVS license:
Microsoft Visual Studio 2022 Version 17.13.2.
Copyright (C) Microsoft Corp. All rights reserved.
Invalid license data. Repair Visual Studio from the Control Panel.
This occurs with the following image:
Runner Image
Image: windows-2022
Version: 20250602.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20250602.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20250602.1
However, this issue doesn't appear if the newer image Version: 20250609.2.0
gets used instead.
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
Failing build with image 20250602.1.0
- https://github.com/andrew-platt/openfast/actions/runs/15718059963/job/44300626480 (June 17, 2025)
- attempts 1:3 failed
- attempts 4:7 cancelled since same image that failed before (I was hoping the newer image would come up to verify it is this specific image)
- attempt 8 run with debugging info, in case this gives any additional info
Passing builds with image 20250609.2.0
- https://github.com/OpenFAST/openfast/actions/runs/15593423429/job/44045794836#step:1:7 (June 13, 2025)
- https://github.com/OpenFAST/openfast/actions/runs/15697506044/job/44225379591 (June 16, 2025)
Passing builds with image 20250427.1.0
Is it regression?
Images 20250427.1.0
and 20250609.2.0
work
Expected behavior
VS should run without a license error
Actual behavior
Reports a license expiration issue
Repro steps
- run our
deploy
action - if the
windows-2022
version20250602.1.0
gets used, the action fails.