InstallShield problem

I wasn' trying to contradict you or H, only to point out the possibility,
that there might be something in the system, causing this behavior.
If not, it's fine with me.
Hope he gets it straightened out. H.


"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

Hi;
I had no luck with the system restore - it said that there were no restore
points available. Just as additional information, I've checked my system
with both CA antivirus and AVG and both said the system is clean. I've gone
through most of the macrovision kb and they have nothing about an error msg
that doesn't show a msg or number.
I'm going to try running an install with Process Explorer running. I know
that shouldn't have any background processes running during the install but
this may show me at what step the install is breaking or what process it's
trying to call...gjw

"George J. Wallace" wrote in message
...
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

George, you don't say how long ago you fell into this hole but you *might* -
if you're lucky - still have a 'good' registry in your sysbckup folder.
(Usually the last 5 days worth)

You could try a scanreg /restore and see if there's a 'good' one - preceding
the hole - still there.

Otherwise, its the hard way!

Mart


"George J. Wallace" wrote in message
...
Hi;
I had no luck with the system restore - it said that there were no
restore
points available. Just as additional information, I've checked my system
with both CA antivirus and AVG and both said the system is clean. I've
gone
through most of the macrovision kb and they have nothing about an error
msg
that doesn't show a msg or number.
I'm going to try running an install with Process Explorer running. I
know
that shouldn't have any background processes running during the install
but
this may show me at what step the install is breaking or what process it's
trying to call...gjw

"George J. Wallace" wrote in message
...
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

remembering that over a year ago you bailed me out

I thought I recognised your 'Handle', George g

If I can just find the CD, then
I should be golden

Hmm, I suspect that a registry which is anywhere near approaching 12 months
or more old, might cause more far problems than it resolves! - not to
mention the effects of the poking about that you allude to have undertaken
in trying to resolve things

Seems to me from this distance that if there's nothing suitable in the
sysbckup folder to work with, then you are almost out of further options and
I suppose therefore that a very old registry may be worth a try as a last
resort. Whether its worth the time and effort is up to you, but be aware, if
that doesn't work and screws things up big-time, you're probably left with a
Clean Install as the ultimate solution - unless you can live with what
you've got!

Good luck

Mart


"George J. Wallace" wrote in message
...
Hi;
Thanks Mart! That tickled one of my few remaining brain cells into
remembering that over a year ago you bailed me out of a bad video driver
problem. After the problem was fixed, I backed up the registry to CD. If
I
can just find the CD, then I should be golden. Thank you Very
Much!!...gjw

"Mart" wrote in message
...
George, you don't say how long ago you fell into this hole but you
*might* -
if you're lucky - still have a 'good' registry in your sysbckup folder.
(Usually the last 5 days worth)

You could try a scanreg /restore and see if there's a 'good' one -
preceding
the hole - still there.

Otherwise, its the hard way!

Mart


"George J. Wallace" wrote in message
...
Hi;
I had no luck with the system restore - it said that there were no
restore
points available. Just as additional information, I've checked my
system
with both CA antivirus and AVG and both said the system is clean. I've
gone
through most of the macrovision kb and they have nothing about an error
msg
that doesn't show a msg or number.
I'm going to try running an install with Process Explorer running. I
know
that shouldn't have any background processes running during the install
but
this may show me at what step the install is breaking or what process
it's
trying to call...gjw

"George J. Wallace" wrote in message
...
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

Hi;
Thanks Mart! That tickled one of my few remaining brain cells into
remembering that over a year ago you bailed me out of a bad video driver
problem. After the problem was fixed, I backed up the registry to CD. If I
can just find the CD, then I should be golden. Thank you Very Much!!...gjw

"Mart" wrote in message
...
George, you don't say how long ago you fell into this hole but you
*might* -
if you're lucky - still have a 'good' registry in your sysbckup folder.
(Usually the last 5 days worth)

You could try a scanreg /restore and see if there's a 'good' one -
preceding
the hole - still there.

Otherwise, its the hard way!

Mart


"George J. Wallace" wrote in message
...
Hi;
I had no luck with the system restore - it said that there were no
restore
points available. Just as additional information, I've checked my
system
with both CA antivirus and AVG and both said the system is clean. I've
gone
through most of the macrovision kb and they have nothing about an error
msg
that doesn't show a msg or number.
I'm going to try running an install with Process Explorer running. I
know
that shouldn't have any background processes running during the install
but
this may show me at what step the install is breaking or what process
it's
trying to call...gjw

"George J. Wallace" wrote in message
...
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

Hi Mart;
Thanks for the warning about using the old registry backup. The logical
next step before I really mess up is to get in touch with Macrovision and
see if they have a solution. Thanks, again, for all of your help both on
this problem and on previous ones. You've been a real life saver!...gjw

"Mart" wrote in message
...
remembering that over a year ago you bailed me out

I thought I recognised your 'Handle', George g

If I can just find the CD, then
I should be golden

Hmm, I suspect that a registry which is anywhere near approaching 12
months
or more old, might cause more far problems than it resolves! - not to
mention the effects of the poking about that you allude to have undertaken
in trying to resolve things

Seems to me from this distance that if there's nothing suitable in the
sysbckup folder to work with, then you are almost out of further options
and
I suppose therefore that a very old registry may be worth a try as a last
resort. Whether its worth the time and effort is up to you, but be aware,
if
that doesn't work and screws things up big-time, you're probably left with
a
Clean Install as the ultimate solution - unless you can live with what
you've got!

Good luck

Mart


"George J. Wallace" wrote in message
...
Hi;
Thanks Mart! That tickled one of my few remaining brain cells into
remembering that over a year ago you bailed me out of a bad video driver
problem. After the problem was fixed, I backed up the registry to CD.
If
I
can just find the CD, then I should be golden. Thank you Very
Much!!...gjw

"Mart" wrote in message
...
George, you don't say how long ago you fell into this hole but you
*might* -
if you're lucky - still have a 'good' registry in your sysbckup folder.
(Usually the last 5 days worth)

You could try a scanreg /restore and see if there's a 'good' one -
preceding
the hole - still there.

Otherwise, its the hard way!

Mart


"George J. Wallace" wrote in message
...
Hi;
I had no luck with the system restore - it said that there were no
restore
points available. Just as additional information, I've checked my
system
with both CA antivirus and AVG and both said the system is clean.
I've
gone
through most of the macrovision kb and they have nothing about an
error
msg
that doesn't show a msg or number.
I'm going to try running an install with Process Explorer running.
I
know
that shouldn't have any background processes running during the
install
but
this may show me at what step the install is breaking or what process
it's
trying to call...gjw

"George J. Wallace" wrote in message
...
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