[v24.x backport] build: add support for Visual Studio 2026

[MikeMcC399]

Backporting 2 interrelated PRs:

---

commit a4b05c1
Author: Michaël Zasso targos@protonmail.com
Date: Wed Nov 19 17:01:37 2025 +0100

build: add support for Visual Studio 2026

Backport-PR-URL: https://github.com/nodejs/node/pull/61840
PR-URL: https://github.com/nodejs/node/pull/60727
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com>

---

commit 25c5353
Author: Stefan Stojanovic stefan.stojanovic@janeasystems.com
Date: Wed Jan 28 15:52:43 2026 +0100

build,win: fix vs2022 compilation

Backport-PR-URL: https://github.com/nodejs/node/pull/61840
PR-URL: https://github.com/nodejs/node/pull/61530
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <richard.lau@ibm.com>

---

Situation

BUILDING > Supported toolchains for the v24.x branch shows:

Operating System	Compiler Versions
Windows	Visual Studio >= 2022 with the Windows 10 SDK on a 64-bit host

With only Visual Studio 2026 Build Tools Edition from https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2026 installed with necessary prerequisites (no side-by-side Visual Studio 2022 installed), executing .\vcbuild in a PowerShell 7 terminal fails, although the "Supported toolchains" suggest that Visual Studio 2026 should be supported.

Looking for Visual Studio 2022
Failed to find a suitable Visual Studio installation with Clang compiler/LLVM toolset.

Change

Cherry-pick 934d907 from #60727

Preserve the [nocorepack] option in vcbuild.bat v24.x, which was removed for >=v25.x, to resolve a cherry-pick conflict.

Also cherry-pick 5a8864d from #61530 to fix a one line bug in #60727 which prevented selecting Visual Studio 2022 with .\vcbuild vs2022 in a side-by-side configuration where both Visual Studio 2022 and 2026 were installed.

Verification

In Windows 11 25H2 with Visual Studio 2022 & 2026 variously installed / not installed, ensure that all valid command combinations of .\vcbuild run:

Command	Visual Studio 2022 installed	Visual Studio 2026 installed	Studio version selected
.\vcbuild	YES	NO	vs2022
.\vcbuild vs2022	YES	NO	vs2022
.\vcbuild	YES	YES	vs2026
.\vcbuild vs2022	YES	YES	vs2022
.\vcbuild vs2026	YES	YES	vs2026
.\vcbuild	NO	YES	vs2026
.\vcbuild v2026	NO	YES	vs2026

[Renegade334]

For releasers, can you prepend Backport-PR-URL: https://github.com/nodejs/node/pull/61840 to your commit trailers?

[MikeMcC399]

@Renegade334

For releasers, can you prepend Backport-PR-URL: #61840 to your commit trailers?

Thanks for your guidance! I did read in https://github.com/nodejs/node/blob/main/doc/contributing/backporting-to-release-lines.md#manual-process that it says:

The Backport-PR-URL metadata does need to be added to the commit, but this will be done later.

So the instructions aren't really very specific about whose action this is and what is supposed to be done.

---

I have added the Backport-PR-URL metadata now and force pushed. Hopefully I got this right!

[Renegade334]

Thanks. I believe that advice only applies to git node backport which adds the backport metadata during the landing session.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71368/