[Windows-2022] Multiple VC Build Tools will be removed on May, 13 #9701

mikhailkoliada · 2024-04-16T19:47:18Z

Breaking changes

We will commence the procedure of removing redundant Microsoft.VisualStudio.Component.VC components and leave only the latest available version of some oh them.

Target date

The images rollout process will start on May, 13 and take 3-4 days.

The motivation for the changes

Due to numerous reports regarding errors when using Visual Studio 2022 with multiple pre-installed versions of VC build tools, we are compelled to cease the distribution of alternative versions of the component. Detailed description of the problem can be found here. The list of previously opened issues: #9670, #9404, #9086, #8891, #7867, #7832, #6107, #6091. Therefore, starting from May 6th, we will commence the procedure of removing redundant VC components and leave only the latest available version. We'll possibly reconsider this decision once the problem is resolved.

List of the VC components which are expected to be installed (if you notice that some useful base VC component is missing - indicate that in the comments, we will consider adding it):

Package	Version
Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM	latest
Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM64	latest
Microsoft.VisualStudio.Component.VC.ASAN	latest
Microsoft.VisualStudio.Component.VC.ATL	latest
Microsoft.VisualStudio.Component.VC.ATL.ARM	latest
Microsoft.VisualStudio.Component.VC.ATL.ARM.Spectre	latest
Microsoft.VisualStudio.Component.VC.ATL.ARM64	latest
Microsoft.VisualStudio.Component.VC.ATL.ARM64.Spectre	latest
Microsoft.VisualStudio.Component.VC.ATL.Spectre	latest
Microsoft.VisualStudio.Component.VC.ATLMFC	latest
Microsoft.VisualStudio.Component.VC.ATLMFC.Spectre	latest
Microsoft.VisualStudio.Component.VC.CLI.Support	latest
Microsoft.VisualStudio.Component.VC.CMake.Project	latest
Microsoft.VisualStudio.Component.VC.CoreIde	latest
Microsoft.VisualStudio.Component.VC.DiagnosticTools	latest
Microsoft.VisualStudio.Component.VC.Llvm.Clang	latest
Microsoft.VisualStudio.Component.VC.Llvm.ClangToolset	latest
Microsoft.VisualStudio.Component.VC.MFC.ARM	latest
Microsoft.VisualStudio.Component.VC.MFC.ARM.Spectre	latest
Microsoft.VisualStudio.Component.VC.MFC.ARM64	latest
Microsoft.VisualStudio.Component.VC.MFC.ARM64.Spectre	latest
Microsoft.VisualStudio.Component.VC.Modules.x86.x64	latest
Microsoft.VisualStudio.Component.VC.Redist.14.Latest	latest
Microsoft.VisualStudio.Component.VC.Redist.MSM	latest
Microsoft.VisualStudio.Component.VC.Runtimes.ARM.Spectre	latest
Microsoft.VisualStudio.Component.VC.Runtimes.ARM64.Spectre	latest
Microsoft.VisualStudio.Component.VC.Runtimes.ARM64EC.Spectre	latest
Microsoft.VisualStudio.Component.VC.Runtimes.x86.x64.Spectre	latest
Microsoft.VisualStudio.Component.VC.TestAdapterForBoostTest	latest
Microsoft.VisualStudio.Component.VC.TestAdapterForGoogleTest	latest

Possible impact

Builds that require non-latest components missing from the list above will be broken.

Platforms affected

Azure DevOps
GitHub Actions

Runner images affected

Mitigation ways

Missing workloads can be installed manually in runtime. We recommend to uninstall unsupported workloads before installing new, it might be done using this snippet.

    steps:
      - name: Delete components
        run: |
                Set-Location "C:\Program Files (x86)\Microsoft Visual Studio\Installer\"
                $InstallPath = "C:\Program Files\Microsoft Visual Studio\2022\Enterprise"
                $componentsToRemove= @(
                    "Microsoft.VisualStudio.Component.VC.ATL.ARM"
                    "Microsoft.VisualStudio.Component.VC.ATL.ARM.Spectre"
                )
                [string]$workloadArgs = $componentsToRemove | ForEach-Object {" --remove " +  $_}
                $Arguments = ('/c', "vs_installer.exe", 'modify', '--installPath', "`"$InstallPath`"",$workloadArgs, '--quiet', '--norestart', '--nocache')
                # should be run twice
                $process = Start-Process -FilePath cmd.exe -ArgumentList $Arguments -Wait -PassThru -WindowStyle Hidden
                $process = Start-Process -FilePath cmd.exe -ArgumentList $Arguments -Wait -PassThru -WindowStyle Hidden
      
      - name: Install components
        run: |
                Set-Location "C:\Program Files (x86)\Microsoft Visual Studio\Installer\"
                $InstallPath = "C:\Program Files\Microsoft Visual Studio\2022\Enterprise"
                $componentsToRemove= @(
                  "Microsoft.VisualStudio.Component.VC.14.39.17.9.ATL.ARM"
                  "Microsoft.VisualStudio.Component.VC.14.39.17.9.ATL.ARM.Spectre"
                )
                [string]$workloadArgs = $componentsToRemove | ForEach-Object {" --add " +  $_}
                $Arguments = ('/c', "vs_installer.exe", 'modify', '--installPath', "`"$InstallPath`"",$workloadArgs, '--quiet', '--norestart', '--nocache')
                # should be run twice
                $process = Start-Process -FilePath cmd.exe -ArgumentList $Arguments -Wait -PassThru -WindowStyle Hidden
                $process = Start-Process -FilePath cmd.exe -ArgumentList $Arguments -Wait -PassThru -WindowStyle Hidden

The text was updated successfully, but these errors were encountered:

malkia · 2024-05-06T21:21:44Z

I saw only Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM and Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM64 - but not x64 and x86.

14.29 is Visual Studio 2019 (v142)

joel-nascimento · 2024-05-15T12:49:58Z

C++ MFC for v142 build tools (x86 & x64)

{"fail_fast": false, "matrix": [{"name": "Windows", "workflow": "windows", "wpt_layout": "none", "profile": "release", "unit_tests": true, "wpt_tests_to_run": ""}]}

erik-bershel · 2024-05-16T14:59:03Z

Heads up.
Latest windows-2022 image contains described list of VC tools. Please ping us if something went wrong.

caesay · 2024-05-16T22:15:52Z

This change is is "very not ideal". Has broken all my fairly basic/standard Rust pipelines in a very non-obvious way (eg. builds succeed but now are producing invalid binaries). I assume that the new image is missing something which is critical for Rust. Microsoft.VisualStudio.Component.VC.Tools.x86.x64 for sure? probably more.

erik-bershel · 2024-05-17T09:02:26Z

Hey @caesay!
Thank you for catching this bug. We'll add this component with the next windows-2022 image release. If you see that something else is missing, be sure to mention it - we will definitely try to add it.

…ctos#6899) GitHub dropped VS2017 in the windows-latest runner: - actions/runner-images#9701 - ilammy/msvc-dev-cmd#80 Addendum to 0f81f46.

actions/runner-images#9701

mikhailkoliada added Announcement OS: Windows Area: Common Tools labels Apr 16, 2024

mikhailkoliada changed the title ~~Visual studio~~ [Windows-2022] Multiple VC Build Tools will be removed on May, 13 Apr 16, 2024

mikhailkoliada pinned this issue Apr 16, 2024

This was referenced Apr 16, 2024

C++ image migration Azure/azure-sdk-for-cpp#5483

Open

Add retries to DisableCrlValidation test to improve reliability Azure/azure-sdk-for-cpp#5537

Merged

erik-bershel mentioned this issue Apr 17, 2024

Image windows-2022: Microsoft.VCToolsVersion.v143.default.props contains wrong version #9670

Closed

13 tasks

erik-bershel self-assigned this Apr 17, 2024

danieljurek mentioned this issue Apr 18, 2024

Revert win2022 image back to latest and add msvc version mitigation Azure/azure-sdk-for-cpp#5539

Merged

Steelskin mentioned this issue May 4, 2024

Remove workaround for the MSVC CI builder after upstream has been fixed. visualboyadvance-m/visualboyadvance-m#1297

Open

julianoes mentioned this issue May 7, 2024

Fix warnings mavlink/MAVSDK#2291

Open

erik-bershel mentioned this issue May 9, 2024

[Windows] Remove all non-latest Visual Studio 2022 VC components except ComponentGroup.UWP.VC.v142 #9819

Merged

4 tasks

mikhailkoliada added the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label May 9, 2024

barnson mentioned this issue May 16, 2024

Adapt to lack of v141 VC toolset on GitHub Actions runner images wixtoolset/issues#8211

Open

1 task

sagudev mentioned this issue May 16, 2024

build(deps): bump smol_str from 0.2.1 to 0.2.2 servo/servo#32295

Merged

mrobinson added a commit to servo/servo that referenced this issue May 16, 2024

Fix missing MSVC components after actions/runner-images#9701

5958d4d

mrobinson added a commit to servo/servo that referenced this issue May 16, 2024

Fix missing MSVC components after actions/runner-images#9701

8e52475

mrobinson added a commit to servo/servo that referenced this issue May 16, 2024

Fix missing MSVC components after actions/runner-images#9701

18b97f6

mrobinson added a commit to servo/servo that referenced this issue May 16, 2024

Fix missing MSVC components after actions/runner-images#9701

65f6494

mukilan pushed a commit to mukilan/servo that referenced this issue May 16, 2024

Fix missing MSVC components after actions/runner-images#9701

7d4e35e

pzhlkj6612 mentioned this issue May 16, 2024

Toolset directory for version '14.38' was not found. ilammy/msvc-dev-cmd#80

Closed

MisterDA mentioned this issue May 16, 2024

gha: use latest Visual Studio compiler ocaml/ocaml#13174

Merged

erik-bershel closed this as completed May 16, 2024

erik-bershel removed the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label May 16, 2024

mikhailkoliada unpinned this issue May 16, 2024

erik-bershel mentioned this issue May 16, 2024

Missing atlbase.h file in windows-2022 runner #9873

Open

14 tasks

sodul mentioned this issue May 16, 2024

atlbase.h missing overnight microsoft/setup-msbuild#127

Closed

erik-bershel mentioned this issue May 17, 2024

[Windows] Add more compatible VS2022 VC components #9876

Open

4 tasks

antonwolfy added a commit to antonwolfy/dpnp that referenced this issue May 17, 2024

Try w/a from actions/runner-images/issues/9701

24fb2d3

phprus mentioned this issue May 17, 2024

Use windows-2019 for build with toolset v141 zlib-ng/zlib-ng#1725

Merged

edo9300 added a commit to edo9300/edopro-vcpkg-cache that referenced this issue May 18, 2024

Install vc141 component in windows-2022 runner for vs2017

9eb8f0e

actions/runner-images#9701

claremacrae mentioned this issue May 18, 2024

update-docs-markdown GitHub Action runs have started failing obsidian-tasks-group/obsidian-tasks#2834

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Windows-2022] Multiple VC Build Tools will be removed on May, 13 #9701

[Windows-2022] Multiple VC Build Tools will be removed on May, 13 #9701

mikhailkoliada commented Apr 16, 2024 •

edited

malkia commented May 6, 2024

joel-nascimento commented May 15, 2024

erik-bershel commented May 16, 2024

caesay commented May 16, 2024 •

edited

erik-bershel commented May 17, 2024

[Windows-2022] Multiple VC Build Tools will be removed on May, 13 #9701

[Windows-2022] Multiple VC Build Tools will be removed on May, 13 #9701

Comments

mikhailkoliada commented Apr 16, 2024 • edited

Breaking changes

Target date

The motivation for the changes

Possible impact

Platforms affected

Runner images affected

Mitigation ways

malkia commented May 6, 2024

joel-nascimento commented May 15, 2024

erik-bershel commented May 16, 2024

caesay commented May 16, 2024 • edited

erik-bershel commented May 17, 2024

mikhailkoliada commented Apr 16, 2024 •

edited

caesay commented May 16, 2024 •

edited