ka6uup said:
OK, I went into the ATT folder and tried opening the exe file and
received an error message that said the runtime.dll file was the wrong
version.
Can you give a *link* to the source website of the application ?
Using "All The Time" as a search time, is getting me gibberish for
search results.
Also, quote the *exact text* of the error message. There are several
kinds of helpers for executables.
DLL built by the developer
Visual Studio helpers, like MSVCRT.dll (multiple versions, different year of intro)
.NET stuff (for dotNET programs)
JAVA stuff (for JAVA programs)
for the Visual Studio ones, they can be stuffed into the application folder,
or in a System folder.
And a developer, if not careful, can fit a "time bomb" into code,
which can cause it to stop functioning on an arbitrary date. In many
cases, this is unintentional (or, so they claim).
I can't think of too many mechanisms, that would cause a desirable version
of a helper, to just... disappear. Normally, new versions are added in
parallel. A file may be patched for security reasons, but its main identifiers
would not change (the loader would see the same info as before). The version
of the file, like 6.1.7694.3 might change after a patch, but it would
still be MSVCRT71.dll or whatever. And probing it with something like
Dependency Walker, should show the same kinds of details. Patching
a file, should not change the declarations inside it.
It's possible an AV program could quarantine a desirable file.
In which case, you'd look in whatever folder is used for quarantining,
for a hint. I would be betting on an AV incident, before blaming
Windows Update.
So there's an idea. Name any AV you happen to be using.
Paul