Visual C++ Redistributable Runtimes AIO Repack is a free installer by abbodi1406 that puts every Microsoft Visual C++ runtime from 2005 to 2026 onto a Windows PC in one pass, which is what fixes most missing DLL errors.
Visual C++ Redistributable Runtimes AIO Repack installs every Microsoft Visual C++ runtime a Windows program might ask for, in one pass.
Most people arrive here because something refused to start and named a missing DLL file.
It is free, it comes from the developer abbodi1406 rather than from Microsoft, and the difference matters enough that there is a section on it below.
The Errors This Fixes
If a program has just failed with one of these, you are in the right place:
- The code execution cannot proceed because VCRUNTIME140.dll was not found.
- MSVCP140.dll is missing from your computer.
- The program can't start because MSVCR120.dll is missing.
- MSVCP100.dll, MSVCR110.dll, VCOMP140.dll and a long list of similar names.
The number in the filename is the runtime version, so 140 is the 2015-to-2026 family, 120 is 2013, 110 is 2012 and 100 is 2010. Reinstalling the program almost never helps, because the file was never part of the program in the first place.
What A Visual C++ Runtime Actually Is
Windows programs written in C++ do not carry their own copies of common code for things like memory handling and string formatting. They call a shared library that Microsoft ships separately, and that library is the Visual C++ Redistributable.
Developers are supposed to bundle the right one with their installer, and plenty do not - especially with portable builds, which are just an unzipped folder with no installer to bundle anything. That is why a tool can run perfectly on one PC and fail instantly on another.
Each Visual Studio generation has its own runtime, and they do not replace each other. A machine that has run Windows software for years will genuinely need several of them side by side, which is the problem this package exists to solve.
What Is Inside The Package
One download covers the whole family, in 32-bit and 64-bit where both exist:
- The modern runtimes - VC++ 2022 and VC++ 2026, which between them cover everything built with Visual Studio 2015, 2017, 2019, 2022 and 2026, because those releases are binary compatible with each other.
- The older ones - 2005, 2008, 2010, 2012 and 2013, each still required by plenty of software that has not been rebuilt since.
- The legacy 32-bit runtimes - Visual C++ 2002 and 2003, plus the Visual Basic runtimes, for genuinely old utilities.
- Visual Studio 2010 Tools for Office, which some Office add-ins still want.
- The Universal CRT, built into Windows 10 and 11 already, and installed as an update on older systems that lack it.
The repack strips the installer wrappers Microsoft ships around each package and drives the MSI files directly from a script, which is why one download covers all of that without being enormous.
Before installing, it checks for older or damaged versions of each runtime and removes them, so you are not left with three half-registered copies of the 2012 redistributable. There is an uninstall mode too, which removes every VC++ runtime it can find apart from the Universal CRT.
The 2022 and 2026 Split
This is the part that confuses people now, because Microsoft split the newest runtime by operating system.
| Your Windows | What you get |
|---|---|
| Windows 10 or 11 | VC++ 2026, which covers everything built with Visual Studio 2015 through 2026. |
| Windows 7, 8 or 8.1 | VC++ 2022, the last v14 runtime Microsoft will ship for these. Still covers Visual Studio 2015 through 2022. |
| Windows Vista | Nothing here works. Release v0.61.0 is the last one compatible. |
| Windows XP | Nothing here works either. Release v0.35.0 is the last one compatible. |
You do not have to work out which applies to you. The repack carries both and installs whichever suits the system it is running on.
Which File To Download
Take the VisualCppRedist_AIO_x86_x64.exe installer unless you have a specific reason not to - it handles both 32-bit and 64-bit runtimes and is what nearly everyone wants.
The zip is the same content for anyone who would rather see inside before running it, and the ARM64 build is for Windows on ARM machines, where the 2022 and Office runtime options do nothing because those packages have no ARM64 version.
How To Install It
Run the installer as administrator and let it finish. The work is done by a command script running hidden in the background, so there is no wizard and not much to look at - and because Windows Installer creates a restore point per package when System Restore is enabled, the first run on an older machine can take a while.
If you would rather watch it work, or you are scripting a fresh Windows setup, the exe takes switches: /y for a visible pass with no prompts, /ai /gm2 for a fully silent one, /ai1 to update only what is already installed, and /aiR to remove every runtime it detects.
You can also extract the exe with 7-Zip or WinRAR to a short path and run Installer.cmd as administrator, which does the same thing with the script visible. Running the exe with /? prints the full switch list.
Where It Is Not The Answer
A missing DLL that is not a runtime file will not be fixed here. If the name does not look like the ones above, search for it before installing anything - it may belong to the program itself, or to a codec pack.
The 0xc000007b error is the one that catches people out. It usually means a 64-bit program is loading a 32-bit library or the reverse, and while installing both architectures of the runtimes often clears it, a mismatched plugin or a half-finished install can produce the same code.
Playback problems are a different department entirely. If a video will not play or has no sound, you want K-Lite Codec Pack or a player that carries its own decoders, not a runtime installer.
MPC-HC and VLC Media Player both do that, and both will play a file that Windows Photos or the Films app refuses.
Games and graphics applications that complain about d3d or xinput files want DirectX instead, and applications built on Microsoft's newer web stack want the Microsoft Edge WebView2 Runtime.
Is It Safe To Run A Repack
Fair question, and worth answering rather than dodging. This is not a Microsoft download. It is a repackage by abbodi1406, built on earlier work by ricktendo64, and it runs a script as administrator that uninstalls and reinstalls system components.
What is in its favour: the project is open on GitHub with thousands of users, the installer contains Microsoft's own signed MSI packages rather than modified binaries, and every release publishes SHA-256 checksums you can verify against the file you downloaded.
If you would still rather not, Microsoft publishes each redistributable individually on its own site - you will be downloading seven or eight installers instead of one, and running them one at a time, but it is the same result from the original source.
Why This Matters On A Codecs Site
Most of the Windows media tools here are native C++ applications, so they link against these runtimes whether their download page mentions it or not. Encoders and front ends like StaxRip and ShanaEncoder are typical, and portable builds are the ones most likely to fail because they ship no installer to add anything.
The same goes for HandBrake and OBS Studio, both of which stop at a DLL box on a freshly installed Windows.
Command-line tools do it too, only less visibly - the various FFmpeg builds fail in a console window you may never see, and MediaInfo is the quickest way to check a file once everything runs again.
Editors and muxers behave no differently: Audacity and MKVToolNix are native Windows builds with exactly the same dependency.
Getting the runtimes in place once, before you start installing media software, saves working out which specific tool was missing which specific file. If you are setting up a new machine, Snappy Driver Installer Origin covers the other half of that job.
What Changed in 0.105.0
A small release, published on 6 June 2026, and there is nothing newer at the time of writing:
- Updated to Visual C++ v14 (2026) Redistributable 14.51.36247.0.
- Improved detection of INF-based entries, so they no longer duplicate the MSI ones.
- Added a Hide All option to ARP.cmd, which hides both INF and MSI uninstall entries.
The tidier uninstall entries themselves arrived in 0.104.0, which replaced the sprawl of near-identical "Microsoft Visual C++ ... Redistributable" lines in Apps and Features with a single organised entry per version. The same release added the ARM64 build and switched on a Windows Installer flag that speeds the install up.
Quick questions
Will this fix my missing DLL error?
If the file is a VCRUNTIME, MSVCP or MSVCR one, almost certainly. If the name looks like something else, search for that name first rather than installing anything.
Is it safe, and is it from Microsoft?
It is not from Microsoft - it is a third-party repack of Microsoft's own signed installer packages, published openly with SHA-256 checksums for every release. Microsoft's individual downloads are the alternative.
Will it break the runtimes I already have?
It replaces older or damaged versions with current ones rather than stacking another copy on top, and Windows creates a restore point per package if System Restore is on.
Do I need this on Windows 11?
Windows 11 includes the Universal CRT but not the Visual C++ runtimes themselves, so yes - a clean Windows 11 install still hits missing DLL errors.
Does it work on Windows 7?
Yes. You get VC++ 2022, the last version Microsoft ships for Windows 7, 8 and 8.1, which covers everything built with Visual Studio 2015 through 2022.
Can I install it silently on several machines?
Yes - /ai /gm2 runs it with no output at all, and /ai1 updates only what is already present. Run the exe with /? for the full list.
Download Visual C++ Redistributable Runtimes AIO Repack 0.105.0 and see whether it clears your error, or tell us how you got on - there are no reviews here yet, so yours would be the first.