Repository navigation
Outdated visualstudio2019-workload-vctools in Node.js 22+ Windows install_tools.bat #59031
Description
Activity
I'd like to add that the install_tools.bat doesn't work either for the node 22 > 24 change requiring ClangCL
on node 24
node_gyp rebuildis called during install (in a workspace that has latest electron and my own native libs) results in trying to use the Clang platform toolset.This (apparently) requires an add-on to the *-workload-vctools. But after sinking a day trying to add them, I couldn't get it to work. Neither could I work out how to globally force node-gyp to use a specific platform instead of ClangCL.
So yes - if someone picks this up - I humbly ask the ClangCL platform requirement is added.
Reacted by Mike McCready and David Hidalgo- linked a pull request that will close this issuewin: upgrade Visual Studio workload from 2019 to 2022 #60318
on Oct 23, 2025 Visual Studio 2022 meets the criteria
Visual Studio >= 2019 with the Windows 10 SDK on a 64-bit host
Visual Studio 2026 Insiders was announced Sep 9, 2025. This can be expected to transition to General Availability at some date in the not too distant future.
- added a commit that references this issue
on Oct 25, 2025 Just since I mentioned it in the previous comment,
Visual Studio 2026 is here: faster, smarter, and a hit with early adopters was announced on Nov 11, 2025.
This is a couple of weeks after #60318 was merged.
See also #60861 for compatibility with Visual Studio 2026
I'd like to add that the install_tools.bat doesn't work either for the node 22 > 24 change requiring ClangCL
on node 24
node_gyp rebuildis called during install (in a workspace that has latest electron and my own native libs) results in trying to use the Clang platform toolset.This (apparently) requires an add-on to the *-workload-vctools. But after sinking a day trying to add them, I couldn't get it to work. Neither could I work out how to globally force node-gyp to use a specific platform instead of ClangCL.
So yes - if someone picks this up - I humbly ask the ClangCL platform requirement is added.
If this is still a problem for you, could you open a new issue? I'm struggling to find a public npm package and a latest Node.js version which fails to build binaries due to missing ClangCL components. I believe it should theoretically still be an issue.
Reacted by Meirion HughesIf this is still a problem for you, could you open a new issue? I'm struggling to find a public npm package and a latest Node.js version which fails to build binaries due to missing ClangCL components. I believe it should theoretically still be an issue.
The problem has gone away; I don't know when, but node 24 and 25 are fine now; no mention of clang in the log; just spawning msbuild:
gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe gyp info spawn args [ gyp info spawn args 'build/binding.sln', gyp info spawn args '/clp:Verbosity=minimal', gyp info spawn args '/nologo', gyp info spawn args '/nodeReuse:false', gyp info spawn args '/p:Configuration=Release;Platform=x64' gyp info spawn args ]- added 2 commits that reference this issue
on Feb 17, 2026
Current situation
The version of Visual C++ build tools workload installed by tools/msvs/install_tools/install_tools.bat is not aligned with the version specified in BUILDING > Supported toolchains for Windows:
In all branches, tools/msvs/install_tools/install_tools.bat the following
chococommand is executed:This is also what gets executed if a user installs Node.js as a Windows MSI package and then selects to install "Tools for Native Modules"
Expected
For Node.js 22.x and 24.x expect that
tools/msvs/install_tools/install_tools.batinstallsVisual C++ build tools workload for Visual Studio 2022 (
visualstudio2022-workload-vctools)instead of
Visual C++ build tools workload for Visual Studio 2019 (
visualstudio2019-workload-vctools)Related