Roger Johnson wrote:
youtube-dl.exe - System Error
The code execution cannot proceed because MSVCR100.dll
was not found. Reinstalling the program may fix this problem.
All I did was download this executable & double click on it to get that!
https://youtube-dl.org/downloads/latest/youtube-dl.exe
What Windows 10 program am I supposed to reinstall and how do I do that?
Welcome to Visual Studio Redistributable roulette.
Let's take an example.
Visual C++ 2010 Redistributable Package
vcredist_x86.exe === all versions have the same name
Date Published: 2010-04-12 to make it "easier" later :-)
File Size: 4.8 MB
https://www.microsoft.com/en-ca/down...s.aspx?id=5555
With 7ZIP, I look inside:
vcredist_x86.exe\.\.\.\.\vc_red.cab\
F_CENTRAL_msvcr100_x86 770,384 bytes
On a 64-bit Windows install, it's generally a
good idea to install both the x86 and the x64 version
while you're at it. Since I have x64 Win10 installs
here, I'd get both downloads and do both of them.
https://www.microsoft.com/en-ca/down....aspx?id=13523
vcredist_x64.exe
F_CENTRAL_msvcr100_x64 829,264 bytes
The installer will correct the names, and the 7ZIP
check is merely to satisfy my curiosity that
I'm getting "close to the correct file". I don't
have to download any more and go fishing for names,
as this may bs sufficient to get the show on the road.
Now, say you suspect you've got "stale" versions
by accepting random links in your web browser. Do
a reboot, visit Windows Update, and it should
patch them up for you (to the latest version).
It must do that, because I remember an early
version of Win10 got into a loop, updating
two of those files over and over... and over again.
What fun :-/
*******
Other places you can look:
Right-click Start
"control.exe"
Programs and Features
Windows Features
and see if any rubbish like that is present there.
Sometimes there's a fill-in version of dotNET there.
In a sense these are similar to dotNET, but they're
from another time, and are part of Visual Studio
IDE and compiler set. These files contain runtime
subroutines the main program may need.
Sometimes the OS installer DVD has a folder with rubbish
of that sort in it too. And some Windows SDK once, had
a good sized folder of DirectX rubbish, suitable for
gamers (that collection was *much* better than going
web fishing).
But since this isn't trivial pursuit, you can get
the files off the microsoft website.
*******
There are sample links here, for a multitude of these.
An earlier one, you have to download .NET 1.1 to get
the file you need.
https://gist.github.com/mmozeiko/de5...8bf4253bed8b3e
It's really not supposed to work this way. Because the
files are redistributable, a developer can package the
DLL in question, in the download. There is not supposed
to be any grief involved. Instead, the developers save
on bandwidth, by making the users "go fishing" for the
damn dependency. And I think you can guess what I
think of that practice. Even if the developer would
leave a README file with the URL(s) of the web pages
needed to complete the install, that would be much
better than the ignorant attitude the developers
express.
And they do the same thing with .NET. In theory, it's
possible to do dynamic loads of DLLs, and write nice
descriptive error messages if a dependency is missing.
Instead, yahoos from the developer community, allow
their program to emit an "mscoree error". The user
is then supposed to pull a Kreskin and say "Oh,
some version of dotNET is missing from my OS".
Then the user gets lucky and downloads the correct
numbered version.
Really, nothing much changes in the software world.
Roulette today, roulette tomorrow.
Paul