Windows Installer Opens at Start-Up

  • Thread starter Thread starter lehmand1
  • Start date Start date
L

lehmand1

Every time I start my computer, the Winodws Installer box
opens and trys to install PC-cillin 2000. I already have
this program in my computer so don't know why it keeps
coming up. It is as if it is stuck half-way through the
installation process and won't go away. The box says "The
feature you are trying to use is on a network resource
that is unavailable. Click OK to try again or enter an
alternate path to a folder containing the installation
package 'PNT2K.Msi'." When I hot cancel, it gives me an
Error 1706.

This causes a long delay in my start-up time and I would
like to know how to make it go away permanently. Any help
that any of you can give, will be greatly appreciated.

Thanks, Dan
 
[email protected] said:
Every time I start my computer, the Winodws Installer box
opens and trys to install PC-cillin 2000. I already have
this program in my computer so don't know why it keeps
coming up. It is as if it is stuck half-way through the
installation process and won't go away.
Click to expand...

Hi

It's most likely Windows Installer doing an on-demand installation...

See "Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand installation?"
in the FAQ at

http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx

To access the Application Log in the Event viewer,
run the following command from Start/Run:

eventvwr.msc


If you are running Windows XP (or have access to a Windows XP computer,
you can copy MSIZAP.EXE over to your Win2k computer):

If a product code is listed there and this product is not really installed,
MSIZAP.EXE is maybe able to fix this issue, it is included as a utility in
the support tools installation package (on your WinXP CD) with some additional
documentation included in suptools.chm (installed by suptools.msi).

It will remove all Windows Installer entries for a product key that you feed
it with.

Note that if MSIZAP.EXE is used incorrectly it can affect other applications
on the machine.

Based on the documentation in
http://msdn.microsoft.com/library/en-us/msi/setup/msizap_exe.asp

this is what you should run:

msizap T {product code}

an example:
msizap T {FFB37294-1155-17D3-A809-0250BAAFB1AB}
 
Back
Top