[ApexLead]

Hello,
I followed some solutions that I was given here about how to get rid of the missing vcruntime140.dll and msvcp140.dll errors but it didn't solve my problem.
I changed the linker to /MT for release and /MTd for debug, but when I try it on different windows 10 machines it says the spoken DLLs are missing, Ive searched for a solution everywhere but all I saw was changing the linker to be static, like I did.

If someone can help me solve this issue it will be much appreciated, thanks in advance :)

[Cød3ing]

What are you trying to compile? what language is it in? what compiler are you using? what compiler flags have you set? What machine did you compile this on?

[ApexLead]

What are you trying to compile? what language is it in? what compiler are you using? what compiler flags have you set? What machine did you compile this on?

A code I wrote, those are all of the headers & libs:
#include "stdafx.h"
#include <iostream>
#include <windows.h>
#include <Shlobj.h>

It's written in c++, visual studio 2015, /MT for release and /MTd for debug, compiled on a windows 10 machine

[RCE]

Make sure you execute the output file from 'release' into your other machines , if the problem is still then u maybe misconfigured ur settings , try to compile with G++/ mingw via command line and check again

[0xDEAD10CC]

Make sure you execute the output file from 'release' into your other machines , if the problem is still then u maybe misconfigured ur settings , try to compile with G++/ mingw via command line and check again

He's not using mingw... Not sure what good this will do, the options aren't even the same.

@OP - are you sure you understand how to use the configuration dropdown?


Then you can see visibly the difference of the static linking by looking at the filesizes:


And/or check the imports to make sure that you don't see the dll in the IAT. If you just change the project settings btw, but your code doesn't change, the IDE may not build it, so you'll have to do a rebuilt instead to force it.

This is easy though, so I'm not sure what your problems would be otherwise.

[HiddenEyE]

OP surprise that you have not been able to solve this when the solution is filled up in google.
anyway if you select /MT their are libs you should link it with. google for the libs.

[0xDEAD10CC]

OP surprise that you have not been able to solve this when the solution is filled up in google.
anyway if you select /MT their are libs you should link it with. google for the libs.

If you select /MT you don't have to link it with anything, this option will take care of the linking for you.

[ApexLead]

He's not using mingw... Not sure what good this will do, the options aren't even the same.

@OP - are you sure you understand how to use the configuration dropdown?


Then you can see visibly the difference of the static linking by looking at the filesizes:


And/or check the imports to make sure that you don't see the dll in the IAT. If you just change the project settings btw, but your code doesn't change, the IDE may not build it, so you'll have to do a rebuilt instead to force it.

This is easy though, so I'm not sure what your problems would be otherwise.

OP surprise that you have not been able to solve this when the solution is filled up in google.
anyway if you select /MT their are libs you should link it with. google for the libs.

Thanks for your replies, but I know how to make /MT and /MTd for release and debug, but for some reason it still shows a runtime dll error on some machines, even if I link statically :/

[0xDEAD10CC]

Thanks for your replies, but I know how to make /MT and /MTd for release and debug, but for some reason it still shows a runtime dll error on some machines, even if I link statically :/

Then you're doing it wrong. Show me the imports table.

[El Lobo]

Make sure you execute the output file from 'release' into your other machines , if the problem is still then u maybe misconfigured ur settings , try to compile with G++/ mingw via command line and check again

What a bunch of shit that you wrote. You cant even read properly and yet you are selling hvnc coded in c++.

To the op, you are not using ide properly. Just like this guy above me said, just look at the iat and see if you have dependencies.

[HiddenEyE]

am not posting any further. solution given.

[ApexLead]

Then you're doing it wrong. Show me the imports table.

Sorry for the newbie question, but where can I find it?

What a bunch of shit that you wrote. You cant even read properly and yet you are selling hvnc coded in c++.

To the op, you are not using ide properly. Just like this guy above me said, just look at the iat and see if you have dependencies.

IAT?

am not posting any further. solution given.

The static linking solution didn't solve the problem tho..

[El Lobo]

IAT?

Import address table. Open compiled file with peexplorer and go to imports tab and you will see all dlls that your exe depends on.

[ApexLead]

Import address table. Open compiled file with peexplorer and go to imports tab and you will see all dlls that your exe depends on.

Opened with PE Explorer, those are the imports:
kernel32.dll
user32.dll
shell32.dll
ole32.dll
api-ms-win-core-path-l1-1-0.dll (On this one I have "Path not found" error)

[Hoodie+]

What a bunch of shit that you wrote. You cant even read properly and yet you are selling hvnc coded in c++.

To the op, you are not using ide properly. Just like this guy above me said, just look at the iat and see if you have dependencies.

Good point, lol.

I asked a few question about how he coded the HVNC and he didn't answer them on his thread.
Imagine buying a $800 bot and it requiring a preinstalled C++ Runtime library 😧

---

Opened with PE Explorer, those are the imports:
kernel32.dll
user32.dll
shell32.dll
ole32.dll
api-ms-win-core-path-l1-1-0.dll (On this one I have "Path not found" error)

api-ms-win-core-path-l1-1-0.dll is a part of Visual C++ Redistributable for Visual Studio 2012 if I'm not mistaking.