Re: Windows Installer Appears every time I start spywareblaster

Hi Gls858, I did put the cd in the drive, and when I did, the installer
went away.. he did not ask me to reinstall it, I believe he meant for me to
see what happens when I find the file it was asking for.

I followed his instructions..:) I try really hard to follow all the advice
and instructions that are given to me..and I appreciate all the help.. it is
the only source of help I have when I have a problem on my computer..
perhaps I misunderstood what he was asking me to do.. that's always a
possibility..:) thanks Rainy

"gls858" <gls858@xxxxxxxxx> wrote in message
news:uoQ1SvM4FHA.472@xxxxxxxxxxxxxxxxxxxxxxx
> Rainy wrote:
>> Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
>> see it..even now when I am making an effort to read in detail, this is
>> the only post I see on the 29th from Wes... I have been known to jump
>> over critical information in the past. and I could be doing that here,
>> and I do apologize if this is what I have done. I thought in this post
>> he was asking what happens if you let windows installer do it's thing,
>> and what was the event that pertained to spywareblaster, which I found.
>> I am just glad to have it fixed! Rainy
>>
>> "Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
>> news:%23Mu8cBN3FHA.3844@xxxxxxxxxxxxxxxxxxxxxxx
>>> Some times the Windows Installer launches when an application is corrupt
>>> and
>>> it launches when you start a totally unrelated program.
>>>
>>> What happens if you let Windows Installer do it's thing.
>>>
>>> [[Troubleshooting
>>> Q. Every time I launch my application, Windows Installer performs an
>>> installation. How can I determine the cause of the on-demand
>>> installation?
>>>
>>> A. An easy way to determine the cause of an on-demand installation is to
>>> look in the application event log for MsiInstaller log messages of the
>>> form:
>>>
>>> Event Type: Warning
>>> Event Source: MsiInstaller
>>> Event ID: 1001
>>> Description:
>>> Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
>>> 'Example' failed during request for component
>>> '{00030829-0000-0000-C000-000000000046}'
>>>
>>> Event Type: Warning
>>> Event Source: MsiInstaller
>>> Event ID: 1004
>>> Description:
>>> Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
>>> 'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
>>> The
>>> resource 'C:\Progam Files\example\example.exe' does not exist.
>>>
>>> The first message (with event ID 1001) states which component was being
>>> installed. The component listed here is the component named in the
>>> Component_ column of the Shortcut table for the particular shortcut.
>>>
>>> The second message (with event ID 1004) indicates which component failed
>>> detection. Improved event logging in Windows Installer 2.0 has updated
>>> the
>>> message so that in most cases, the message identifies the actual
>>> resource
>>> that resulted in the failed detection. The component with the missing or
>>> damaged keypath is the component that is triggering the reinstallation.
>>>
>>> In the example above, the reinstallation is triggered because the
>>> resource
>>> 'c:\Program Files\example\example.exe' does not exist. You would then
>>> need
>>> to find out why the keypath does not exist -in this case, the user
>>> deleted
>>> it.]]
>>> Frequently Asked Questions About Windows Installer
>>> http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
>>>
>>> --
>>> Hope this helps. Let us know.
>>>
>>> Wes
>>> MS-MVP Windows Shell/User
>>
>>
> Actually I looked at the wrong date it was 10/31 not 10/29
>
> Excerpt from post:
>
> Do you have Office 2003?
>
> Stick the CD in the drive the next time Windows Installer asks for
> PRO11.MSI.



.

Relevant Pages

  • RE: Windows installer on SBS server 2003 SP2
    ... "The Windows Installer Service could not be accessed. ... Windows Installer Service cannot be started correctly. ... Verify that the SYSTEM/administrators account has been added and that it has Full control. ...
    (microsoft.public.windows.server.sbs)
  • Re: New Imformation on System Restore & Windows Installer Registry Corruption
    ... html bar click in and think since I'm not using any html selection (bold, ... 2003 Updates and other Office version updates, ... After running the Installer Clean utility to remove remnants of OfficeXP, ... > Windows Installer version 1.0 to Windows Installer version 1.1. ...
    (microsoft.public.windowsxp.customize)
  • Re: UNABLE TO CHECK FOR UPDATES ON THIS COMPUTER
    ... Running the Windows Installer Cleanup Utility should take care of the patch ... i did download the windows installer cleanup utility w/o ... >There are some known issues with the Office Update site. ...
    (microsoft.public.officeupdate)
  • Re: New Imformation on System Restore & Windows Installer Registry Corruption
    ... html bar click in and think since I'm not using any html selection (bold, ... 2003 Updates and other Office version updates, ... After running the Installer Clean utility to remove remnants of OfficeXP, ... > Windows Installer version 1.0 to Windows Installer version 1.1. ...
    (microsoft.public.windowsxp.basics)
  • Re: Removal/Install Office 2000
    ... You might try the Windows Installer Cleanup Utility, ... >> This problem may occur if the registry contains Microsoft Windows ...
    (microsoft.public.office.setup)