>>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Cu rrentVersion\Installer\UserData\S-1-5-18\Products\b25099274a207264182f8181add555d0
> I don't seem to have that product code so does that means I have and
> older version?
>>If you have a different version of the redist installed, you may need to
>>poke around a bit to find the right one. Look for the "DisplayName" value,
>>under the InstallProperties sub-key.
>
> Not sure what subkey you're referring to here. Could you please post
> the full key
For teh VS2005 SP1 Redstributeable, the key would be:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Microsoft\Windows
\CurrentVersion
\Installer
\UserData
\S-1-5-18
\Products
\b25099274a207264182f8181add555d0
\InstallProperties
And the value is called "DisplayName", of type REG_SZ. The contents of value
is "Microsoft Visual C++ 2005 Redistributable"
For previous versions of the Redistributable,
b25099274a207264182f8181add555d0 will be replaced with a unique GUID
matching the specific version. So walk through all the keys uder Products,
looking for a DisplayName like "Microsoft Visual C++ 2005 Redistributable"
> Thats basically my problem I don't know the version and if I did I
> don't know where to get the vcredist.msi that the prompt is looking
The "DisplayVersion" value witll give you some idea which version you
currently have installed.
>>"vcredist /C /T:C:\TEMP\VCREDIST" to unpack the files into a dir called
>>C:\TEM\VCREDIST. Obviously you can change the directory on the /T:
>>parameter
>>to suite your local requirements.
>
> Ok so I know now. ;-)
> But I neeed the correct version info and a place to get the redist.exe
> that matches that version. correct?
Yeah, that's right . Hopefully you still have the redistributable that was
used to install on these machines in the first place. There's a principle of
IT management called "configuration management" and/or "change management".
It's designed to prevent this kind of predicament :-) See
http://en.wikipedia.org/wiki/ITIL. Or you may be able to find it lurking in
the archives, somewhere on the Internet.
Your other possibility would be to run the new VCRedist.msi with the "forced
update" parameter; eg:
C:\TEMP\EXTRACT>msiexec /fa vcredist.msi /l*v vcredist.log
The "/fa" is the forced update" switch. "/l*v vcredist.log" tells MSIexec to
create a verbose log file called vcredist.log, showing what it is doing at
every stage. If you still encounter errors, this log file may help you
determine why they are occuring and how to fix them.
But if you can uninstall the old version cleanly, I think that would be the
best solution.
--
Andrew McLaren
amclar (at) optusnet dot com dot au