How do I uninstall MS C++ redistributable

[billpierpont]

Lately a lot of my installs started trying to install MS C++
redistributable but to do so it needs to uninstall the old version.
However it can not "find the source" and keeps asking me to insert
disk 1 or browse to it's source. Well I don't have either and thus my
installs are failing because they can not remove the old version.

I've tried downloading the redistributable but the same thing happens
I NEED THE SOURCE DISK

how can I get it uninstalled or at least make the OS think it is
uninstalled so that it continues?

Thanks

 

[Andrew McLaren]

Lately a lot of my installs started trying to install MS C++
redistributable but to do so it needs to uninstall the old version.
However it can not "find the source" and keeps asking me to insert
disk 1 or browse to it's source. Well I don't have either and thus my
installs are failing because they can not remove the old version.
I've tried downloading the redistributable but the same thing happens
I NEED THE SOURCE DISK
how can I get it uninstalled or at least make the OS think it is
uninstalled so that it continues?

Hi Bill,

Which version of the redist do you have already installed, and which version
are you trying to install now?

If Uninstall prompts you for a the source disc, it's probably because the
cached MSI file has been deleted, or the original source directory no longer
exists. MSIexec will store info about the installation in the Registry,
under the Installer key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\

For the VS2005 SP1 redist, the product code is
"b25099274a207264182f8181add555d0". So the install info is stored in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\b25099274a207264182f8181add555d0

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.

There are 2 interesting values here:
"InstallSource" the location of the MSI file the redist was installed from;
"Local Package" -the cached local copy of the MSI file
If the Installer cannot locate the MSI file using either of these values, it
will throw up the error message you saw when uninstalling or modifying an
installation.

If you have the MSI file from the existing Redist package you have
installed, you can drop it in a directory or network share somewhere; then
change the "InstallSource" value to point towards this valid copy of the
MSI.

You can extract the MSI and CAB file from the redist EXE file by running
"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.

So in summary:
- inspect Registry, find that the old InstallSource is set to (for example)
C:\TEMP\INSTALL
- extract MSI file from old redist EXE, copy it to C:\TEMP\INSTALL
- now run Uninstall either via GUI, or using "msiexec /X {GUID}" command
line.

Let us know how you get on,

 

[billpierpont]

Hi Bill,

Which version of the redist do you have already installed, and which version
are you trying to install now?

If Uninstall prompts you for a the source disc, it's probably because the
cached MSI file has been deleted, or the original source directory no longer
exists. MSIexec will store info about the installation in the Registry,
under the Installer key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\

For the VS2005 SP1 redist, the product code is
"b25099274a207264182f8181add555d0". So the install info is stored in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\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

There are 2 interesting values here:
"InstallSource" the location of the MSI file the redist was installed from;
"Local Package" -the cached local copy of the MSI file
If the Installer cannot locate the MSI file using either of these values, it
will throw up the error message you saw when uninstalling or modifying an
installation.

If you have the MSI file from the existing Redist package you have
installed, you can drop it in a directory or network share somewhere; then
change the "InstallSource" value to point towards this valid copy of the
MSI.

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
for.

You can extract the MSI and CAB file from the redist EXE file by running
"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?

So in summary:
- inspect Registry, find that the old InstallSource is set to (for example)
C:\TEMP\INSTALL

I don't have the product so I don't have install info

- extract MSI file from old redist EXE, copy it to C:\TEMP\INSTALL ok but where do I get it ?
- now run Uninstall either via GUI, or using "msiexec /X {GUID}" command
line.

I'm not there yet.
Thanks for the help but I need a little more.

 

[Andrew McLaren]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\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?

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.

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.

 

[bp]

On Mon, 27 Aug 2007 14:19:14 +1000, "Andrew McLaren"
Hello Andrew

Thanks for the help
Here is what I have found

The version is 8.0.50727.42
It should be at C:\Windows\Installer\2572b8.msi ?

However I have no windows\installed folder on either of my boot drives
(one for Vista and one for XP)

Now what?

I have the redist from a current demo I'm trying to install so is
there any way to force this to install?

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

A little confused here
What is the MSIEXEC and where do I get it?

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.

I appreciate your help

 

[Jane C]

Hi bp,

To see the 'Installer' folder in the Windows directory, you need to uncheck
'Hide protected operating system files' via Folder and Search options.

 

[bp]

Hi bp,

To see the 'Installer' folder in the Windows directory, you need to uncheck
'Hide protected operating system files' via Folder and Search options.

hmmm
I have directory opus as a replacement for explorer and I thought it
was set up to show me hidden folders. Now I have to figure out what's
wrong with that . ;-)

However explorer is set to show hidden files and folders and using it
I still don't have any install directory on either one of my windows
installalations.

 

[bp]

Hi it's me again, just want to say i fixed the problem - I don't know if
this'll work for you, but after much rummaging around and struggling
with the old version I simply used the windows install cleanup tool to
remove the old version of VCredist and then installed the new one -
everything up and ran with no problems!

OK what is the Windows install clean up tool?

 

[bp]

Hi it's me again, just want to say i fixed the problem - I don't know if
this'll work for you, but after much rummaging around and struggling
with the old version I simply used the windows install cleanup tool to
remove the old version of VCredist and then installed the new one -
everything up and ran with no problems!

I found it and it sounds like it might do the trick
I'll let you know, I'm installing it now ....
..
..
..
..
..
BINGO!!!

Nice little utility

Thanks to all that helped.

 

[Andrew McLaren]

BINGO!!!
Nice little utility

Cool. I guess the simplest solutions are often the best!

In future, I'll suggest the cleanup utility first (and leave registry
grovelling for the really ugly cases)

Cheers,

 

[bp]

Cool. I guess the simplest solutions are often the best!

In future, I'll suggest the cleanup utility first (and leave registry
grovelling for the really ugly cases) now that i know

Cheers,