Install the right Microsoft Visual C++ Redistributable before blaming the app. Many Windows programs need these tiny runtime packages to start. Microsoft says the latest supported packages install runtime components for apps built with Microsoft C and C++ tools [source: Microsoft]. When one is missing, Windows may throw a scary error like VCRUNTIME140.dll was not found.
TLDR: Microsoft Visual C++ Redistributables are shared helper files for Windows apps. If a game, printer tool, or business app fails to open, install both the x64 and x86 versions for the matching year. For example, a 64 bit PC can still need the 32 bit package if the app is 32 bit. In many support cases, checking Event Viewer first can cut a 30 minute guessing session down to about 5 minutes.
What are Visual C++ Redistributables?
Think of them as kitchen tools.
Your app is the chef. The redistributable is the pan, knife, and stove. If the chef shows up and the stove is gone, nothing cooks.
These packages include files like:
- VCRUNTIME140.dll
- MSVCP140.dll
- concrt140.dll
- vcruntime140_1.dll
Apps built with Visual C++ often expect these files to exist on Windows. Some installers include them. Some do not. Honestly, it feels like every third old app assumes your PC is a museum with every runtime ever made.
Why the error happens
Missing runtime errors usually come from one of these things:
- The Redistributable was never installed.
- The wrong bit version was installed.
- The app needs an older runtime.
- A file is damaged.
- The app folder contains a bad copy of a DLL.
The bit version part bites people a lot.
A 64 bit Windows PC can run 32 bit apps. So you may need x86 runtimes even on a shiny 64 bit machine. That sounds silly. It is also true.
Start with the easy fix
Go to Microsoft’s official Visual C++ Redistributable page. Download the latest supported packages. Install both:
- vc_redist.x64.exe for 64 bit apps.
- vc_redist.x86.exe for 32 bit apps.
Restart the app. Not always the PC. Just the app first.
If it opens, great. You win. Go get coffee.
If it still fails, keep reading. This is where the detective hat comes out.
Use Dependencies to find missing files
Dependencies is a free tool that shows what DLL files an EXE needs. It is like an X ray for Windows apps. The modern project is available on GitHub [source: GitHub].
Here is the simple flow:
- Open Dependencies.
- Drag the app’s .exe file into it.
- Wait for the scan.
- Look for red or warning items.
- Search the missing DLL name.
If you see VCRUNTIME140.dll or MSVCP140.dll, that points to a Visual C++ runtime issue.
If you see a weird vendor DLL, the app itself may be broken. In that case, reinstall the app.
Do not download random DLL files from random websites. That is how small problems become spicy malware stories.
Use Event Viewer when the error is vague
Sometimes Windows says nothing useful. The app just blinks and dies. Great. Thanks, Windows.
This is when Event Viewer helps.
Open it like this:
- Press Windows + R.
- Type eventvwr.msc.
- Press Enter.
- Open Windows Logs.
- Click Application.
Now try to start the broken app again. Then refresh Event Viewer.
Look for recent entries named:
- Application Error
- SideBySide
- Windows Error Reporting
SideBySide is the juicy one. It often points to missing or mismatched runtime files. Event ID 33 is a common clue for side by side configuration trouble.
Open the event. Read the text. Yes, it looks like robot soup. Still, scan for file names, version numbers, and phrases like dependent assembly.
It drives me crazy that the useful line is often buried near the bottom. Expect to spend 20 seconds squinting.
Match the runtime to the app
Visual C++ runtimes come by version. Common groups include:
- 2005
- 2008
- 2010
- 2012
- 2013
- 2015 to 2022
The 2015, 2017, 2019, and 2022 runtimes are usually covered by the latest 2015 to 2022 package. Older apps may still need older packages.
Yes, you can have many installed at once. That is normal. Do not uninstall them just because the list looks messy.
Quick repair checklist
- Install both x64 and x86 latest Visual C++ packages.
- Restart the broken app.
- Run Dependencies on the EXE.
- Check Event Viewer under Application logs.
- Search for missing DLL names.
- Repair or reinstall the app if vendor DLLs are missing.
- Avoid random DLL download sites.
The simple rule
If the error mentions VCRUNTIME, MSVCP, or SideBySide, think Visual C++ first.
Install the official runtimes. Check the app with Dependencies. Confirm the crash in Event Viewer. That small routine solves a huge number of “this app will not open” mysteries.
And best of all, you do not need to be a Windows wizard. You just need the right clues.
