You're trying to launch a game or maybe just open Photoshop to get some work done, and suddenly a gray box pops up. It tells you msvcp140.dll was not found. It's annoying. It feels like your computer is falling apart, but honestly, it’s just a missing link in a chain of code.
Windows is a massive ecosystem of shared files. Instead of every single app carrying its own heavy luggage, they share libraries. These are Dynamic Link Libraries (DLLs). Think of it like a public library where different programs "check out" the tools they need to run. When that specific file goes missing or gets corrupted, the program basically forgets how to function. It panics and shuts down.
The msvcp140.dll file is part of the Microsoft Visual C++ Redistributable for Visual Studio 2015. If you don't have this specific package installed, or if a recent update bumped something out of place, you're stuck. You'll see this error most often with gaming platforms like Steam or Epic Games, and creative suites like Adobe. It’s one of the most common hiccups in modern computing because so many developers rely on Microsoft's C++ libraries to build their software.
Why msvcp140.dll was not found happens in the first place
It's usually a mess-up during an installation. Sometimes, you install a new game and the installer is supposed to include these "redistributables," but it skips them. Or maybe your antivirus got a little too aggressive. Security software sometimes flags DLLs as false positives and tosses them into quarantine because they interact with the system core.
Don't go downloading random DLL files from "fix-it" websites. Seriously. That is the fastest way to get malware. Those sites often host outdated or tampered files that can open a backdoor into your OS. If you need the file, get it from the source: Microsoft.
Another culprit is a botched Windows Update. Sometimes the system tries to update the C++ libraries and hits a snag, leaving the file half-written or entirely gone. It’s a classic "too many cooks in the kitchen" situation.
The right way to fix the missing file error
The most reliable fix—the one that actually works 90% of the time—is reinstalling the Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022. Microsoft combined these into one single package recently to make things easier.
Go to the official Microsoft Download Center. You’ll see two versions: x86 and x64. If you’re on a 64-bit version of Windows, which you almost certainly are if your computer was made in the last decade, you actually need both. People often make the mistake of only installing the 64-bit version. But many apps are still built on 32-bit architecture, and they specifically look for the x86 version of msvcp140.dll. Install both, restart your machine, and usually, the problem vanishes.
What if the redistributable is already there?
If you check your "Apps & Features" and see it listed, don't just assume it’s working. It could be corrupted. You can try the "Repair" function. Click the three dots next to the Microsoft Visual C++ entry, hit "Modify," and then choose "Repair." It’s basically a self-healing process where Windows checks for missing bits and pieces.
The "System File Checker" trick
Sometimes the issue isn't the C++ package at all, but the underlying health of your Windows installation. There’s a built-in tool called SFC (System File Checker). It's a bit old-school, but it works.
Open your Command Prompt as an administrator. Type sfc /scannow and hit Enter. Windows will start crawling through your system files like a digital janitor. If it finds that msvcp140.dll is missing or looks "wrong," it will attempt to replace it from a local cached copy. It takes about ten minutes. Grab a coffee while it runs.
📖 Related: Fire Stick User Guide: What Most People Get Wrong About Setting Up Their Streamer
Common myths about DLL errors
People will tell you to copy-paste the DLL from another computer. Don't do that. DLLs are version-specific. If you grab a version of msvcp140.dll from a friend running an older version of Windows, or even a different build of the redistributable, your app might launch but then crash randomly when it tries to call a function that doesn't exist in that specific version.
Another myth? Reinstalling the entire game or app. While this can work if the app’s installer is smart enough to detect the missing library, it’s often a waste of time. If the issue is with the Windows-level library, reinstalling the app won't help because the app assumes the OS has its act together.
Dealing with the "vcrruntime140.dll" cousin
Often, when you see msvcp140.dll was not found, its twin sibling vcrruntime140.dll isn't far behind. They are both part of the same Visual C++ runtime environment. If you're missing one, there's a high chance the other is missing too. Fixing the C++ Redistributable package handles both at once, so you don't have to play whack-a-mole with individual files.
What to do when nothing works
If you've reinstalled the redistributables and ran SFC, and it's still yelling at you, it might be a registry issue. I usually shy away from suggesting registry cleaners because they can be sketchy. Instead, check for pending Windows Updates. Sometimes a "Feature Update" is hanging in the background and has locked certain system folders, preventing new DLLs from being registered correctly.
Check your Quarantine folder in your antivirus too. If you see msvcp140.dll sitting in there, tell your antivirus to "Restore and Exclude." It’s rare, but it happens, especially with smaller indie games that use non-standard wrappers.
Actionable steps for a permanent fix
First, head to the Microsoft website and search for "Latest supported Visual C++ Redistributable downloads." Download the vc_redist.x86.exe and vc_redist.x64.exe files. Run them both. If they ask to "Repair" or "Install," go with it.
Next, perform a cold reboot. Don't just hit "Sleep." Actually shut down the computer and turn it back on. This clears the memory and forces Windows to re-index the newly installed libraries.
Finally, if the error persists for only one specific app, check the "Bin" or "System" folder inside that app’s installation directory. Some programs expect the DLL to be right there next to the .exe file rather than in the C:\Windows\System32 folder. If the folder is empty, you might need to verify the integrity of the game files through Steam or the Epic Games Launcher. This will force the launcher to download just the missing dependencies without a full re-install.
Keeping these libraries updated is a boring part of PC maintenance, but it’s what keeps the machine running smoothly. Most of the time, the fix is just a couple of clicks away on a Microsoft support page.
Next steps: Verify your Windows version (32-bit or 64-bit) in the "About your PC" settings. Ensure you have the 2015-2022 multi-year redistributable package installed for both architectures to cover all your software needs. If the error occurred after a recent driver update, consider rolling back that specific driver to see if a conflict was introduced.