Missing vcruntime140d.dll and ucrtbased.dll

Question

Hello,

I'm using VS Community 2015 for college and although all programs I made in VS worked in my computer, if I try to execute them in different computers (that lack VS 2015) they don't work. Something about missing "vcruntime140d.dll" and "ucrtbased.dll". I tried different programs in different computers and it's always the same problem. I enjoy using VS, but it's impossible to continue doing so if the programs simply don't work in different computers.

Anyone has any idea how to solve this? Maybe there's a way to deactivate the need for these two dlls?

Thanks!

Answer 1

Those are Debug versions of DLLs.

You must compile in Release mode.

Answer 2

Thanks. I compiled in Release mode, but now it's saying "missing vcruntime140.dll"...

Answer 3

It is Visual C++ Redistributable for Visual Studio 2015

You can also see threads like :

http://stackoverflow.com/questions/35805113/visual-studio-2015-run-time-dependencies-or-how-to-get-rid-of-universal-crt

Answer 4

Thanks for Castorix31's help.

Hi RenanKJ,

As far as I know, high version VS project often could not be opened by low version VS. Because they have different features. Unless the high version VS project is not use any new features in high version VS.

Since you are using VS2015 create this project, this project will use the VS2015 related component dlls in your project. But there doesn't have VS2015 installed on another machine, which will lead to your project could not run successful because lack of dlls.

Please try Castorix31's suggestion to install the Visual C++ Redistributable for Visual Studio 2015. And I think you also could install Visual Studio 2015 on that machine, which will install all VS2015 components. If possible, please open the project with one version of Visual Studio.

Best Regards,
Weiwei

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 5

Thanks for all the answers!

Unfortunately, I'm not allowed to install any software in the computers where I had the issue. But then, even if I could, I sincerely don't believe this to be the best solution, depending on the user to have something installed isn't a very good idea to me when distributing your own programs; it would be better if the program would install needed components if the computer lacks them.

Anyway, I did find a solution! I don't really understand yet how it works and what are the pros and cons of using it, but I linked the DLLs with the executable. That solved the problem in all computers where I tested it. =)

Thanks for the help, guys!

Answer 6

Hi friend,

Glad to know that you have resolved this issue, and thanks for sharing your solution here. Would you please mark your reply as the answer? So it would be helpful for other members who meet the same issue as yours.

Have a nice day :)

Sincerely,

Oscar

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 7

Hi i have the exact same problem. didnt understand how did you linked it to the exe. can you please guide me.

Thanks