francais
August 15th, 2004, 11:30 AM
Hi all,
I'm running Windows XP on two different computers and have installed and updated Spyware Blaster 3.2 on both without any problems. Yet on one machine, which has exactly the same software installed as the other, everytime I open Spyware Blaster it triggers the MS Installer (MSI) and attempts to install a program that I have long since removed from my PC. I get the following application error message:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 8/15/2004
Time: 13:09:55
User: N/A
Computer: WOLF
Description:
Detection of product '{057AA4D8-559F-42B1-98A0-508303834B2E}', feature '_MainFeature' failed during request for component '{22056900-C842-11D1-A0DD-00A0C9054277}'
I've thoroughly searched my registry and the MS Installer for the the entries in the error message but the searches always turn up negative.
Most puzzling is that this strange behavior is only triggered on one of my systems and not on the other.
I would really appreciate any help anyone might be able to offer toward solving this problem.
Thanks in advance for your input.
???
I'm running Windows XP on two different computers and have installed and updated Spyware Blaster 3.2 on both without any problems. Yet on one machine, which has exactly the same software installed as the other, everytime I open Spyware Blaster it triggers the MS Installer (MSI) and attempts to install a program that I have long since removed from my PC. I get the following application error message:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 8/15/2004
Time: 13:09:55
User: N/A
Computer: WOLF
Description:
Detection of product '{057AA4D8-559F-42B1-98A0-508303834B2E}', feature '_MainFeature' failed during request for component '{22056900-C842-11D1-A0DD-00A0C9054277}'
I've thoroughly searched my registry and the MS Installer for the the entries in the error message but the searches always turn up negative.
Most puzzling is that this strange behavior is only triggered on one of my systems and not on the other.
I would really appreciate any help anyone might be able to offer toward solving this problem.
Thanks in advance for your input.
???