vcruntime140_1.dll not found: why 64-bit programs need it and how to get it back
vcruntime140_1.dll is a small companion of vcruntime140.dll in Microsoft's Visual C++ runtime. It holds the newer C++ exception handler that 64-bit programs built with Visual Studio 2019 or later call, and it exists only as a 64-bit file. Windows does not include it, so the fix is the current x64 Visual C++ Redistributable from Microsoft, not a loose DLL.
Prefer to fix it yourself? The manual steps follow.
Download vcruntime140_1.dll the official way
14.51.36247.0Install the current Microsoft Visual C++ Redistributable for x64 (version 14.51.36247.0). It writes vcruntime140_1.dll into C:\Windows\System32 together with vcruntime140.dll, which it cannot work without, and registers both so that later updates and repairs keep them current.
Only the x64 package matters for this file. Microsoft never built a 32-bit vcruntime140_1.dll, because 32-bit programs handle C++ exceptions differently and never ask for it, so the x86 package does not contain it. On a Windows on ARM laptop install the ARM64 package from Microsoft's download page: the vcruntime140_1.dll inside it is the same x64 file, used by 64-bit Intel and AMD programs that run there under emulation.
“DLL files only” is for a 64-bit program that expects the runtime in its own folder, or a PC where the installer refuses to run: vcruntime140_1.dll together with vcruntime140.dll, msvcp140.dll and the other files of the same x64 package (version 14.51.36247.0), unpacked unchanged from Microsoft's installer. A free uGetFix account is needed to download. Sign in, or create one in a minute, and you return straight to this page.
We downloaded the x64 installer from Microsoft on October 14, 2026 and unpacked it to read the files inside. The download page shows its size and SHA-256 checksum, so you can compare the file you receive. The installer comes from Microsoft's own server (aka.ms).
Step by step
- Find the x64 runtime in your apps list. Open Settings, Apps, Installed apps and type “Visual C++” in the search box. The entry you need is “Microsoft Visual C++ 2015-2022 Redistributable (x64)” or “Microsoft Visual C++ v14 Redistributable (x64)”. Note its version number.
- Not listed: install it. Run the x64 installer from the link above, accept the licence and start the program again. If you also see the error for other programs, install the x86 package as well; it does not add vcruntime140_1.dll, but 32-bit programs need the rest of the runtime.
- Listed with an old version: update it. A 2015 or 2017 redistributable predates vcruntime140_1.dll and does not contain it. Running the current x64 installer over it upgrades the package in place and adds the file. Nothing needs to be removed first.
- Listed and current: repair it. Open the menu next to the x64 entry, choose Modify, then Repair. The repair writes fresh copies of vcruntime140_1.dll and vcruntime140.dll into System32. Restart if the installer asks you to.
- One program still fails: look in its folder. A program can keep its own vcruntime140_1.dll next to its .exe, and Windows loads that copy before the one in System32. If it is damaged or out of date the error stays. Reinstall the program, or in Steam open Properties, Installed files, Verify integrity of game files.
What not to do
Do not fetch vcruntime140_1.dll from a DLL download site.
A loose file comes without the matching vcruntime140.dll, nothing updates it later, and you cannot tell whose build it is. Sites that offer a “32-bit” vcruntime140_1.dll are offering a file Microsoft never made. If a program needs the files in its own folder, use “DLL files only” above; to judge a copy you already have, use the checker below.
Do not put it into SysWOW64.
SysWOW64 holds 32-bit files. A 64-bit vcruntime140_1.dll there is never used by anything, and a 32-bit program will not look for it anyway. The genuine file belongs in System32 only, and the installer puts it there.
Do not copy it into System32 by hand.
The installer does not know about a file you placed yourself. The next update or repair may skip it, and you keep a mismatched pair: a vcruntime140_1.dll from one version next to a vcruntime140.dll from another.
Do not run regsvr32 on it.
vcruntime140_1.dll is a plain function library with three exports and no registration entry point. regsvr32 only answers with another error, and registering it fixes nothing.
Do not delete the other copies you find.
Windows apps and many programs bundle a private vcruntime140_1.dll. Winbindex lists 88 distinct builds of the file inside Windows images and updates, in 19 versions. They belong to their programs; removing one breaks that program, not the error.
Check the copy on your PC
Choose the vcruntime140_1.dll you have. Its checksums are calculated in your browser and compared with 96 builds we know: the file from the current official redistributable, the copies indexed from Windows images and the older versions found on PCs.
The file stays on your computer. Nothing is uploaded: the checksum is computed locally.
1 genuine programs have been documented loading a planted copy of vcruntime140_1.dll. Found a vcruntime140_1.dll in Downloads, Temp, ProgramData or beside a program you never installed? That is a security question rather than a missing-file one. How to tell if vcruntime140_1.dll is malware, on 2-Spyware
The error messages and what each one means
A missing vcruntime140_1.dll always comes from a 64-bit program. The exact wording tells you whether the file is absent, unusable, or only the place where a program crashed.
The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem.
The wording of Windows 10 and Windows 11. The program was built with Visual Studio 2019 or later and the PC has no x64 runtime, or one too old to contain this file. vcruntime140.dll is often present at the same time. Install the current x64 package.
The program can't start because VCRUNTIME140_1.dll is missing from your computer. Try reinstalling the program to fix this problem.
The same situation in the older wording of Windows 7 and 8. The fix is the same: the current x64 redistributable.
VCRUNTIME140_1.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.
A file with that name was found but could not be loaded: it is empty, damaged, or not a genuine 64-bit build. This is typical after a copy from a DLL site. Repair the x64 redistributable, delete any stray copy in the program's folder and reinstall that program.
The application was unable to start correctly (0xc000007b). Click OK to close the application.
A mix of 32-bit and 64-bit files. With this file it usually means a 32-bit vcruntime140.dll or vcruntime140_1.dll was placed where a 64-bit program loads it, most often in the program's own folder. Remove hand-copied runtime files there and repair both packages.
Faulting module name: VCRUNTIME140_1.dll
A line in the Application log of Event Viewer after a crash. The file loaded fine. Because it handles C++ exceptions, it is the module on duty when a program fails on an error it did not catch, so the cause is nearly always the program. Update the program first, then install the current x64 runtime.
File facts for the current official version
Read from the file inside Microsoft's x64 installer, version 14.51.36247.0. Microsoft® C Runtime Library, Microsoft Corporation.
| Build | Version | Size | Exported functions | Signed by |
|---|---|---|---|---|
| x64 | 14.51.36247.0 | 50,112 bytes | 3 | Microsoft Windows Software Compatibility Publisher |
- SHA-256 · x64
a7146c08f89fe5b04541ab507cdb59ff7b44534d4ba3c668a426c6450a03434e
- Where the genuine vcruntime140_1.dll belongs
C:\Windows\System32C:\Windows\SysWOW64- Signed by
- Microsoft Windows Software Compatibility Publisher: Properties, Digital Signatures shows it.
After installation the file is in C:\Windows\System32 and nowhere else: there is no 32-bit copy for SysWOW64. Its three exported functions are the frame handler __CxxFrameHandler4 and two helpers it uses. Visual Studio 2019 made this handler the default for 64-bit code because it stores the data for C++ exceptions in far less space, which keeps 64-bit programs smaller. Every program compiled that way names vcruntime140_1.dll in its import table.
What vcruntime140_1.dll itself depends on
vcruntime140_1.dll does not stand alone. Its import table names VCRUNTIME140.dll, so Windows must load the matching vcruntime140.dll first. If that file is missing too, the next error after copying vcruntime140_1.dll by hand names vcruntime140.dll. The redistributable installs both at once and keeps their versions in step.
Below them there is only Windows: three files of the Universal C Runtime (heap, runtime and string functions) and KERNEL32.dll. If an error names one of the api-ms-win-crt files instead, the gap is in Windows, not in the Visual C++ package.
VCRUNTIME140.dllapi-ms-win-crt-heap-l1-1-0.dllapi-ms-win-crt-runtime-l1-1-0.dllapi-ms-win-crt-string-l1-1-0.dllKERNEL32.dllThe api-ms-win-crt files belong to the Universal C Runtime, which is part of Windows 10 and Windows 11 and is kept up to date by Windows Update. The highlighted file comes from the same redistributable as vcruntime140_1.dll.
What the redistributable installs
The runtime files of the x64 installer, version 14.51.36247.0: 12 files that are installed and updated together. vcruntime140_1.dll is one of the smallest of them, and the x86 installer has the same set without it.
| File | Microsoft's description | Size |
|---|---|---|
concrt140.dll | Microsoft® Concurrency Runtime Library | 365 KB |
msvcp140.dll | Microsoft® C Runtime Library | 628 KB |
msvcp140_1.dll | Microsoft® C Runtime Library _1 | 35 KB |
msvcp140_2.dll | Microsoft® C Runtime Library _2 | 268 KB |
msvcp140_atomic_wait.dll | Microsoft® C Runtime Library _atomic_wait | 56 KB |
msvcp140_codecvt_ids.dll | Microsoft® C Runtime Library _codecvt_ids | 30 KB |
vcamp140.dll | Microsoft® C++ AMP Runtime | 408 KB |
vccorlib140.dll | Microsoft ® VC WinRT core library | 342 KB |
vcomp140.dll | Microsoft® C/C++ OpenMP Runtime | 208 KB |
vcruntime140.dll | Microsoft® C Runtime Library | 174 KB |
vcruntime140_1.dll | Microsoft® C Runtime Library | 49 KB |
vcruntime140_threads.dll | Microsoft® C Runtime Library | 38 KB |
Older versions of vcruntime140_1.dll found on PCs
Games and installers often put their own vcruntime140_1.dll into their folder, and those copies stay long after Microsoft has released a newer runtime. A public DLL catalogue has collected 7 such copies, from version 14.22.27821.0 to 14.27.29111.0. The table lists each one with its checksums, so you can tell which you have.
The redistributable above installs 14.51.36247.0. If the check on this page finds your file in this list, it is most likely an older Microsoft build; confirm the Microsoft signature, because the list itself is not verified. Any entry that claims to be a 32-bit build does not match anything Microsoft has published for this file.
| Version | Build | Size | MD5 | SHA-1 |
|---|---|---|---|---|
14.27.29111.0 | 64-bit | 3b22b2ec303b0721827dd768c87df6ed | 86f8af095cf7368ccbff2d0fd6d33586145acd2b | |
14.26.28804.1 | 64-bit | 2f74f7bbf256d0acb305068a6960ea5a | 0212fee4a1997fd5828d7afc94926a69ba71bf59 | |
14.25.28508.3 | 64-bit | 6fe223ce568d919f80bea233738d0628 | d7bf5acfb4bed8b0790dfc617a9b6f899b484d4a | |
14.24.28127.4 | 64-bit | 9040ed0fdf4ce7558cbffb73d4c17761 | 669c8380959984cc62b05535c18836f815308362 | |
14.23.28008.0 | 64-bit | 770184b0a38debfa6194f71d7673ea2a | 355f23b92222ceabac1a038098c844044e2f5402 | |
14.23.27820.0 | 64-bit | e62522e067aacf9e7a4faf928bfc3965 | 676105c373bf128a5b5700ff1f52486fd01e72b7 | |
14.22.27821.0 | 64-bit | 2fa6da61d1bac1055bbf7c6d473e7a1e | 75f381e0240a97dace5918fecc52efeb67425de8 |
Copies uploaded by users to a public DLL catalogue, read on 14 October 2026. We list their checksums so you can identify a file; we do not offer them for download and we did not verify each one against Microsoft's signature.
Questions people ask
Is there a 32-bit (x86) version of vcruntime140_1.dll?
No. Microsoft builds vcruntime140_1.dll for x64 only. 32-bit programs use a different way of handling C++ exceptions that lives in vcruntime140.dll, so they never ask for this file. If a 32-bit program seems to need it, the error is coming from a 64-bit part of that program, and the x64 package fixes it.
I have vcruntime140.dll. Why is vcruntime140_1.dll still missing?
Because the copy of the runtime on your PC is older than the program. vcruntime140_1.dll arrived with Visual Studio 2019, and redistributables from the 2015 and 2017 era do not have it. Installing the current x64 package upgrades the runtime in place and adds the file next to vcruntime140.dll.
Do I need vcruntime140_1.dll on Windows on ARM?
Only for 64-bit Intel and AMD programs, which Windows on ARM runs under emulation. The ARM64 redistributable installs the x64 vcruntime140_1.dll for them. There is no native ARM64 build of the file, and native ARM64 programs do not use it.
Can I copy vcruntime140_1.dll from another computer?
It can work if you copy vcruntime140.dll from the same PC with it, since the two must match. You also bring over whatever version and state those files are in, and the installer will not know about them. Installing the x64 redistributable takes a minute and gives you the current, registered pair.
Is the vcruntime140_1.dll on my PC safe to keep?
The genuine file is a signed Microsoft library and is safe. Another file can carry the same name, so check a copy you are unsure about with the tool on this page; the security page linked above covers where suspicious copies turn up.
Which Visual C++ year do I need for vcruntime140_1.dll?
The 2015-2022 (v14) redistributable in its current version. Programs built with Visual Studio 2019 and 2022 ask for vcruntime140_1.dll, and they all share this one runtime. Older Visual C++ packages, including early 2015 and 2017 releases of the same family, do not contain the file.
Related guides
How to fix VCRUNTIME140_1.dll missing or not found error in Windows?
FixFix: this application failed to start because no Qt platform plugin could be initialized
FixHow to fix error code 0xe06d7363 on Windows?
FixHow to fix Entry Point Not Found error in Windows?
Sources
- Microsoft: Latest supported Visual C++ Redistributable downloads
- Winbindex, the Windows binaries index (m417z)
File data read on October 14, 2026.
The editors who write and check uGetFix guides and reference pages. File facts are read from Microsoft's own installers and documentation, and every page shows the date its data was read.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…