Microsoft is rolling out a major update to how the Microsoft C++ (MSVC) Build Tools are released and supported, starting with Visual Studio 2026 and MSVC version 14.50, which shipped on November 11 as a Long-Term Support (LTS) release. The company is decoupling MSVC from the Visual Studio IDE, giving developers rapid IDE innovation while delivering predictable, long-term stability for compiler and toolchain updates.

What’s changing

MSVC release cadence and support lifecycle. Credit: Microsoft

MSVC now follows the Modern Lifecycle Policy, with a clear and consistent release rhythm:

• Semiannual releases every May and November

• Nine months of support for each regular release

• LTS releases every two years in November, with three years of support

• Releases, including previews, available on both Stable and Insiders channels

The MSVC toolchain covered by this change includes core compiler tools such as cl.exe and link.exe, C and C++ libraries like STL, ATL/MFC and OpenMP, and the VC Runtime redistributables.

This shift gives teams more predictable planning windows, reduced fragmentation and a lifecycle aligned with .NET’s LTS schedule.

What stays the same

Visual Studio remains the primary way to install MSVC, and developers can continue using multiple side-by-side MSVC versions to meet project requirements. ABI compatibility between MSVC 14.50 and versions dating back to Visual Studio 2015 also remains intact, making step-by-step migrations easier.

Redistributables will continue to behave as in-place binary-compatible upgrades, and MSVC versions that shipped with Visual Studio 2022 and earlier will follow the lifecycle of their respective Visual Studio versions.

Why the change

Microsoft says the new schedule better serves teams that value stability, compliance and secure supply chains:

• Visual Studio now ships monthly feature updates, but most customers prefer a slower-moving compiler toolchain.

• Regulations and standards from organizations such as NIST and CISA require modern, up-to-date build tools to maintain compliance.

• Supporting a decade of legacy compiler versions has become increasingly complex.

• Fewer MSVC versions allow deeper investment in C++ conformance, safety and performance.

Helping teams upgrade

Visual Studio 2026 adds new tools to make migrations smoother:

• Setup Assistant, a more flexible workflow that separates IDE upgrades from toolset installation

• Generous overlap: 1-year overlap for LTS releases and 3 months for regular releases

• ABI compatibility, enabling incremental adoption without full rebuilds

• vcpkg support for rebuilding third-party dependencies with the latest toolset

• A new GitHub Copilot app modernization for C++ experience in Private Preview, capable of updating project settings, enabling recommended warnings, and modernizing code for stricter compliance

Teams can sign up for the Copilot modernization preview to test these new capabilities.

Looking ahead

Microsoft encourages teams to upgrade to MSVC Build Tools 14.50 to take advantage of performance improvements, better standards conformance and enhanced security. Developers can submit feedback directly through Visual Studio’s Help menu or reach the team at [email protected].