The short answer
Repair the complete v14 runtime for the app version and architecture. If the app bundles these files, use vendor verification or repair to restore a consistent dependency set.
Common symptoms
Match the complete error before following the checks:
- Launching reports that MSVCP140_1.dll / MSVCP140_2.dll cannot be found.
- Reinstalling the application still leaves it exiting before loading.
- Mixing MSVCP140-family versions can turn a missing-file error into an entry-point error. Do not download, rename or replace these files individually.

What causes MSVCP140_1.dll / MSVCP140_2.dll
The same message can have different causes. Check Windows version, application architecture and logs.
Repair steps
Follow these 4 steps in order, starting with the simplest checks.
Identify the application architecture and Windows version
Difficulty: Easy5–10 minCheck the vendor's requirements for x86, x64 or ARM64. A 32-bit application on 64-bit Windows still needs the x86 runtime. Select packages for the application, not just the operating system.
You have recorded Windows version, application architecture and the exact missing filename.
Install or repair Visual C++ v14
Difficulty: Easy5–10 minSelect a Microsoft v14 package that supports your Windows version and meets the application's version requirement. Match the application architecture and choose Repair if installed. Do not remove all runtimes to install an older package.
Read Microsoft's official guidanceSetup finishes successfully. Restart if requested, then test. Record any setup error code.
Check versions and the loaded copy
Difficulty: Easy5–10 minMixing MSVCP140-family versions can turn a missing-file error into an entry-point error. Do not download, rename or replace these files individually.
No system DLLs were overwritten; vendor-supplied dependencies in the game folder were repaired through the original installer.
Verify application files and test again
Difficulty: Easy5–10 minVerify files in the original game launcher or use the vendor's repair installer. Keep saves and settings, launch the same application through its original launcher and record any new error.
File verification completes and both launcher and application open. If the message changes, investigate the new filename.
Verify the fix
Verify with the same application and launch method that originally failed:
Frequently asked questions
Can I rename MSVCP140.dll to _2?
No. They export different functionality; similar names do not make them interchangeable.
Why is a dependency still missing after installing x64?
The launcher, plugins and main program can use different architectures. Check each against vendor requirements; 32-bit dependencies need the x86 package.
Can I copy a downloaded DLL into System32?
Use the complete Microsoft or application-vendor installer. A loose DLL can have the wrong architecture, version or origin and does not restore its dependencies. Do not overwrite system-directory files.

