VCRUNTIME140_1.dll was not found

I hate it when I have to touch anything Microsoft or running on Microsoft. VCRUNTIME140_1.dll is just the latest in the never ending battle with The Gang That Couldn’t Shoot Straight.

The Gang That Couldn’t Shoot Straight movie cover

Today it was OnlyOffice that wanted to force an update on me. Software on Windows has the world’s worst habit of trying to force upgrades on you right when you are in the middle of doing something. I was literally four pages into a document when it spit this up. Like an imbecile I saved my file and said okay. After it finished and tried to restart I was greeted with:

VCRUNTIME140_1.dll
MSVCP140_1.dll

Yes, “works on my computer” syndrome is rampant in the Windows world. Ironic that I was verify documentation on how to set up development environments for RedDiamond when all of this happened. Yes, I write this doc and test it, even for OpenSource projects. Why? Because I’m a professional. That means I won’t touch AGILE with a hundred mile pole. AGILE’s hacking on the fly without any specifications or functional documentation is exactly how shit like this gets into the wild.

Fixing VCRUNTIME140_1.dll not found

This happens a lot. I couldn’t believe how many hits there were on the Microsoft message thread on this. When you are hacking with AGILE you simply don’t bother testing installs on bare machines. That can’t be done via CI/CD because it requires an actual machine.

You need to download the All-in-One package from techpowerup.com, run a virus scanner on it just in case, unzip it, then run the install BAT file as administrator. Yes, the download count at the time I pulled it down was north of seven million.

AGILE is an epidemic that may well end the human race.

The source of VCRUNTIME140_1.dll not found errors?

The primary source of this error is AGILE. Plain and simple, you don’t have a Systems Architect and an Application Architect creating The Four Holy Documents up front and riding roughshod over the team. Without The Four Holy Documents independent QA cannot happen. If you’ve never heard of The Four Holy Documents, read this book before you write even one more line of code.

Because there is no independent QA geeks build “update packages” in a half-assed manner. They “test” them on a development machine and hurl them out into the world.

They all forget to include the Visual C++ Runtime!

A real software development team using actual SDLC Software Engineering rather than AGILE hacking on the fly would have an independent QA team that would know enough to set up a raw Windows install for testing.

Add a Comment