T
Todd B.
Just recently, our installations have been acting very strange. We
released a software update, and upon installing it several users
reported that they could not uninstall their previous versions because
uninstall could not find the installation source. It shows the msi
filename in the combobox, but it's the filename with no path. It
won't even allow the user to browse for the setup package. What's
even stranger is if the user runs the previous version setup, it won't
install either due to the fact that another version is detected.
We've been following the same method of building installs for quite
some time now, and this has never happened before. I've tried to have
users delete the entries in
"HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" that
contain references to our software, but the programs remains in the
Add/Remove Programs group. When they try to install the new version
it still pops up a message stating that there is already a version of
the software installed, and that it needs to be removed before
proceeding. This is normal, as we instruct our customers to remove
the old version before installing the new version.
The only information about the installs that I know might be helpful
is that this is happening on 2 of our products, one created with
Windows Installer 1.1, and the other with 2.0 (.NET). The upgrade
codes were also accidentally changed on both without the product codes
being changed as well.
I cannot produce this behavior on my test machine, so I have no idea
where to start. Is there a way I can get the user's computers back to
normal, and what do I need to do in the future to prevent this from
happening again?
released a software update, and upon installing it several users
reported that they could not uninstall their previous versions because
uninstall could not find the installation source. It shows the msi
filename in the combobox, but it's the filename with no path. It
won't even allow the user to browse for the setup package. What's
even stranger is if the user runs the previous version setup, it won't
install either due to the fact that another version is detected.
We've been following the same method of building installs for quite
some time now, and this has never happened before. I've tried to have
users delete the entries in
"HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" that
contain references to our software, but the programs remains in the
Add/Remove Programs group. When they try to install the new version
it still pops up a message stating that there is already a version of
the software installed, and that it needs to be removed before
proceeding. This is normal, as we instruct our customers to remove
the old version before installing the new version.
The only information about the installs that I know might be helpful
is that this is happening on 2 of our products, one created with
Windows Installer 1.1, and the other with 2.0 (.NET). The upgrade
codes were also accidentally changed on both without the product codes
being changed as well.
I cannot produce this behavior on my test machine, so I have no idea
where to start. Is there a way I can get the user's computers back to
normal, and what do I need to do in the future to prevent this from
happening again?