The shared runtime used by many Windows applications
Microsoft Visual C++ Redistributable installs C and C++ runtime libraries needed by applications built with compatible Microsoft development tools. This page covers the current v14 family, which Microsoft lists for Visual Studio 2017, 2019, 2022 and 2026. The verified x86 and x64 package version is 14.51.36247.0. Its role is to satisfy execution dependencies, not provide the complete Visual Studio development environment.
A program may request this runtime during setup or report a missing library when it starts. Follow that application’s requirements before choosing a package. The presence of C++ in its description is not enough to infer the exact dependency, and an installed runtime does not resolve unrelated missing data, licensing requirements or operating-system incompatibilities.
Select x86, x64 or ARM64 for the application
Choose according to the program’s target architecture. A 32-bit application needs x86 components even on a compatible 64-bit Windows machine. A 64-bit x64 application needs the matching x64 libraries, while native ARM64 software has ARM64 requirements. A computer can consequently need more than one runtime architecture for its installed software.
The current x64 installer contains both x64 and ARM64 binaries, which supports the relevant deployment on ARM64 devices. This does not mean it includes the separate x86 runtime or converts an application into another architecture. Keep operating-system compatibility, application architecture and installer contents as related but distinct checks.
Understand the version rule within v14
Microsoft requires the installed redistributable to be at least as recent as the build tools used to create the dependent application. Within the compatible v14 family, one maintained runtime serves programs built with supported toolsets from several Visual Studio releases. That differs from downloading an unrelated historical family merely because its year resembles the application’s release date.
Libraries from 2013 and earlier remain separate. For example, Visual C++ 2010 Redistributable can still be required by older software after v14 is installed. Do not remove that dependency on the assumption that the latest package universally replaces every Visual C++ entry. Visual Studio 2015 support ended in October 2025; binary compatibility within v14 does not reopen the old product’s support lifecycle.
Install or repair without unnecessary downgrades
Close the affected application, save work and run the matching installer with the necessary permissions. Complete any requested restart, then repeat the operation that failed. The current installer supports installation and repair operations; use the action appropriate to the existing state instead of repeatedly removing every library family.
An older installer can refuse to proceed when a newer compatible redistributable is already present. That message alone does not prove corruption or justify a downgrade. Review the installed version and the application requirement. For a persistent reproducible launch problem, Process Monitor can help inspect file and Registry activity, while individual failed lookups still need interpretation in context.
Windows requirements and licensing
Microsoft lists Windows 10 and Windows 11 for the current v14 package, together with Windows Server 2016, 2019, 2022 and 2025. Do not extend these current requirements to Windows 7 or assume a historical package’s system list applies to this release. The application itself can impose additional operating-system or hardware conditions.
The runtime has no separate end-user purchase and is proprietary Microsoft software. It is not a compiler subscription, an application licence or open-source permission to redistribute every file without conditions. Developers must follow the applicable redistribution terms. After setup, verify the dependent program’s actual task; a completed installer is not a guarantee that every function or unrelated software issue has been resolved.