Windows 10: VCRUNTIME140.dll and MSVCP140.dll missing in Windows 10

In trying to open a particular program (On1 Resize 2019) in my brand new computer running Windows 10, I get the following messages:


The code execution cannot proceed because VCRUNTIME140.dll was not found


and


The code execution cannot proceed because MSVCP140.dll was not found.



Any help would be greatly appreciated.

:)

 

MSVCP140.dll and VCRUNTIME140.dll is missing!

Hello, I've been having quite the issue since I re-installed windows on my pc, I own a rust server, and there is a program called "Rust Admin", but to open that it says I don't have MSVCP140.dll and VCRUNTIME140.dll, even though I installed Visual C++ Redistributable
for Visual Studio 2015. If I go to the System32 folder, I have MSVCP140.dll and VCRUNTIME140.dll in there, so that's why I was confused, I tried re-installing the program, repairing it and even going into cmd and doing "sfc /scannow", which didn't help. I've
scanned for malware and can't find any so I'm confused as to why it's not working. Even if I copy the 2 files to the Rust Admin folder, it says "The application was unable to start correctly (0xc000007b)."

I hope we can get this problem resolved, thank you.

- Dylan

Moved from ( Windows / Windows 10 / Windows settings )

 

MSVCP140.dll is missing in my Win 10

Hello, I am using for the first time a brand new OEM W10 and neither step did any good.

In addition to the MSVCP140.dll missing error I also have a VCRUNTIME140.dll missing.

 

mfc140u.dll msvcp140.dll vcruntime140.dll with non-matching version-numbers: what to expect???

Hi,

Here's the setup:

I'm deploying a C++ x86/x64 executable which crashed on a customer system. Analyzing the crash showed that the following versions of mfc140u.dll, msvcp140.dll and vcruntime140.dll were used:

[table][tr][td]module[/td][td]version[/td][/tr][tr][td]mfc140u.dll[/td][td]14.0.24210.0[/td][/tr][tr][td]msvcp140.dll[/td][td]14.11.25506.0[/td][/tr][tr][td]vcruntime140.dll[/td][td]14.11.25506.0[/td][/tr][/table]

Installing the latest vcredist updated all the modules above to version 14.15.26706.0 and fixed the crash.

Apparently, some install updated msvcp140.dll and vcruntime140.dll WITHOUT using the official
vcredist and so missed mfc140u.dll

My questions are:

• Is this non-compatibility of dlls from different versions of the C/C++/MFC-runtime to expect? (I assume: yes)
• Couldn't the OS detect such version mismatches and/or even prohibit installations that try to update only parts of the vcredist-package?

Tobias