Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If Windows says “VCRUNTIME140.dll was not found” or “The code execution cannot proceed because VCRUNTIME140 was not found,” install the official Microsoft Visual C++ Redistributable that matches the affected app’s architecture. Use x86 for a 32-bit app, x64 for a 64-bit app, or ARM64 for a native ARM64 app. Do not download a loose DLL from a mirror. The supported package supplies the runtime as a complete Microsoft component.
The current Visual C++ v14 Redistributable is the normal path for applications built with Visual Studio 2017, 2019, 2022 and 2026 on Windows 10 or Windows 11. If installation does not resolve the error, repair Windows component files with DISM followed by System File Checker (SFC); when only one game or program still fails, reinstall it from its official installer or contact its publisher.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Tech-Shop-pro Compatible with install Key Included USB For Windows 11 pro Email Delivery in 2 Hours... | $42.00 | Buy on Amazon |
| 2 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What does the VCRUNTIME140.dll error mean?
VCRUNTIME140.dll is a Microsoft C and C++ runtime library. Programs compiled with Microsoft Visual C++ can depend on that shared library instead of carrying every runtime file inside their own folder. Microsoft describes the Redistributable this way: “A Visual C++ Redistributable installs Microsoft C and C++ Runtime libraries.”
A missing-file dialog tells you that the application could not load a required runtime library. It does not, by itself, identify the cause. The package may never have been installed, its files may be damaged, the installed architecture may not match the application, or the program may require a particular deployment supplied by its publisher.
Popular on Amazon
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
- Delivery via Amazon messsges within 2 hours please send us a messge a soon as you buy so we can send it to you with in the time frame
The wording can vary slightly between Windows 10 and Windows 11 and between applications. Common examples include:
- “VCRUNTIME140.dll is missing from your computer.”
- “VCRUNTIME140.dll was not found.”
- “The code execution cannot proceed because VCRUNTIME140 was not found. Reinstalling the program may fix this problem.”
Although the message often appears when launching a game, the same runtime is used by utilities, creative applications and other Windows software. Fixing the shared runtime can therefore help more than one program, but a one-program failure may still be specific to that program’s installer.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Is downloading VCRUNTIME140.dll from a random website safe?
No. A standalone DLL-download mirror is not Microsoft’s documented remedy. A loose file can be the wrong architecture, an incompatible build, incomplete, modified or bundled with unwanted software. Copying it into a game folder can also hide the real installation problem and create a different error later.
Use Microsoft’s Latest Supported Visual C++ Redistributable Downloads page and the Windows repair tools instead. The official installer deploys the runtime as a coherent component and can maintain the files that applications expect. If a publisher supplies a runtime installer with its game, use that publisher’s official package or support instructions rather than replacing one DLL manually.
Which Visual C++ package does my game or app need?
The package architecture must match the application’s target architecture, not simply the edition of Windows installed on the computer. Microsoft states: “The redistributable package architecture must match your app’s target architecture.”
| Application target | Redistributable package | Practical example |
|---|---|---|
| 32-bit (x86) | x86 | A 32-bit game running on either 32-bit or 64-bit Windows needs the x86 runtime. |
| 64-bit (x64) | x64 | A native 64-bit game needs the x64 runtime. |
| Native ARM64 | ARM64 | An ARM64-native application needs the ARM64 runtime. |
On an ARM64 Windows device, Microsoft notes that the x64 package contains ARM64 and x64 binaries when installed on that device. The application’s target still determines which package is appropriate. If a 64-bit Windows PC runs both 32-bit and 64-bit programs, those programs can require different packages; install the architecture required by each affected application.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →How can I determine the application architecture?
Check the game or software publisher’s system requirements, installation notes or support article first. The publisher may identify the executable as 32-bit, 64-bit or ARM64 and may provide a specific runtime installer. If the documentation is silent, ask the publisher for the executable’s target architecture rather than guessing from the Windows edition.
For a game installed through a launcher, check the game’s own executable and support documentation, not the launcher alone. A 64-bit Windows installation does not make every game executable 64-bit.
How do I install the official Visual C++ Redistributable?
For most VCRUNTIME140.dll errors, installing the current supported v14 package is the first and most effective manual fix. Follow this sequence so that the source, architecture and restart are all handled correctly.
- Open Microsoft’s download page. In a browser, go to Microsoft’s Latest Supported Visual C++ Redistributable Downloads page. Select the package links published there, not a third-party DLL site.
- Choose the package that matches the app. Select x86 for a 32-bit application, x64 for a 64-bit application or ARM64 for a native ARM64 application. If you know that separate 32-bit and 64-bit applications are affected, obtain the corresponding packages for those applications.
- Download the latest supported v14 release. Microsoft recommends the current v14 Redistributable for applications built with Visual Studio 2017, 2019, 2022 or 2026. The current v14 release supports Windows 10 and Windows 11.
- Run the installer. Close the affected game or program, launch the downloaded Microsoft installer and follow its prompts. Allow the installer to finish; do not cancel it after it has begun replacing or adding runtime files.
- Restart if requested. A restart lets Windows and applications load the newly installed runtime cleanly. If the installer asks for a restart, choose it before testing the program.
- Launch the affected application again. Use the same shortcut or launcher that produced the error. If it opens normally, the missing runtime was the immediate cause.
The v14 family is an in-place cumulative update. Applications built with Visual Studio 2015 or later can use the latest Redistributable when its version is equal to or newer than the version of the build tools used to create the application. That is why installing the current supported v14 package is generally preferable to searching for an old VCRUNTIME140.dll file.
Free tools Windows power users keep installed
One-click scans. No signup required.
What if the installer says a newer version is already installed?
First verify that you selected the architecture required by the application. A newer x64 installation does not satisfy a 32-bit program that needs x86, and an x86 installation does not satisfy a native x64 program. On an ARM64 device, also follow the application’s target architecture and Microsoft’s package guidance.
If the correct package is present and the same application still reports VCRUNTIME140.dll, do not copy a replacement DLL into its folder. Continue with the Windows integrity checks below, then use the application’s official installer or support instructions. Microsoft notes that an application may require a particular runtime deployment chosen by its publisher.
How do I repair Windows system files with DISM and SFC?
Use this sequence when several applications fail, Windows components show related file errors, or the Redistributable installation appears damaged. Microsoft documents running Deployment Image Servicing and Management (DISM) first and System File Checker second. Both commands should be run from an elevated Command Prompt, and each operation must finish before the next begins.
- Open an elevated Command Prompt. Search for Command Prompt, choose the option to run it as administrator and approve the Windows permission prompt.
- Repair the Windows image. Enter the following command and press Enter:
DISM.exe /Online /Cleanup-image /RestorehealthWait for DISM to complete. Closing the window early can leave the repair unfinished.
- Check protected system files. After DISM finishes, enter:
sfc /scannowWait until SFC reaches 100 percent and reports its result. Microsoft describes SFC as a Windows tool that checks system files for corruption and helps fix problems that may cause Windows to malfunction.
- Restart Windows and test again. Reboot after both commands have completed, then open the affected application.
DISM and SFC address Windows component or system-file corruption; they do not replace an application’s own files. If the error remains limited to one game after these checks, move to that game’s official reinstall or support process.
Recommended Free Tools
What should I do if only one game or program still fails?
A single-application failure points toward that application’s installation, deployment choice or compatibility rather than a system-wide missing runtime. Microsoft directs users who are updating the runtime to fix an app to contact the app vendor because the application may require a particular runtime deployment.
Use the publisher’s installer
Download the latest installer or repair package from the game or software publisher’s official site or the software’s legitimate distribution channel. Follow its own repair or reinstall instructions. Do not substitute a DLL downloaded from another site.
Also popular on Amazon
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Record the exact failure
Keep the complete error text, the application name and version, your Windows edition, the package architecture you installed and the result of DISM and SFC. These details let the publisher distinguish a missing runtime from an application-specific deployment problem.
Escalate when the publisher requires a private runtime
Some applications deploy runtime files in an application-specific way or require a particular build. If the publisher’s support instructions name a different package or a bundled installer, follow those instructions even when the generic v14 package is already installed. The publisher is the authority for that program’s deployment requirements.
How do I tell whether the problem affects Windows or just one application?
Test deliberately rather than repeatedly reinstalling the same DLL. The pattern of failures determines the next step.
| Observed pattern | Most useful next action |
|---|---|
| One game or program shows VCRUNTIME140.dll; other software works | Install the matching official Redistributable, then use the affected application’s official installer or vendor support if it still fails. |
| Several unrelated programs show missing-runtime or other system-file errors | Install the matching v14 package and run DISM followed by sfc /scannow from an elevated Command Prompt. |
| A 32-bit program fails after only x64 was installed | Install the x86 package required by that 32-bit program. |
| A native ARM64 application fails on an ARM64 device | Use the ARM64 package and confirm the application’s deployment instructions. |
| The runtime installs successfully but the same app still fails | Stop replacing DLLs manually; reinstall the app from its official source or contact its publisher. |
Does the current v14 runtime replace every older Visual C++ package?
No. The current v14 family is the compatible path for supported applications built with Visual Studio 2017 through 2026. Microsoft records that Visual Studio 2015 support ended on October 15, 2025, while the v14 runtime remains the compatible path for supported applications.
Older 2013-and-earlier Redistributables remain side by side when legacy software requires them. Do not remove a legacy package solely because v14 is installed; an older application can depend on its own generation of runtime libraries. The practical rule is to install the latest supported package unless the application vendor explicitly requires a legacy runtime.
| Application build generation | Runtime guidance | Lifecycle note |
|---|---|---|
| Visual Studio 2017, 2019, 2022 or 2026 | Use the latest supported v14 Redistributable that matches the application architecture. | The current v14 release supports Windows 10 and Windows 11. |
| Visual Studio 2015 applications | Use the compatible v14 path unless the publisher specifies another deployment. | Visual Studio 2015 support ended October 15, 2025. |
| Visual Studio 2013 or earlier applications | Keep or install the legacy Redistributable generation required by the application. | These older Redistributables remain side by side when needed. |
What mistakes should I avoid while fixing VCRUNTIME140.dll?
- Do not use a DLL mirror. It is not the documented Microsoft remedy and may provide the wrong build or an unsafe file.
- Do not choose a package solely because Windows is 64-bit. The application target architecture controls the choice.
- Do not install only one architecture for a mixed software library. A 32-bit game and a 64-bit utility can require different runtime packages.
- Do not run SFC before DISM when following Microsoft’s repair sequence. Run
DISM.exe /Online /Cleanup-image /Restorehealth, wait for completion, then runsfc /scannow. - Do not assume the message proves malware or a failing hard drive. It identifies an unavailable runtime dependency, not the underlying reason it is unavailable.
- Do not delete older Redistributables indiscriminately. Legacy applications may still require 2013-or-earlier packages side by side with v14.
- Do not keep reinstalling the runtime when one application alone fails. After the correct package and Windows integrity checks, use that application’s official installer or support channel.
What should I check after the repair?
Confirm that Windows was restarted when requested, then launch the exact program that displayed the message. If it opens, test the feature that previously failed, such as loading a saved game or entering the main menu. If another application now displays a different missing-file message, record that exact filename rather than substituting VCRUNTIME140.dll; each runtime error can identify a different dependency.
If the same message returns, note whether it appears immediately at launch, after an application update or only for one user account. Provide those observations, the package architecture, the Windows version and the DISM/SFC results to the publisher’s support team. That information is more useful than sending an unverified DLL file.
As an optional shortcut after these manual checks, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared-DLL problems, on Windows 11, 10, 8 and 7. It complements antivirus software rather than replacing it; its free trial lasts at least two days before a subscription, results vary, and no tool repairs every crash.
Frequently asked questions
Can I copy VCRUNTIME140.dll from another Windows computer?
That is not a reliable repair. The other computer may have a different architecture, runtime build or servicing state, and copying one file does not install the rest of the Microsoft runtime component. Use the official Redistributable package so the complete, matching library set is installed.
Why did the error appear after a game update?
An update can change the executable or its runtime deployment requirements. Recheck the updated game’s official support notes and architecture, then install the package they specify; if the general v14 package is already correct, the publisher may need to repair or redeploy files through its own installer.
Can I remove the Visual C++ Redistributable after the game starts?
No. The game may need the runtime every time it launches, and other applications can depend on the same shared libraries. Leave the package installed unless you are following a documented uninstall or migration procedure from the application publisher.
What information should I include in a support request?
Include the exact error wording and DLL name, the game or program version, Windows 10 or 11 edition, whether the app is x86, x64 or ARM64, which Redistributable package you installed, and whether DISM and SFC completed. Also state whether other applications fail or only one program does; that distinction helps support identify a system-wide runtime problem versus an application-specific deployment issue.
Frequently Asked Questions
Can I copy VCRUNTIME140.dll from another Windows computer?
That is not a reliable repair. The other computer may have a different architecture, runtime build or servicing state, and copying one file does not install the rest of the Microsoft runtime component. Use the official Redistributable package so the complete, matching library set is installed.
Why did the error appear after a game update?
An update can change the executable or its runtime deployment requirements. Recheck the updated game’s official support notes and architecture, then install the package they specify; if the general v14 package is already correct, the publisher may need to repair or redeploy files through its own installer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can I remove the Visual C++ Redistributable after the game starts?
No. The game may need the runtime every time it launches, and other applications can depend on the same shared libraries. Leave the package installed unless you are following a documented uninstall or migration procedure from the application publisher.
What information should I include in a support request?
Include the exact error wording and DLL name, the game or program version, Windows 10 or 11 edition, whether the app is x86, x64 or ARM64, which Redistributable package you installed, and whether DISM and SFC completed. Also state whether other applications fail or only one program does; that distinction helps support identify a system-wide runtime problem versus an application-specific deployment issue.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
