Visual Studio 2022 - "VCRUNTIME140.dll Is Missing" [duplicate] - visual-studio

I have a problem when trying to install apache 2.4 on my windows 10. It always shows the error that VCRUNTIME140.dll is missing. I have checked other threads and found out that installing the 2015 Visual c++ Redistributables x64/x86 always solves the problem but I have both installed and I still have this problem. Are there any other solutions?

You need to install Microsoft Visual C++ 2015 Redistributable Update 3 RC, please find the link here, choose between the 32bit or the 64bit.
Reinstall the apache 2.4 and error should gone.

I had the same issue after installing wamp on windows 10.This worked for me.
Download VCRUNTIME140.DLL
Copy the dll file to C:\Windows\System32 using administrative privileges.
Try reinstalling apache.

Download and install the proper version of Microsoft Visual C++ 2015 Redistributable Update 3 RC regarding your hardware architecture (x86 / x64). Use the link below:
Microsoft Visual C++ 2015 Redistributable Update 3 RC

On Windows 6 X64, got an error 500 on any PHP files,
installing the 2015 Visual c++ Redistributables x64 solved my problem.

I'v already had VC 2015 Redist on my PC but files were not copied into Windows\System32.
So I copied missing files directly to this folder. A thing that I should mention is since I compiled my application in X86 mode I copied them from
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x86
not
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x64
I know that this solution is not the ideal one, but it was a workaround for my case.

If you are using Microsoft Visual C/C++ and you have already downloaded VCRUNTIME140.DLL, Go to Project Properties->Configuration Properties-> C/C++ -> Code Generation, Set Runtime Library Multi-threaded (/MT)

Remove apache 2.4 from your pc
Download VCRUNTIME140.dll from this link
Copy VCRUNTIME140.dll file and paste it inside to Windows/System32
Finally reinstall apache and run

Related

Visual Studio 2017 does not detect Windows Driver Kit installation

I already have Visual Studio 2017 professional with Desktop Development with C++ installed.
I am trying to build the Virtual Serial project found here:
https://github.com/Microsoft/Windows-driver-samples/tree/master/serial/VirtualSerial
When I try to build it, I get the error:
Severity Code Description Project File Line Suppression State
Error MSB8020 The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". virtualserial C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets
I cannot find any instructions on installation aside from this website.
https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
I downloaded the WDK for Windows 10, version 1803.
I closed VS2017 and ran the installer.
When running the installer I got the message in the screenshot below, I clicked Next to continue installing
After running the installer, the project still does not build, with the same error: WindowsUserModeDriver10.0 is not installed.
What am I missing during installation? Is this the correct installer for regular VS2017 (not community edition)?
Thanks,
I know this is old, but I recently fell into this rabbit hole. What worked for me was uninstalling all of the WDKs, rebooting, and installing WDK 1803 (the wdksetup.exe program downloaded from Other WDK downloads shows version 10.0.17134.1 in properties). That WDK installer specifically calls out VS 2017 when you add the Visual Studio integration at the end of the install process.
In my situation, I installed vs2022 with SDK 19041 and WDK 19041.
After some testing, I realized that VS2022 only supports WDK 22621(so on this date). So I installed WDK 22621 and SDK 22621, and problem solved.
If you still can't find Kernel Driver Build option, try run this file C:\Program Files (x86)\Windows Kits\10\Vsix\VS2022\10.0.22621.0\WDK.vsix(WDK 19041 only has VS2019). It's a Visual Studio's extension.
According to this: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/windows-wdk-on-visual-studio-2017-community/fdbd2b44-e57a-4849-903d-04001205a764
WDK is not currently supported by visual studio 2017.
This is ridiculous

VCRUNTIME140.dll missing

I have a problem when trying to install apache 2.4 on my windows 10. It always shows the error that VCRUNTIME140.dll is missing. I have checked other threads and found out that installing the 2015 Visual c++ Redistributables x64/x86 always solves the problem but I have both installed and I still have this problem. Are there any other solutions?
You need to install Microsoft Visual C++ 2015 Redistributable Update 3 RC, please find the link here, choose between the 32bit or the 64bit.
Reinstall the apache 2.4 and error should gone.
I had the same issue after installing wamp on windows 10.This worked for me.
Download VCRUNTIME140.DLL
Copy the dll file to C:\Windows\System32 using administrative privileges.
Try reinstalling apache.
Download and install the proper version of Microsoft Visual C++ 2015 Redistributable Update 3 RC regarding your hardware architecture (x86 / x64). Use the link below:
Microsoft Visual C++ 2015 Redistributable Update 3 RC
On Windows 6 X64, got an error 500 on any PHP files,
installing the 2015 Visual c++ Redistributables x64 solved my problem.
I'v already had VC 2015 Redist on my PC but files were not copied into Windows\System32.
So I copied missing files directly to this folder. A thing that I should mention is since I compiled my application in X86 mode I copied them from
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x86
not
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x64
I know that this solution is not the ideal one, but it was a workaround for my case.
If you are using Microsoft Visual C/C++ and you have already downloaded VCRUNTIME140.DLL, Go to Project Properties->Configuration Properties-> C/C++ -> Code Generation, Set Runtime Library Multi-threaded (/MT)
Remove apache 2.4 from your pc
Download VCRUNTIME140.dll from this link
Copy VCRUNTIME140.dll file and paste it inside to Windows/System32
Finally reinstall apache and run

VSTOInstaller.exe error 0x8007007F The procedure entry point GetFileVersionInfoExW could not be located in the dynamic link library VERSION.dll

I've got VSTO project for Outlook, developed in VS 2012.
When I install it under Windows XP, where Visual Studio 2010 or later version is installed, I've got no problems.
When I install it by clicking .vsto file under Windows XP where no Visual Studio is installed, VSTOInstaller.exe fails with 0x8007007F error.
When I install it from command line (in fact it's the same)
"c:\Program Files\Common Files\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe" /install file://.../OutlookAddIn.vsto
I get
The procedure entry point GetFileVersionInfoExW could not be located in the dynamic link library VERSION.dll
Windows installer 4.5, VSTO 2010 runtime are installed on the problem machine.
How to fix it?
Thanks.
Finally I suppose VSTO 2010 runtime downloaded from https://www.microsoft.com/en-us/download/details.aspx?id=48217 has a bug in VSTOInstaller.exe (version 10.0.60724.0).
Uninstalling it and reinsalling older version from distributive of VS 2015/2012/2010 (find file vstor40_x86.exe or vstor40_x64.exe) fixes the problem.
VSTOInstaller.exe from VS 2015 has version 10.0.50903.0 - it is OK.

Why is MSTest.exe not installed?

I have a dev machine and a build machine, both of which have Visual Studio 2012 Premium Update 3 installed (Version 11.0.60610.01). Both machines are 64 bit and are running Windows Server 2012 Version 6.2 (Build 9200)
The Dev machine has the following folder which contains MSTest.exe
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE
On the build machine, that folder doesn't exist and searching for mstest.exe shows that it isn't on the build server anywhere.
Opening Control Panel > Programs and trying the Change operation doesn't provide any option to install mstest. All options shown in that Change window are identical on each machine.
The build server is also installed as a TFS agent
I've tried re-installing VS but no change.
Why isn't MStest.exe installed on the build machine and how can I get it installed?
I am using VS2017 and I was facing the same issue and I found it in here.
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\Common7\IDE
Anybody using the VS2017 and facing the same issue can search the directory I have mentioned above to search MSTest.exe
Problem solved - the test components were on the F drive for some reason
This sounds like you did what I did.
If you install the update "2012.3" it will only install minimal components and not the full IDE. Try installing Visual Studio from the ISO (~2GB) and then apply the Update...
I found on a different directory:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\MSTest.exe
EDIT: I came upon this page because I am trying to make the transition from Visual Studio to the Jetbrains Rider IDE and they assisted with some other questions on where to find dependencies for their command line Justmock runner here

Microsoft.ReportView.ProcessingObjectModel Version 8.0.0.0 - Visual Studio 2005-2010

I have a program that was built in Visual Studio 2005. However, this program does not run on Windows 7 machine. I converted the project from Visual Studio 2005 to Visual Studio 2010. I then copied the published files to a Windows 7 laptop and ran the executable from there. When doing so, I got the following error:
Unable to install or run the application. The application requires that assembly Microsoft.ReportView.ProcessingObjectModel Version 8.0.0.0 be installed in the GAC first
Most of the solutions that I have found are for Visual Studio 8. Anybody have an answer?
I was able to resolve this by removing the Microsoft.ReportView.ProcessingObjectModel Version 8.0.0.0 from the assembly and adding 10.0.0.0 instead.

Resources