Jump to content

Can't open unGTP, VCRUNTIME140.dll error


Recommended Posts

Posted

vcruntime140.dll sits big as life in my System32 folder. Tried adding it to SysWOW64 as well as directly into the folder from which I'm trying to run unGTP,  the only change is to the error message, now 0xc000007b. Updated vcredist '13, '15, '17 and '19, still no joy. Using Win7 Ultimate with all critical updates through Jan 14, 2020. Can anyone point me to a solution for this? I'm just itching to get at those stock skins. Thx!

  • 2 weeks later...
Posted (edited)

 

@motomad

 

Look here please:

 

 

 

Edited by Yankee_One
  • 2 years later...
Posted

This error message is directly related to the DLL file, when the VCRUNTIME140.DLL file is misplaced or deleted from the Windows system and you will face this error message. This error indicates a problem with the 2015 version of the Visual C++ Redistributable because there is a known conflict between the 2017 version and the 2015 version.

 

Please follow these steps:

 

Open Programs and Features form Control Panel

Uninstall the 2017 version of the C++ Redistributalbe, if that is installed on your System.

Then from the link below, download and install the 2015 version, then once that is installed, download and install the 2017 version.

 

https://docs.microsoft.com/en-GB/cpp/windows/latest-supported-vc-redist?view=msvc-170

 

Please Note, regardless of whether your version of Windows 10 is 32bit or 64bit, you must download and install both the x86 and x64 versions, do not try to install the ARM64 version.

 

DLL or Dynamic Link Libraries are external parts of applications and services that run on the Windows system. DLL files are the important part of any computer / laptop and we cannot imagine an operating system without DLL files. A single DLL file can be shared by more than one application and services. That is why, when a dll file gets corrupted / deleted / moved from the system, all linked applications start launching DLL errors. Sometimes, this error message also starts to appear after installing a Windows update or an incorrect installation of any program. This is for the reason that, in all the latest updates or patches released by Microsoft, there may be a missing system file or dll file.


 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...