Msvc V142 - Vs 2019 C X64/x86 Build Tools _top_ 〈2025-2026〉

Run the Visual Studio Installer, select "Modify" on VS 2019, go to the "Individual components" tab, and search for "MSVC v142" . Check the box for the latest version of "MSVC v142 - VS 2019 C++ x64/x86 build tools".

Microsoft's policy is that the v142 toolset (VS 2019) is fully supported as long as the runtime libraries are included in the Windows OS. Since Windows 10 and 11 ship with the v142 redistributables, your binaries will run indefinitely.

Why your pipeline says “v142” and why you shouldn’t confuse it with your IDE. msvc v142 - vs 2019 c x64/x86 build tools

Demystifying msvc v142 : The Heart of VS 2019 for x64/x86 Builds

If you’ve ever dug into a .vcxproj file, browsed the Visual Studio Installer, or debugged a failing CI/CD pipeline, you’ve likely encountered the cryptic string: (often seen as PlatformToolset v142 ). Run the Visual Studio Installer, select "Modify" on

| Visual Studio Version | Default Platform Toolset | |----------------------|--------------------------| | VS 2017 | v141 | | | v142 | | VS 2022 | v143 | The Specifics: msvc v142 for x64/x86 When you select v142 , you are telling MSBuild: "Use the C++ compiler and libraries that shipped with Visual Studio 2019."

The toolset is not the IDE. You can build v142 code inside VS 2022, and you can build v143 code inside VS 2019 (with extensions). But for consistency across your team and your CI server—pin your toolset to v142 and never look back. Have you run into a strange v142 linker error? Let me know in the comments below. Since Windows 10 and 11 ship with the

Pro tip: If you are running a CI/CD pipeline (GitHub Actions, Azure DevOps, Jenkins), do install the full IDE. Use the Build Tools for Visual Studio 2019 installer and select only the v142 workload. v142 in CI/CD Pipelines Here is how you invoke the v142 toolset for x64 on a headless build server: