Windows 10: Probleme mit Vcruntime140.Dll, msvcp140.dll und weitere DLL Files

Ich habe das Problem, dass wenn ich den Origininstaller starte, mir immer wieder die selbe Fehlermeldung angezeigt wird, nämlich vcruntime140.dll, msvcp140.dll wurde nicht gefunden, bitte installieren sie das Programm neu. Ich habe versucht Microsoft Visual neu herunter zu laden, Windows geupdated, die Files einzeln herunterzuladen, es über die Eingabeaufforderung versucht, da wurde mir dann angezeigt ,dass der Dll-RegisterServer-Eingangspunkt nicht gefunden wurde, Windows mehrfach neu aufgesetzt und sogar von meinem Bruder die Files, welche bei ihm funktionieren, verwendet und trotzdem geht es bei mir nicht. Mittlerweile bin ich absolut ratlos was ich noch machen kann damit es endlich funktioniert

:)

 

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 )

 

keep getting error messages...vcruntime140.dll, vccorlib140.dll, and msvcp140.dll....how do I fix this?

keep getting error messages...vcruntime140.dll, vccorlib140.dll, and msvcp140.dll....how do I fix this?

 

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