actions
Please add the VS2019 toolset to the 2022 runner
Tool name
MSVC 14.x
Tool license
same as alreads installes MS VS 2022
Add or update?
- [x] Add
- [ ] Update
Desired version
latest
Approximate size
No response
Brief description of tool
Required to build VS2019 projects, now that the 2019 runner is deprecated its the only way. running: run: START "" /WAIT "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" --add Microsoft.VisualStudio.Component.VC.14.29.16.11.x86.x64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL --add Microsoft.VisualStudio.Component.VC.14.29.16.11.CLI.Support --add Microsoft.VisualStudio.Component.VC.14.29.16.11.MFC --quiet --norestart
each time takes for ever watest your resources and our time.
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 22.04
- [ ] Ubuntu 24.04
- [ ] macOS 13
- [ ] macOS 13 Arm64
- [ ] macOS 14
- [ ] macOS 14 Arm64
- [ ] macOS 15
- [ ] macOS 15 Arm64
- [ ] Windows Server 2019
- [x] Windows Server 2022
- [x] Windows Server 2025
Can this tool be installed during the build?
yes but it takes about 15 minutes!!!
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response
Hi @DavidXanatos , Thank you for bringing this feature request issue to our attention. We will look into this issue and will update you after investigating.
I'm also affected by this change. You deprecated the VS2019 runner, and without VS2019 support you broke all my builds as of July 1. Of course I can figure something out, but why are you breaking builds for no reason? I'm expecting a longer support period.
If you want me to move onto windows-latest, provide better support for older projects.
You can fix your project by using the 2019 runner from Azure it supported until December
is that free ow how much doe sit cost?
It looks like it's already installed. The list of VS components includes Microsoft.VisualStudio.ComponentGroup.VC.Tools.142.x86.x64, and it seems to work for me.
when I tested it back then it did nto work, may be only the .MFC and .ATL is missing anyhow i need the full set with MFC and ATL and also i woudl need the ARM versions as well:
START "" /WAIT "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ARM64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.x86.x64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL.ARM --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL.ARM64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL --add Microsoft.VisualStudio.Component.VC.14.29.16.11.CLI.Support --add Microsoft.VisualStudio.Component.VC.14.29.16.11.MFC.ARM --add Microsoft.VisualStudio.Component.VC.14.29.16.11.MFC.ARM64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.MFC --quiet --norestart
@DavidXanatos It's already Installed in the windows 22 and 25 Images.Thank you.
For my use case, all I need is v141 toolset. It's OK to require use of VS2022 for the windows-2022 runner, but I don't understand why you don't just include the other toolsets by default.
In the windows-2022 runner, my logs show that the v142 and v144 toolsets are already installed. It just seems like it is not asking for much to have older toolsets like v141 installed also. It's just an image.
My builds normally require less than 20 seconds to run- and now they take 6 minutes to install v141. As the OP notes, this is just a waste of time and resources.
@DavidXanatos I hope your issue got resolved, We are closing this issue. Thanks.