InstallShield problem

Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer version
of Spybot began to self-install. Without thinking (which is the cause of
most of my problems!), I let it proceed. Halfway thru, it choked. I dl'ed
the new version and successfully installed it but it brought my system to a
crawl, so I uninstalled it and re-installed the older version. Since then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt any
of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up as a
process that is running in the Task Manager or your Process Explorer.
--------------------------------------------------------------------------------
Try to Delete all instances of IsUninst.exe from the Windows directory and
try running your setup again. If IsUninst.exe cannot be deleted because it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer version
of Spybot began to self-install. Without thinking (which is the cause of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

I have two comments;
1). If the uninstall shield is corrupted, would running the uninstall
feature of another program solve the problem or do these programs use the
same uninstall shield? I'm thinking of CCLEANER or EASYCLEANER.
2).If the uninstall shield is corrupted and always in use, then you may have
to go into mvp Gary Terhune's "tricked" CLEAN BOOT environment. If
interested, see
http://groups.google.com/group/micro...a0422c281f3c47

In effect go into MSCONFIG and change from normal startup to "selective
startup". Remove the checkmarks in "load startup group" and "load
environment variables". Reboot and then start/run and type %temp%. When new
screen appears Ctrl + A and delete everything highlighted. Then go to
Control Panel/Internet Options and delete TIF, including offline content.
Then empty recycled bin. Return to MSCONFIG and reactivate NORMAL STARTUP
but this time DO NOT REBOOT. Go ahead and uninstall what you are trying to
uninstall and once done, reboot to normal mode. The only caveat to the above
is if you haven't managed your startup items other than by removing
checkmarks, take a note of what was checked before starting and then
replicate when returning to normal mode.

Hope this helps
"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up as
a process that is running in the Task Manager or your Process Explorer.
--------------------------------------------------------------------------------
Try to Delete all instances of IsUninst.exe from the Windows directory and
try running your setup again. If IsUninst.exe cannot be deleted because it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer version
of Spybot began to self-install. Without thinking (which is the cause of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try the SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up as
a process that is running in the Task Manager or your Process Explorer.
--------------------------------------------------------------------------------
Try to Delete all instances of IsUninst.exe from the Windows directory and
try running your setup again. If IsUninst.exe cannot be deleted because it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer version
of Spybot began to self-install. Without thinking (which is the cause of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

Hi;
First, thanks for all the quick replies. As usual, solve one problem and
get another. As Heirloom suggested, I deleted IsUninst.exe and got a little
farther along in the install process but then got an error msg saying I
didn't have enough room in the Temp folder. I cleaned it out and now the
install goes a little farther before giving me an error msg with no text at
all, just an "OK" button (now that's hilarious!). Unfortunately, it's not
even leaving behind a log file that might tell me more. I'll try the System
Restore next. Thanks again...gjw

"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt
any
of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up as
a
process that is running in the Task Manager or your Process Explorer.
--------------------------------------------------------------------------
------
Try to Delete all instances of IsUninst.exe from the Windows directory and
try running your setup again. If IsUninst.exe cannot be deleted because it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the cause
of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system
to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

Mart,
Spybot doesn't update itself, the user must do it.
Isn't that a red flag?

Harry.


"Mart" wrote in message
...
George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try the SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up
as
a process that is running in the Task Manager or your Process Explorer.

--------------------------------------------------------------------------
------
Try to Delete all instances of IsUninst.exe from the Windows directory
and
try running your setup again. If IsUninst.exe cannot be deleted because
it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set
just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the cause
of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system
to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

Harry.....sometimes it does. It tried to download the latest build
without my asking it to and I cancelled it immediately. But I did find
that yes, what it was trying to download was quite kosher and it is on
here now.

It was just the fact that it was totally unexpected that threw me. So
no, it was NOT a red flag.

HF

"webster72n" wrote in message
...
Mart,
Spybot doesn't update itself, the user must do it.
Isn't that a red flag?

Harry.


"Mart" wrote in message
...
George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try
the SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the
original
install failed and you then performed the uninstall. Before you
attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your
machine.
IsUninst.exe is the InstallShield uninstallation file, and when it
is
corrupted it might appear to be in use even though it is not
showing up
as
a process that is running in the Task Manager or your Process
Explorer.

--------------------------------------------------------------------------
------
Try to Delete all instances of IsUninst.exe from the Windows
directory
and
try running your setup again. If IsUninst.exe cannot be deleted
because
it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was
set
just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans
don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the
cause
of
most of my problems!), I let it proceed. Halfway thru, it choked.
I
dl'ed
the new version and successfully installed it but it brought my
system
to
a
crawl, so I uninstalled it and re-installed the older version.
Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I
guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

So can you tell me 'why' it does update itself?
It certainly isn't designed that way.
The fact that it does, must signify something wrong, because simply updating
definitions requires choosing a site.
Maybe it's time to 'contact us' at Spybot.

Harry.


"Heather" wrote in message
...
Harry.....sometimes it does. It tried to download the latest build
without my asking it to and I cancelled it immediately. But I did find
that yes, what it was trying to download was quite kosher and it is on
here now.

It was just the fact that it was totally unexpected that threw me. So
no, it was NOT a red flag.

HF

"webster72n" wrote in message
...
Mart,
Spybot doesn't update itself, the user must do it.
Isn't that a red flag?

Harry.


"Mart" wrote in message
...
George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try
the SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the
original
install failed and you then performed the uninstall. Before you
attempt
any of the steps below, read through some of the articles he

http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your
machine.
IsUninst.exe is the InstallShield uninstallation file, and when it
is
corrupted it might appear to be in use even though it is not
showing up
as
a process that is running in the Task Manager or your Process
Explorer.


-------------------------------------------------------------------------
-
------
Try to Delete all instances of IsUninst.exe from the Windows
directory
and
try running your setup again. If IsUninst.exe cannot be deleted
because
it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was
set
just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans
don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the
cause
of
most of my problems!), I let it proceed. Halfway thru, it choked.
I
dl'ed
the new version and successfully installed it but it brought my
system
to
a
crawl, so I uninstalled it and re-installed the older version.
Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I
guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

I don't quite follow where you're driving Harry, but either way in my
opinion - and it would seem, HL's too - reverting to an earlier SR point
might be a useful exercise.

My understanding is that 'things were working normally' until George - while
attempting his download - was met with a 'spontaneous' self-install of "a
newer version of Spybot" - Reason unknown, apparently (although Heather
suggests 'spontaneous updates' may sometimes occur).

But if, as George now believes:-

.. I guess a registry key was corrupted,

then a good place to get back to, would be to a time before he began his
download - or at least as far as the registry is concerned. All other
(temporary) folders etc., should be deletable (if he can find them) and/or a
fresh install/uninstall of Spybot (without running it!) ought to clean-up
his machine. Then he can install it again - if he still wants it! g

But let's wait and see how George has fared after his last posting. (20:10
GMT)

Mart



"webster72n" wrote in message
...
Mart,
Spybot doesn't update itself, the user must do it.
Isn't that a red flag?

Harry.


"Mart" wrote in message
...
George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try the
SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing up
as
a process that is running in the Task Manager or your Process Explorer.

--------------------------------------------------------------------------
------
Try to Delete all instances of IsUninst.exe from the Windows directory
and
try running your setup again. If IsUninst.exe cannot be deleted because
it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set
just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the cause
of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my system
to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I
guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace

Yep, Mart, I agree. IIRC, Spybot creates an SR when installing a new
version.....I could be wrong on that. In any case, if his SR is working
properly, he should have a point not too far from when the botched install
took place. Before any 'invasive surgery' takes place, I would surely try
that......at least, it is reversible!
Heirloom, old and love my whole disc backups

"Mart" wrote in message
...
I don't quite follow where you're driving Harry, but either way in my
opinion - and it would seem, HL's too - reverting to an earlier SR point
might be a useful exercise.

My understanding is that 'things were working normally' until George -
while attempting his download - was met with a 'spontaneous' self-install
of "a newer version of Spybot" - Reason unknown, apparently (although
Heather suggests 'spontaneous updates' may sometimes occur).

But if, as George now believes:-

.. I guess a registry key was corrupted,

then a good place to get back to, would be to a time before he began his
download - or at least as far as the registry is concerned. All other
(temporary) folders etc., should be deletable (if he can find them) and/or
a fresh install/uninstall of Spybot (without running it!) ought to
clean-up his machine. Then he can install it again - if he still wants it!
g

But let's wait and see how George has fared after his last posting. (20:10
GMT)

Mart



"webster72n" wrote in message
...
Mart,
Spybot doesn't update itself, the user must do it.
Isn't that a red flag?

Harry.


"Mart" wrote in message
...
George wrote:-

.. I guess a registry key was corrupted,
but which one and what should it be?

I'm with HL, - in his last paragraph, HL wrote:-

you should have a System Restore point .. .. I think I would try the
SR
first!!

Mart



"Heirloom" wrote in message
...
I believe you may have corrupted the Uninstall shield when the original
install failed and you then performed the uninstall. Before you
attempt
any of the steps below, read through some of the articles he
http://knowledge.macrovision.com/sel...searchEntry.do

This could be happening if IsUninst.exe is corrupted on your machine.
IsUninst.exe is the InstallShield uninstallation file, and when it is
corrupted it might appear to be in use even though it is not showing
up
as
a process that is running in the Task Manager or your Process
Explorer.

--------------------------------------------------------------------------
------
Try to Delete all instances of IsUninst.exe from the Windows directory
and
try running your setup again. If IsUninst.exe cannot be deleted
because
it
is in use, try to reboot the machine and run the setup again.

Don't forget that you should have a System Restore point that was set
just
before all this happened. That may be your best shot at resolving
this.....I think I would try the SR first!!

Hope that helps resolve the issue.

Heirloom, old and too bad humans don't
have
an SR



"George J. Wallace" wrote in message
...
Hi;
About 2 weeks ago, while dl'ing new defs for Spybot S&D, a newer
version
of Spybot began to self-install. Without thinking (which is the
cause
of
most of my problems!), I let it proceed. Halfway thru, it choked. I
dl'ed
the new version and successfully installed it but it brought my
system
to
a
crawl, so I uninstalled it and re-installed the older version. Since
then,
I can't install any other programs. I get the following message:

Setup Initialization Error
Setup has detected that unInstallShield is in use. Please close
unInstallShield and restart setup. Error 432

Using Process Explorer, I don't see unInstallShield running so I
guess
a
registry key was corrupted, but which one and what should it be?

Any help would be greatly appreciated. TIA...gjw



--
George J. Wallace