VCRUNTIME140_1.dll was not found - d3 will not start

[TiredCliche-1622]

On an HP Open laptop, 2-3 days ago Diablo 3 stopped running. When I start on the battle.net d3 window, I get the message:
“The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem.”
I’ve removed and reinstalled d3, battle net, and ran windows drivers updates. I also ran the gear next to start for the scan and repair option. Nothing works.

I tried writing support and they gave me a link to a help article for WoW and a message they don’t help anymore but feel free to check forums.

If anyone else had this problem and found a solution I’d really appreciate it.

[yessquire-1869]

Have you looked at any of the other posts that address this issue?

[Perusoe-1251]

@TiredCliche-1622

If anyone else had this problem and found a solution I’d really appreciate it.

If you have the VCRUNTIME104_1.DLL error read this

For those of you that are getting the VCRUNTIME104_1.DLL error on trying to launch the game, there may be a relatively easy solution. Go to the TechPowerUp site and download the all in one Visual C++ Runtime package. Follow the instructions on the page I linked and it will install all of the VC++ runtime packages released so far. The very error you’re seeing is one of the errors listed on that page that gets fixed by installing (or reinstalling) the VC++ Runtime packages. Make sure you carefull…

[TiredCliche-1622]

I did a search for the term, error message, and did not get any hits before I posted this. If there is another way I should have searched I’m all ears.

[Perusoe-1251]

@TiredCliche-1622

If there is another way I should have searched I’m all ears.

Go to the Forum Index. Click on the magnifying glass icon to the left of your Avatar. Type in VCRUNTIME140_1. Scroll down to the bottom of the popup and click More….

You should find yourself here.

[yessquire-1869]

error message is too generic a term. If you had just scrolled a bit in General Discussion,or even Bug Report, you would have found related threads.

[TiredCliche-1622]

Thanks - I did nothing but the error seems to have vanished on its own. Like nothing at all - no more updates, drivers…it just started working. Thanks though!