Seeing “VCRUNTIME140.dll was not found” when you open a program in Windows 11 usually means the application cannot find a required Microsoft Visual C++ runtime component.
You don’t normally need to search the internet for the missing DLL itself. In most cases, the better solution is to install or repair the Microsoft Visual C++ Redistributable that the application needs.
This guide explains exactly what to do, including which version to install, what to try if Visual C++ is already installed, and what to avoid.
What Is VCRUNTIME140.dll?
VCRUNTIME140.dll is part of Microsoft’s Visual C++ runtime libraries.
Applications built with Microsoft Visual C++ can depend on these runtime libraries to start and operate correctly. Microsoft explains that applications built with supported MSVC tools require a sufficiently recent Visual C++ Redistributable on the computer where the application runs.
When the required runtime isn’t available or the installation is damaged, Windows may display an error such as:
The code execution cannot proceed because VCRUNTIME140.dll was not found.
You might also see:
The program can’t start because VCRUNTIME140.dll is missing from your computer.
The wording can vary, but the underlying issue is similar: the application cannot access the runtime component it expects.
The Quickest Fix
For most people, start here:
- Download the latest supported Microsoft Visual C++ Redistributable from Microsoft.
- Install the package matching your application’s architecture.
- If you’re using 64-bit Windows and aren’t sure whether the application is 32-bit or 64-bit, install both x64 and x86 packages.
- Restart Windows.
- Try opening the application again.
Microsoft provides permanent download links for the current x64, x86, and ARM64 packages on its official documentation page.
Microsoft Visual C++ Redistributable downloads
1. Download the Official Visual C++ Redistributable
The most important step is to get the runtime from Microsoft rather than downloading an individual DLL.
Microsoft’s current Visual C++ v14 Redistributable is intended for applications built with supported versions of Visual Studio, including Visual Studio 2017, 2019, 2022, and 2026.
On a typical Windows 11 PC, you’ll usually be choosing between:
- x64 — for 64-bit applications
- x86 — for 32-bit applications
- ARM64 — for compatible ARM-based Windows devices
The Redistributable architecture needs to match the application’s target architecture.
Which one should you install?
If you know the application is 64-bit, install x64.
If the application is 32-bit, install x86.
If you’re using 64-bit Windows 11 but aren’t sure which architecture the affected application uses, installing both x64 and x86 is a practical option. They can coexist because they support different application architectures.
2. Install the Redistributable
After downloading the appropriate Microsoft installer:
- Open the downloaded
vc_redistinstaller. - Read and accept the license terms.
- Select Install.
- Wait for the installation to finish.
- Restart Windows.
Then launch the program that produced the VCRUNTIME140.dll error.
If it opens normally, you have solved the problem.
What if Microsoft says the runtime is already installed?
Don’t assume that means everything is working correctly.
An existing Visual C++ installation can be damaged or incomplete. In that situation, use the Repair option described below.
3. Repair Visual C++ If It’s Already Installed
If you already have the Visual C++ Redistributable installed, repairing it is the next thing to try.
In Windows 11:
- Press Windows + I to open Settings.
- Select Apps.
- Select Installed apps.
- Search for Visual C++.
- Find the relevant Microsoft Visual C++ Redistributable entry.
- Select the three-dot menu.
- Choose Modify.
- Select Repair when the Microsoft installer appears.
- Let the repair finish.
- Restart Windows.
Then try opening the affected application again.
The reason this step matters is that reinstalling the runtime isn’t always necessary if the package is present but its installation needs repair.
4. Still Getting the Error? Check x86 vs x64
This is one of the easiest details to overlook.
64-bit Windows does not mean every application you install is 64-bit.
Windows 11 can run older 32-bit applications. A 32-bit application may therefore need the x86 Visual C++ Redistributable, even when Windows itself is 64-bit.
For example:
64-bit Windows + 32-bit application → x86 runtime
64-bit Windows + 64-bit application → x64 runtime
If you don’t know which type of application is producing the error, installing both Microsoft packages is often simpler than trying to identify the application’s architecture manually.
Microsoft specifically notes that the Redistributable architecture must match the application’s target architecture.
5. What If VCRUNTIME140.dll Is Still Missing?
If you’ve installed or repaired the appropriate Redistributable and the application still produces the same error, the problem may be specific to that application.
Try these checks before making major Windows changes.
Reinstall the affected application
Uninstall the program from:
Settings → Apps → Installed apps
Then download a fresh installer from the application’s official website or its trusted distribution platform.
A damaged application installation can sometimes cause startup failures even when the required runtime is correctly installed.
Check the application’s own requirements
Some applications, particularly older software, games, and specialized utilities, may require a particular runtime or additional Microsoft component.
If the application’s developer provides installation instructions, follow those instructions rather than manually copying DLL files.
Microsoft also recommends contacting the application vendor when troubleshooting an application through its runtime requirements.
Don’t Download VCRUNTIME140.dll From a Random DLL Website
A common search for this error is:
“VCRUNTIME140.dll download”
That can lead to websites offering individual DLL files.
This isn’t the approach you should use first.
The Visual C++ Redistributable is the actual runtime package designed to provide the libraries applications need. Microsoft provides the supported packages directly.
Downloading a standalone DLL from an unknown source also creates unnecessary uncertainty about:
- Where the file came from
- Which version it is
- Whether its architecture is correct
- Whether it actually matches your application
- Whether the file has been modified
Instead of replacing one DLL manually, repair the runtime installation that provides it.
What About MSVCP140.dll?
You may encounter a similar error mentioning:
MSVCP140.dll
This is another Visual C++ runtime component.
If an application reports both VCRUNTIME140.dll and MSVCP140.dll as missing, installing or repairing the appropriate Visual C++ Redistributable is still the logical first step.
You generally don’t need to hunt down each DLL separately.
What About VCRUNTIME140_1.dll?
Another related message is:
VCRUNTIME140_1.dll was not found.
Although the filename is slightly different, the troubleshooting approach is similar.
Start by installing or repairing the appropriate current Visual C++ Redistributable. Make sure the package architecture matches the affected application.
If the application still fails after the runtime has been repaired, reinstall the application or check its official support documentation.
Do You Need to Install Every Visual C++ Version?
No.
You don’t need to download every Visual C++ Redistributable version you can find.
For the modern v14 runtime, Microsoft states that the latest Redistributable is binary compatible with applications built using Visual Studio 2015 and later supported MSVC toolsets, although older applications can have separate requirements.
The practical approach is:
Start with the current supported Redistributable.
If an older application specifically requires an older runtime, follow the software developer’s documented requirements.
Why Does the Error Appear After an Application Update?
Sometimes the error appears immediately after installing or updating a program.
That doesn’t necessarily mean Windows itself is broken.
An application may have been:
- Installed without its required runtime
- Updated incorrectly
- Built against a runtime that isn’t currently installed
- Installed alongside an incomplete dependency package
In these situations, repairing or installing the correct Visual C++ Redistributable can restore the missing dependency.
A Simple Troubleshooting Path
You don’t need to run ten different Windows repair commands immediately.
Use this order:
Step 1 — Install the current Microsoft Visual C++ Redistributable
Choose the architecture required by the application.
Step 2 — If you’re unsure, install both x64 and x86
This covers 64-bit and 32-bit applications on a typical 64-bit Windows 11 system.
Step 3 — Restart Windows
Then test the application again.
Step 4 — Repair Visual C++
If the runtime is already installed, use Modify → Repair.
Step 5 — Reinstall the affected application
If only one program continues to show the error, reinstall that program from its official source.
Step 6 — Check the application’s documentation
If the problem remains, look for the developer’s specific runtime requirements or support instructions.
This sequence keeps the troubleshooting focused on the most likely cause instead of changing unrelated Windows settings.
Frequently Asked Questions
Is VCRUNTIME140.dll part of Windows 11?
It is a Microsoft Visual C++ runtime component used by applications. It isn’t something you should normally obtain by manually downloading a DLL file.
Applications that depend on the runtime require the appropriate Visual C++ Redistributable to be installed.
Is VCRUNTIME140.dll safe?
The legitimate Microsoft runtime component is a normal software library used by applications.
The important distinction is where you obtain it. Use Microsoft’s official Visual C++ Redistributable rather than downloading a standalone DLL from an unknown website.
Why is VCRUNTIME140.dll missing if Visual C++ is installed?
The installed runtime may be the wrong architecture, damaged, incomplete, or otherwise unsuitable for the application.
Try repairing the existing Redistributable and make sure the application has the correct x86 or x64 runtime.
Should I install both x86 and x64?
If you’re running 64-bit Windows 11 and you’re unsure whether the affected application is 32-bit or 64-bit, installing both is a practical solution.
They support different application architectures.
Do I need to restart after installing Visual C++?
A restart is recommended. It gives Windows and the affected application a clean opportunity to load the newly installed runtime components.
Can I simply copy VCRUNTIME140.dll into System32?
It’s better not to.
Manually copying DLL files can leave you with the wrong version or architecture and doesn’t address the underlying runtime installation.
Install or repair the official Visual C++ Redistributable instead.
Final Takeaway
The “VCRUNTIME140.dll was not found” error in Windows 11 is usually a Visual C++ runtime dependency problem, not a reason to download a random DLL file.
Start with Microsoft’s current Visual C++ Redistributable:
Install the correct architecture → restart Windows → repair the package if necessary → reinstall the affected application if the problem continues.
For most 64-bit Windows 11 users who aren’t sure whether their application is 32-bit or 64-bit, installing both the x64 and x86 Redistributables provides the simplest way to cover both application types.
Get the latest supported Visual C++ Redistributable from Microsoft