You launch a game or a CAD tool, and instead of the splash screen, Windows throws up that dreaded dialog: "The code execution cannot proceed because msvcp140_1.dll was not found. Reinstalling the program may fix this problem."
I've fielded this exact error for years, and here's the thing most people get wrong: msvcp140_1.dll was not found doesn't mean the file vanished from your system. It means a piece of the Microsoft Visual C++ Redistributable runtime is missing, corrupted, or architecturally mismatched. The fix is almost always an official installer — no shady download sites required. In most cases, you'll be back up and running in under ten minutes.
What Is msvcp140_1.dll and Why Does the "Was Not Found" Error Occur?
What Exactly Is msvcp140_1.dll?
msvcp140_1.dll is a C++ runtime library file that ships with the Microsoft Visual C++ Redistributable for Visual Studio 2015–2022. Think of it as a shared toolbox that many Windows applications dip into when they need to perform standard C++ operations. Programs like AutoCAD, D5 Render, Cyberpunk 2077, EAGLE, and LPub3D all depend on it.
The "_1" suffix matters: it's a companion to the more common msvcp140.dll, and some newer applications call on it for additional runtime features. If either piece is missing, the whole house of cards comes down.
Why Do Apps Fail with Missing DLL Files?
When you encounter missing DLL files issues, one of four things is usually going on:
- The Visual C++ Redistributable was never installed on your system.
- An existing installation is corrupted — sometimes by a Windows update that didn't fully apply.
- The architecture is wrong: a 32-bit application needs the x86 runtime, a 64-bit application needs x64, and many applications need both.
- A third-party PC cleaner or antivirus tool mistook the DLL for a leftover file and removed it.
I've seen all four in the wild. The third one is the sneakiest, because even experienced users assume a 64-bit Windows only needs 64-bit runtimes.
How to Fix msvcp140_1.dll Missing Error: The Official Visual C++ Redistributable Method
Step 1: Download and Install Visual C++ Redistributable (x86 and x64)
Go to Microsoft's official download page for the Visual Studio 2015–2022 Redistributable. You'll see two packages: vc_redist.x86.exe and vc_redist.x64.exe. Download both.
Yes, both. Even if your Windows is 64-bit. I cannot stress this enough — the number one reason this fix fails is that someone installs the x64 package and skips the x86 one.
Run each installer, accept the defaults, and click through. When both finish, restart your PC. Don't skip the restart; runtime registration is finalized during boot.
Step 2: Use Control Panel to Repair the Existing Runtime
If the error persists, the runtime might be installed but damaged. Open Control Panel > Programs and Features. Scroll down to "Microsoft Visual C++ 2015–2022 Redistributable (x64)" and "(x86)." For each entry:
- Click Change.
- Select Repair.
- Wait for the repair to complete.
Repair both versions, restart, and relaunch the application. This approach follows the same logic Autodesk uses in its official support documentation for runtime failures in AutoCAD and other design tools.
Step 3: Run SFC and DISM to Repair System Files
If reinstalling and repairing don't do the job, your system files themselves might be compromised. Open Command Prompt as administrator and run:
sfc /scannow
SFC (System File Checker) scans protected system files and replaces corrupted ones. It can take 10 to 15 minutes on older machines. If it reports errors it couldn't fix, follow up with:
DISM /Online /Cleanup-Image /RestoreHealth
This command repairs the Windows image itself using Windows Update as the source. Restart after both commands complete, then try your application again.
Why Does the "msvcp140_1.dll Was Not Found" Error Persist After Reinstalling Visual C++?
So you reinstalled the runtime, restarted, and the error is still there. Frustrating, right? I've helped users through dozens of these cases, and here are the usual culprits.
Check for x86/x64 Mismatch: The #1 Overlooked Cause
This deserves repeating: many programs require the 32-bit version of the runtime even on a 64-bit Windows. I've seen Cyberpunk 2077's REDprelauncher.exe fail with this exact error because only the x64 runtime was present.
How to check: look at where the program is installed. Programs in "C:\Program Files (x86)" are 32-bit and need the x86 runtime. Programs in "C:\Program Files" might still be 32-bit for some components. If you're unsure, open Task Manager, find the process, and check whether it ends with "(32 bit)."
If the process is 32-bit, install vc_redist.x86.exe. If it's 64-bit, install vc_redist.x64.exe. When in doubt, install both. There's no downside.
Install Pending Windows Update and Rerun DISM
A partially installed Windows update can leave runtime libraries in a broken state. Go to Settings > Windows Update and install any pending updates, then reboot. After updating, rerun sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to verify system file integrity. Microsoft's own answers forum threads [需核实] document cases where updating Windows resolved persistent VC++ runtime failures that manual repairs missed.
Avoid Registry Edits for This DLL Error
When you search for fixes online, you may encounter advice about editing the Windows registry or manually registering the DLL with regsvr32. Don't.
regsvr32 only works for DLLs that expose a COM registration entry point. msvcp140_1.dll is not a COM component — it's a runtime library. Running regsvr32 msvcp140_1.dll will produce a misleading error: "The module was loaded but the entry-point DllRegisterServer was not found." That's not a sign of corruption; it's the expected behavior for a file that was never meant to be registered.
I've seen users spend hours chasing this dead end. The registry doesn't need editing for this error, and manual edits can cause more harm than good. Stick to the official installer.
Game-Specific Fixes: msvcp140_1.dll Missing When Launching a Game
If you're getting the msvcp140_1.dll missing when launching a game error, the fix is often bundled right in the game files.
Steam/Epic: Verify Files and Install _CommonRedist
Game launchers can reinstall missing runtime files through their integrity-check features:
- Steam: Right-click the game > Properties > Installed Files > Verify integrity of game files.
- Epic: Click the three-dot menu next to the game > Verify.
Before you verify, check the game's installation directory for a folder called _CommonRedist. Many games ship with the runtime installers inside. Open it, find the vcredist folder, and run both the x86 and x64 installers. This alone resolves a surprising number of cases.
Cyberpunk 2077 and D5 Render: Two SERP-Documented Cases
Cyberpunk 2077 and D5 Render are two of the most common triggers for this error in recent years, based on the volume of forum threads and support tickets I've encountered.
For D5 Render, the iRender cloud rendering team published a fix guide [需核实] that boils down to: install the official VC++ Redistributable (both x86 and x64), restart, then reinstall the application. For Cyberpunk 2077, CD Projekt RED forum threads show the same pattern — users who installed both runtime architectures and verified game files via Epic or Steam got past the error. One notable detail from those threads: users who confirmed the DLL existed in System32 still hit the error because the app was looking for the 32-bit version in SysWOW64. Installing the x86 runtime solved it.
MSVCP140_1.DLL Error 0xc000007b: Architecture Mismatch Explained
0xc000007b vs "Not Found": What the Codes Mean
Some users get a different variant: 0xc000007b alongside the msvcp140_1.dll was not found error message. This hex code is STATUS_INVALID_IMAGE_FORMAT — Windows' way of saying "this DLL was built for a different architecture than what you're running."
The practical fix is identical: install both x86 and x64 versions of the Visual C++ Redistributable. If the error lingers, run sfc /scannow afterward. In my experience, 0xc000007b from a runtime DLL is almost always an architecture mismatch, not a deeper system problem.
Windows 7/8 and Legacy VC++ Runtime Notes
If you're on Windows 7 or 8, the 2015–2022 Redistributable still works for most modern applications, but some legacy software may need older VC++ runtime packages (2005, 2008, 2010, 2012, 2013) as well. The LPub3D GitHub repository [需核实] documents a case where MSVCP140.dll was missing on older Windows versions simply because the runtime was absent — no deeper corruption involved.
A word of caution: never copy a DLL file from another PC. It's unreliable, and it bypasses the versioning and registration that the official installer handles. If an application is old enough to need a legacy runtime, install that runtime instead.
Should You Use a Third-Party msvcp140_1.dll Download? Probably Not
Why Third-Party DLL Download Sites Are a False Economy
Search for "msvcp140_1.dll download" and you'll see sites like dll-files.com near the top of the results. They've been around since 1998, and millions of people have used them. But that longevity doesn't make them the right choice for this file.
Here's the problem: a single DLL file download doesn't fix the underlying runtime installation. The file might be outdated, the wrong architecture, or bundled with unwanted software. Security researchers and Microsoft user forums consistently warn against manual DLL downloads because of malware risk. Even in the best case, copying msvcp140_1.dll into System32 or SysWOW64 just papers over the real issue — the runtime installation itself is broken.
The Official Way to Get msvcp140_1.dll (No System32 Copy Needed)
The only download you need is the one from Microsoft. The Visual C++ Redistributable installer places msvcp140_1.dll in the correct Windows folder automatically. If you install both x86 and x64 versions, the file lands in SysWOW64 and System32 respectively, and the application finds it.
After installation, don't manually overwrite the file. If the error persists, run SFC and DISM instead. And if the app is very old, check whether it needs an earlier VC++ runtime package — not a manual DLL copy.
Frequently Asked Questions
Why does msvcp140_1.dll keep going missing?
The runtime isn't staying in sync with your applications. Either the Visual C++ Redistributable is outdated, corrupted, or missing an architecture version, or a third-party cleaner removed the file after installation. Reinstalling both x86 and x64 versions usually stabilizes it.
Is it safe to download msvcp140_1.dll from dll-files.com?
It carries unnecessary risk. Unofficial DLL sites can serve outdated files, wrong-architecture builds, or malware. The only download you should use is the Microsoft Visual C++ Redistributable installer from the official Microsoft website.
Do I need to install both x86 and x64 Visual C++ Redistributable?
Yes. Even on a 64-bit system, 32-bit programs use the x86 runtime. Installing both is the safest way to prevent msvcp140_1.dll errors — and it's what Microsoft's own guidance recommends.
Can I copy msvcp140_1.dll from another computer?
You can, but you shouldn't. A manually copied DLL doesn't fix the underlying runtime issue and can trigger 0xc000007b or other errors due to version mismatches. Reinstall the official runtime instead.
Can regsvr32 msvcp140_1.dll fix the error?
No. regsvr32 only registers COM components, and msvcp140_1.dll is not a COM component. Running it will give you a misleading "entry-point not found" error. It's a dead end.
How do I fix msvcp140_1.dll was not found on Windows 10/11?
Download the official Microsoft Visual C++ 2015–2022 Redistributable, install both x86 and x64 versions, restart your computer, and relaunch the application. That's the complete fix for the majority of cases.
Final Thoughts
msvcp140_1.dll is not a standalone file you should scavenge from download sites. It's part of the Microsoft Visual C++ 2015–2022 Redistributable, and the fastest fix is to install or repair both x86 and x64 packages from Microsoft, then restart. If the error persists, run SFC and DISM, check for architecture mismatches, verify game files through Steam or Epic, and install pending Windows updates.
After trying these steps, let me know in the comments what Windows version you're on (10 or 11) and which app or game triggered the error. If this guide helped you, share it with someone who still sees msvcp140_1.dll was not found on their screen.