How to Check Microsoft C++ Build Tools Version

For developers working in the Microsoft ecosystem, especially those building C++ applications, it’s essential to ensure that the right version of Microsoft C++ Build Tools is installed. This toolset includes compilers, linkers, libraries, and other utilities necessary for developing Windows applications in C++. Knowing which version you’re using helps in troubleshooting, validating compatibility, and following specific project requirements.

TL;DR

To check which version of Microsoft C++ Build Tools you have installed, the easiest approach is to use the Developer Command Prompt and run cl.exe with the /Bv flag. For Visual Studio installations, you can also check the version through the Visual Studio Installer. Additionally, examining environment variables or using PowerShell provides more flexibility. This guide explains each method with step-by-step instructions.

Why It Matters

Microsoft C++ Build Tools are frequently updated along with different versions of Visual Studio. These versions introduce new features, improve performance, and in many cases, retire older functionality. Ensuring compatibility between your system and project requirements is critical—especially when collaborating with teams or configuring CI/CD pipelines.

Furthermore, developers might be using different systems or performing builds inside containers where manual inspection isn’t straightforward. That’s why knowing how to check the version of C++ Build Tools installed is not just a matter of curiosity—it’s a necessary skill for efficient development workflows.

Method 1: Using the Developer Command Prompt

This is the most direct and reliable way to check the installed version of the Microsoft C++ compiler and build tools.

1. Open the Developer Command Prompt for Visual Studio. You can find this in your Windows Start Menu under your Visual Studio folder.
2. At the prompt, type:
   cl.exe /Bv

This command outputs detailed version information about the C++ compiler, including the version of the Microsoft Build Tools being used.

Here’s a sample of what the output might look like:

Microsoft (R) C/C++ Optimizing Compiler Version 19.38.33133 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.

Compiler Passes:
 C1.dll:         19.38.33133 
 C2.dll:         19.38.33133 
 Backend Version:                19.38.33133 

The version number (e.g., 19.38.33133) indicates the version of the compiler and, by extension, the build tools in use.

Method 2: Using the Visual Studio Installer

If you have Visual Studio installed, you likely also have Build Tools installed as part of the installation. The Visual Studio Installer provides a GUI method to check which components and versions are present.

1. Launch the Visual Studio Installer from the Start Menu.
2. Locate the version of Visual Studio you have installed and click the “Modify” button.
3. Under the “Workloads” tab, look for “Desktop development with C++” – this includes the Build Tools.
4. Switch to the “Individual components” tab and scroll down to locate C++ tools and compilers. You’ll see version numbers listed next to each.

This method is particularly useful when managing multiple instances or needing to verify exactly which components (e.g., MSVC v142, v143) are included in your build environment.

Method 3: Check Manually in Build Tools Installation Folder

Sometimes you may not have Visual Studio installed, just the Build Tools. In that case, you can check the installation folders directly.

By default, the Microsoft C++ Build Tools are installed in a directory similar to:

C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC

Inside the MSVC folder, you will find a directory named after the installed version—e.g., 14.38.33133. This folder name represents the version of the MSVC toolset (which contains the compiler, linker, standard libraries, etc.).

So, simply navigating to that directory will show you which version of the Build Tools you have installed.

Method 4: Using PowerShell

To script and automate version checks—especially on build servers—PowerShell is a powerful option. You can run the following script to identify the MSVC version:

$path = "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC"
if (Test-Path $path) {
    Get-ChildItem $path | ForEach-Object { $_.Name }
}

This script checks for folder names under the typical MSVC installation path. As noted earlier, the folder name corresponds to the MSVC toolset version.

Method 5: Environment Variables

Some installations of Visual Studio and Build Tools set environment variables that include version numbers or platform paths.

To view them, open a command prompt and run:

set

Look for variables such as:

• VCINSTALLDIR
• VCToolsInstallDir
• VSINSTALLDIR

You can then navigate to these directories and inspect their structure to determine the actual toolset versions.

Cross-Referencing MSVC Version with Build Tools Version

At this point, you might notice that MSVC version numbers like 14.38.33133 don’t correspond exactly with Visual Studio versions like 17.8.3.

To map MSVC versions to Visual Studio versions (and thus Build Tools releases), Microsoft provides official release notes and version mappings here:

Visual C++ Tools Documentation

You’ll find that:

• MSVC 14.38 – corresponds to Visual Studio 2022 v17.8
• MSVC 14.37 – corresponds to Visual Studio 2022 v17.7

Therefore, understanding how MSVC versions integrate with the Build Tools and Visual Studio is important, especially for troubleshooting and support purposes.

Conclusion

Knowing how to check the Microsoft C++ Build Tools version is crucial when developing, deploying, or supporting Windows-based applications using C++. Whether you’re using the command line, exploring installation directories, or automating inspections with PowerShell, each method outlined in this guide provides reliable ways to find the necessary version data.

Version precision aids compatibility, reduces integration issues, and makes collaboration among teams—especially in enterprise environments—more predictable. Whenever you update Visual Studio or migrate to a new development setup, don’t forget to verify that the installed tools meet project requirements.

Finally, for those managing multiple versions or targeting multiple platforms, keeping a record of toolchain versions can be an invaluable best practice.