If this were a prescription--it would be an "off label" prescription. The
KB article about the SP states:
----------------------------------------------------------
In addition to distributing simple executables, you can also use the
VBRun60sp6.exe file for the following: . To minimize the size of Internet
downloads of Visual Basic applications.
By running the Vbrun60sp6.exe file ahead of time, users can download
your application from the Web faster.
. As a troubleshooting step when an installation of Visual Basic or a
Visual Basic application fails.
If Setup fails with an error message that mentions one of the core
files, or if registration of a component fails during Setup, the core files
on the target computer might be mismatched. If the versions of the files in
the VBRun60sp6.exe file are newer than the versions on the target computer,
you might resolve the problem by running the VBRun60sp6.exe file before you
run Setup.
---------------------------------------
I'm looking at the second bullet point in that list and thinking that this
might fit this instance.
I'm still at a point where I'm somewhat experimental in seeing what this
covers. FWIW--I have tried it on a system which cannot submit a Tools,
Suspected spyware report--and it had no effect on that issue!
Unfortunately, I have very few of the common issues we see here available to
test with.
