False Windows Install action on XP Boot

Some days afterloading XP SP2 & Office 2003, my PC started showing a Windows
Installer splash screen on boot. This is delaying boot by about 3 to 5
minutes. Taking the cancel option does not speed it up. I tried system
restore to no avail. Help!

Harvey M wrote:

> Some days afterloading XP SP2 & Office 2003, my PC started showing a Windows
> Installer splash screen on boot. This is delaying boot by about 3 to 5
> minutes. Taking the cancel option does not speed it up. I tried system
> restore to no avail. Help!
Hi

Most likely it is 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...t/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...msizap_exe.asp

this is what you should run:

msizap T {product code}

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


Alternatively, for a more user friendly interface to MSIZAP.EXE ,
take a look at this article:

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default...b;en-us;290301


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Thankyou Torgair
I have found the reference and will try it out tonight

Harvey

"Torgeir Bakken (MVP)" wrote:

> Harvey M wrote:
>
> > Some days afterloading XP SP2 & Office 2003, my PC started showing a Windows
> > Installer splash screen on boot. This is delaying boot by about 3 to 5
> > minutes. Taking the cancel option does not speed it up. I tried system
> > restore to no avail. Help!
> Hi
>
> Most likely it is 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...t/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...msizap_exe.asp
>
> this is what you should run:
>
> msizap T {product code}
>
> an example:
> msizap T {FFB37294-1155-17D3-A809-0250BAAFB1AB}
>
>
> Alternatively, for a more user friendly interface to MSIZAP.EXE ,
> take a look at this article:
>
> Description of the Windows Installer CleanUp Utility
> http://support.microsoft.com/default...b;en-us;290301
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Torgeir
I investigated as you suggested and found 2900 incidents from running
eventvwr.msc. These are typicallyu as warnings:-

Source, ESSENT"wuavclt(1448) database engine stopped"

and information:-
Source WinMgmt "A provider, OffProv11, has bneen registered in the WMI
namespace. Root \MSAPPS11, to use the local systems account. This account
is priviledged and the provider may cause a secdurity violation if it does
not correctly impersonate user requests"

These leave me (a simple engineering manager trained as a mechanical
engineer!) a little confused so I must do some heavy thinking before I go
further!

Regards

Harvey



"Torgeir Bakken (MVP)" wrote:

> Harvey M wrote:
>
> > Some days afterloading XP SP2 & Office 2003, my PC started showing a Windows
> > Installer splash screen on boot. This is delaying boot by about 3 to 5
> > minutes. Taking the cancel option does not speed it up. I tried system
> > restore to no avail. Help!
> Hi
>
> Most likely it is 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...t/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...msizap_exe.asp
>
> this is what you should run:
>
> msizap T {product code}
>
> an example:
> msizap T {FFB37294-1155-17D3-A809-0250BAAFB1AB}
>
>
> Alternatively, for a more user friendly interface to MSIZAP.EXE ,
> take a look at this article:
>
> Description of the Windows Installer CleanUp Utility
> http://support.microsoft.com/default...b;en-us;290301
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Harvey M wrote:

> Torgeir
> I investigated as you suggested and found 2900 incidents from running
> eventvwr.msc. These are typicallyu as warnings:-
>
> Source, ESSENT"wuavclt(1448) database engine stopped"
>
> and information:-
> Source WinMgmt "A provider, OffProv11, has bneen registered in the WMI
> namespace. Root \MSAPPS11, to use the local systems account. This account
> is priviledged and the provider may cause a secdurity violation if it does
> not correctly impersonate user requests"
>
> These leave me (a simple engineering manager trained as a mechanical
> engineer!) a little confused so I must do some heavy thinking before I go
> further!
Hi

Those events you list above is not relevant to the Windows Installer
problem you have.

The Q/A "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...t/msi_faq.mspx
explains what type of event to look for.



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Thankyou Torgeir

I just noticed that my HDD has magically double it's used size so I think my
problems are best resolved by a clean install on a larger disk.

Thanks again

Harvey

"Torgeir Bakken (MVP)" wrote:

> Harvey M wrote:
>
> > Torgeir
> > I investigated as you suggested and found 2900 incidents from running
> > eventvwr.msc. These are typicallyu as warnings:-
> >
> > Source, ESSENT"wuavclt(1448) database engine stopped"
> >
> > and information:-
> > Source WinMgmt "A provider, OffProv11, has bneen registered in the WMI
> > namespace. Root \MSAPPS11, to use the local systems account. This account
> > is priviledged and the provider may cause a secdurity violation if it does
> > not correctly impersonate user requests"
> >
> > These leave me (a simple engineering manager trained as a mechanical
> > engineer!) a little confused so I must do some heavy thinking before I go
> > further!
> Hi
>
> Those events you list above is not relevant to the Windows Installer
> problem you have.
>
> The Q/A "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...t/msi_faq.mspx
> explains what type of event to look for.
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>