Windows Installer Appears every time I start spywareblaster

[Rainy]

I posted a few days ago about this problem, but no one has responded..and
that is my fault.. I had TROJANS in the subject line but my question was
about the Windows Installer so I am reposting! I have tried to sort this
out by myself.. and found the information below .. I followed along and
thought I was getting somewhere, but Windows Installer still Appears Every
Time I click on Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I appreciate any
help..this is very annoying.. thanks Rainy ps. I followed along with
Solution 2 but it did not work! I didn't think Solution 1 applied to my
situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many Microsoft
products, including Office 2000 and Office XP, and is even available to
third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency to
appear every time you start Office (or some other programs) and begin a
reinstallation or reconfiguration process. All you'll see is the "Please
Wait" screen, followed by a progress bar. The problem is related to the This
feature will be installed when required option (sometimes called "Install on
Demand"), used when installing some applications. In essense, Windows
Installer starts to install a "feature" when it is needed, even though it
may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge that
there is a serious flaw in thier installer software. Here are the solutions
we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the This
feature will be installed when required for any of the optional components.
However, this may not solve the problem (which is the very bug we're talking
about). We're currently looking for a way to fix the problem properly, but
in the mean time, here's how to turn off the "feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start Menu, and
typing gpedit.msc. (If the file is missing, run mmc.exe instead. Then,
select Add/Remove Snap-in from the Console menu, click Add, and double-click
Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative Templates
\ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap in, as
described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy the
next time you try to install an application, you'll have to re-enable the
Windows Installer temporarily

 

[Wesley Vogel]

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

In

 

[Rainy]

I responded to some help on this.. but haven't heard what to do next.. Does
anyone know anything else to suggest? I would really like to resolve this
issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed it in
system32. and actually thought I was home free.. but Microsoft Installer is
still coming up.. not sure what it is asking me to do. but this is the
screenshot.. It appears to me asking me for PRO11MSI... I have no idea where
to find this... I am sure I did not delete or remove this path.. this isn't
something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster, and
the same thing happens.. fortunately I can click cancel a few times and the
installer goes away... but still it is annoying! Thanks Rainy

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

In

I posted a few days ago about this problem, but no one has responded..and
that is my fault.. I had TROJANS in the subject line but my question was
about the Windows Installer so I am reposting! I have tried to sort
this out by myself.. and found the information below .. I followed along
and thought I was getting somewhere, but Windows Installer still Appears
Every Time I click on Spywareblaster. Windows Installer has done this
with other applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I followed
along with Solution 2 but it did not work! I didn't think Solution 1
applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency to
appear every time you start Office (or some other programs) and begin a
reinstallation or reconfiguration process. All you'll see is the "Please
Wait" screen, followed by a progress bar. The problem is related to the
This feature will be installed when required option (sometimes called
"Install on Demand"), used when installing some applications. In essense,
Windows Installer starts to install a "feature" when it is needed, even
though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the very
bug we're talking about). We're currently looking for a way to fix the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap in, as
described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy the
next time you try to install an application, you'll have to re-enable the
Windows Installer temporarily

 

[Wesley Vogel]

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I responded to some help on this.. but haven't heard what to do next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed it
in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do. but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or remove
this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster, and
the same thing happens.. fortunately I can click cancel a few times and
the installer goes away... but still it is annoying! Thanks Rainy

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

In

I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line but
my question was about the Windows Installer so I am reposting! I
have tried to sort this out by myself.. and found the information below
.. I followed along and thought I was getting somewhere, but Windows
Installer still Appears Every Time I click on Spywareblaster. Windows
Installer has done this with other applications as well.. sort of comes
up at the wrong time.. I appreciate any help..this is very annoying..
thanks Rainy ps. I followed along with Solution 2 but it did not work!
I didn't think Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency to
appear every time you start Office (or some other programs) and begin a
reinstallation or reconfiguration process. All you'll see is the "Please
Wait" screen, followed by a progress bar. The problem is related to the
This feature will be installed when required option (sometimes called
"Install on Demand"), used when installing some applications. In
essense, Windows Installer starts to install a "feature" when it is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the very
bug we're talking about). We're currently looking for a way to fix the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap in,
as described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy the
next time you try to install an application, you'll have to re-enable
the Windows Installer temporarily

 

[Rainy]

Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as I
sent it I checked to see the post, and it was there.. not sure what happen
to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of hard
drive space) I have already put in the cd when the installer came up, and
it went away, but came back the next time I clicked on Spywareblaster. I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems or
less bugs, is that possible? Thanks Rainy ps. this is not the only program
that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I responded to some help on this.. but haven't heard what to do next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed it
in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do. but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or remove
this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster, and
the same thing happens.. fortunately I can click cancel a few times and
the installer goes away... but still it is annoying! Thanks Rainy

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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line but
my question was about the Windows Installer so I am reposting! I
have tried to sort this out by myself.. and found the information below
.. I followed along and thought I was getting somewhere, but Windows
Installer still Appears Every Time I click on Spywareblaster. Windows
Installer has done this with other applications as well.. sort of comes
up at the wrong time.. I appreciate any help..this is very annoying..
thanks Rainy ps. I followed along with Solution 2 but it did not work!
I didn't think Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency to
appear every time you start Office (or some other programs) and begin a
reinstallation or reconfiguration process. All you'll see is the
"Please
Wait" screen, followed by a progress bar. The problem is related to the
This feature will be installed when required option (sometimes called
"Install on Demand"), used when installing some applications. In
essense, Windows Installer starts to install a "feature" when it is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the very
bug we're talking about). We're currently looking for a way to fix the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap in,
as described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy
the
next time you try to install an application, you'll have to re-enable
the Windows Installer temporarily

 

[Wesley Vogel]

This may be worth a shot.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as I
sent it I checked to see the post, and it was there.. not sure what
happen to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of hard
drive space) I have already put in the cd when the installer came up, and
it went away, but came back the next time I clicked on Spywareblaster. I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems or
less bugs, is that possible? Thanks Rainy ps. this is not the only
program that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I responded to some help on this.. but haven't heard what to do next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed
it in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do. but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or remove
this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster,
and the same thing happens.. fortunately I can click cancel a few times
and the installer goes away... but still it is annoying! Thanks Rainy


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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line
but my question was about the Windows Installer so I am reposting!
I have tried to sort this out by myself.. and found the
information below .. I followed along and thought I was getting
somewhere, but Windows Installer still Appears Every Time I click on
Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I
followed along with Solution 2 but it did not work! I didn't think
Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency to
appear every time you start Office (or some other programs) and begin
a reinstallation or reconfiguration process. All you'll see is the
"Please
Wait" screen, followed by a progress bar. The problem is related to
the This feature will be installed when required option (sometimes
called "Install on Demand"), used when installing some applications.
In essense, Windows Installer starts to install a "feature" when it is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the very
bug we're talking about). We're currently looking for a way to fix the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap in,
as described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy
the
next time you try to install an application, you'll have to re-enable
the Windows Installer temporarily

 

[Rainy]

apparently I have a policy against this installation.. where do I go to
change the policy? Is the website saying that I would have to reinstall all
the programs that have been installed using that installer? thanks Wes
appreciate the help.. Rainy

This may be worth a shot.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as I
sent it I checked to see the post, and it was there.. not sure what
happen to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of hard
drive space) I have already put in the cd when the installer came up,
and
it went away, but came back the next time I clicked on Spywareblaster. I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems or
less bugs, is that possible? Thanks Rainy ps. this is not the only
program that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
I responded to some help on this.. but haven't heard what to do next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed
it in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do.
but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or remove
this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster,
and the same thing happens.. fortunately I can click cancel a few times
and the installer goes away... but still it is annoying! Thanks Rainy


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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line
but my question was about the Windows Installer so I am reposting!
I have tried to sort this out by myself.. and found the
information below .. I followed along and thought I was getting
somewhere, but Windows Installer still Appears Every Time I click on
Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I
followed along with Solution 2 but it did not work! I didn't think
Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency
to
appear every time you start Office (or some other programs) and begin
a reinstallation or reconfiguration process. All you'll see is the
"Please
Wait" screen, followed by a progress bar. The problem is related to
the This feature will be installed when required option (sometimes
called "Install on Demand"), used when installing some applications.
In essense, Windows Installer starts to install a "feature" when it
is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the
This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the
very
bug we're talking about). We're currently looking for a way to fix
the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap
in,
as described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy
the
next time you try to install an application, you'll have to re-enable
the Windows Installer temporarily

 

[Wesley Vogel]

These two, I think.

Start | Run | Type: gpedit.msc | Click OK |
Navigate to >>
Local Computer Policy\Computer Configuration\Administrative
Templates\Windows Components\Windows Installer\
and
Local Computer Policy\User Configuration\Administrative Templates\Windows
Components\Windows Installer\

Always install with elevated privileges
[[Note: This setting appears both in the Computer Configuration and User
Configuration folders. To make this setting effective, you must enable the
setting in both folders.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

apparently I have a policy against this installation.. where do I go to
change the policy? Is the website saying that I would have to reinstall
all the programs that have been installed using that installer? thanks
Wes appreciate the help.. Rainy

This may be worth a shot.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as I
sent it I checked to see the post, and it was there.. not sure what
happen to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of
hard drive space) I have already put in the cd when the installer came
up, and
it went away, but came back the next time I clicked on Spywareblaster. I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems or
less bugs, is that possible? Thanks Rainy ps. this is not the only
program that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
I responded to some help on this.. but haven't heard what to do next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting
module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and installed
it in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do.
but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or
remove this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster,
and the same thing happens.. fortunately I can click cancel a few
times and the installer goes away... but still it is annoying!
Thanks Rainy


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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line
but my question was about the Windows Installer so I am reposting!
I have tried to sort this out by myself.. and found the
information below .. I followed along and thought I was getting
somewhere, but Windows Installer still Appears Every Time I click
on Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I
followed along with Solution 2 but it did not work! I didn't
think Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency
to
appear every time you start Office (or some other programs) and
begin a reinstallation or reconfiguration process. All you'll see
is the "Please
Wait" screen, followed by a progress bar. The problem is related to
the This feature will be installed when required option (sometimes
called "Install on Demand"), used when installing some applications.
In essense, Windows Installer starts to install a "feature" when it
is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the
This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the
very
bug we're talking about). We're currently looking for a way to fix
the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap
in,
as described above, you don't need to "save changes to the console."

e.. Note: If you encounter an error about the Administrator Policy
the
next time you try to install an application, you'll have to
re-enable the Windows Installer temporarily

 

[Rainy]

Hi.. I want you to know how much I appreciate the help.. but unfortunately..
it did not work.. I enabled "always install with elevated privileges" on
both of these, and tried to download the Windows installer cleanup utility
and it gave me the same prompt "The system Administrator has set policies to
prevent this installation" So there must be other places in group policy to
enable or ... disable.. I was so hoping to have this issue resolved.. and
appreciate any help I receive! Rainy

These two, I think.

Start | Run | Type: gpedit.msc | Click OK |
Navigate to >>
Local Computer Policy\Computer Configuration\Administrative
Templates\Windows Components\Windows Installer\
and
Local Computer Policy\User Configuration\Administrative Templates\Windows
Components\Windows Installer\

Always install with elevated privileges
[[Note: This setting appears both in the Computer Configuration and User
Configuration folders. To make this setting effective, you must enable the
setting in both folders.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

apparently I have a policy against this installation.. where do I go to
change the policy? Is the website saying that I would have to reinstall
all the programs that have been installed using that installer? thanks
Wes appreciate the help.. Rainy

This may be worth a shot.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as
I
sent it I checked to see the post, and it was there.. not sure what
happen to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of
hard drive space) I have already put in the cd when the installer came
up, and
it went away, but came back the next time I clicked on Spywareblaster.
I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems
or
less bugs, is that possible? Thanks Rainy ps. this is not the only
program that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
I responded to some help on this.. but haven't heard what to do
next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting
module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and
installed
it in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do.
but
this is the screenshot.. It appears to me asking me for PRO11MSI... I
have no idea where to find this... I am sure I did not delete or
remove this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled spywareblaster,
and the same thing happens.. fortunately I can click cancel a few
times and the installer goes away... but still it is annoying!
Thanks Rainy


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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject line
but my question was about the Windows Installer so I am reposting!
I have tried to sort this out by myself.. and found the
information below .. I followed along and thought I was getting
somewhere, but Windows Installer still Appears Every Time I click
on Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I
followed along with Solution 2 but it did not work! I didn't
think Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is
even
available to third-party developers to include with their programs.
Unfortunately, it's fraught with bugs, one of which is its tendency
to
appear every time you start Office (or some other programs) and
begin a reinstallation or reconfiguration process. All you'll see
is the "Please
Wait" screen, followed by a progress bar. The problem is related to
the This feature will be installed when required option (sometimes
called "Install on Demand"), used when installing some
applications.
In essense, Windows Installer starts to install a "feature" when it
is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the
This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the
very
bug we're talking about). We're currently looking for a way to fix
the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe
instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap
in,
as described above, you don't need to "save changes to the
console."

e.. Note: If you encounter an error about the Administrator
Policy
the
next time you try to install an application, you'll have to
re-enable the Windows Installer temporarily

 

[Rainy]

Hi.. I was trying to figure this out and came apon a site that has the
download for windows installer...
http://www.softwarepatch.com/windows/wininstallnt.html

and would like to know if anyone thinks this will fix the problem or if the
problem is on my computer and the same thing will occur? thanks Rainy

Hi.. I want you to know how much I appreciate the help.. but
unfortunately..
it did not work.. I enabled "always install with elevated privileges" on
both of these, and tried to download the Windows installer cleanup utility
and it gave me the same prompt "The system Administrator has set policies
to
prevent this installation" So there must be other places in group policy
to
enable or ... disable.. I was so hoping to have this issue resolved.. and
appreciate any help I receive! Rainy

These two, I think.

Start | Run | Type: gpedit.msc | Click OK |
Navigate to >>
Local Computer Policy\Computer Configuration\Administrative
Templates\Windows Components\Windows Installer\
and
Local Computer Policy\User Configuration\Administrative Templates\Windows
Components\Windows Installer\

Always install with elevated privileges
[[Note: This setting appears both in the Computer Configuration and User
Configuration folders. To make this setting effective, you must enable
the
setting in both folders.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

apparently I have a policy against this installation.. where do I go to
change the policy? Is the website saying that I would have to reinstall
all the programs that have been installed using that installer? thanks
Wes appreciate the help.. Rainy
This may be worth a shot.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
Hi Wes, sorry, I had a screenshot embedded when I sent it..as soon as
I
sent it I checked to see the post, and it was there.. not sure what
happen to it.. thanks for responding...

I did have MS Office but have uninstalled it..(I don't have a lot of
hard drive space) I have already put in the cd when the installer
came
up, and
it went away, but came back the next time I clicked on Spywareblaster.
I
honestly don't know what to do next. My thought was maybe there is a
alternate Windows installer that can be downloaded with less problems
or
less bugs, is that possible? Thanks Rainy ps. this is not the only
program that the windows Installer has come up uninvited..

I do not see a screenshot or a link to a screenshot.

MSVBVM60.DLL is Microsoft Visual Basic Virtual Machine dll file.

*.MSI files are Windows Installer Packages.

PRO11.MSI is for Microsoft Office 2003.

Do you have Office 2003?

Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Rainy <[email protected]> hunted and pecked:
I responded to some help on this.. but haven't heard what to do
next..
Does anyone know anything else to suggest? I would really like to
resolve this issue... thanks Rainy

Hi Wes.. thanks so much for the response.. I found the event log for
MsiInstaller.. and this is what it said:

Faulting application spywareblaster.exe. version 3.40.0 faulting
module

MSVBVM60.DLL IS version6.097.82 fault address 0x00044177

I assumed the dll was corrupt, so I found the dll online and
installed
it in system32. and actually thought I was home free.. but Microsoft
Installer is still coming up.. not sure what it is asking me to do.
but
this is the screenshot.. It appears to me asking me for PRO11MSI...
I
have no idea where to find this... I am sure I did not delete or
remove this path.. this isn't something I would do..

I hope this helps you to help me.. I have reinstalled
spywareblaster,
and the same thing happens.. fortunately I can click cancel a few
times and the installer goes away... but still it is annoying!
Thanks Rainy


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

In Rainy <[email protected]> hunted and pecked:
I posted a few days ago about this problem, but no one has
responded..and that is my fault.. I had TROJANS in the subject
line
but my question was about the Windows Installer so I am reposting!
I have tried to sort this out by myself.. and found the
information below .. I followed along and thought I was getting
somewhere, but Windows Installer still Appears Every Time I click
on Spywareblaster. Windows Installer has done this with other
applications as well.. sort of comes up at the wrong time.. I
appreciate any help..this is very annoying.. thanks Rainy ps. I
followed along with Solution 2 but it did not work! I didn't
think Solution 1 applied to my situation.


Intended For
Windows XP
Windows 2000

The Windows Installer is a global application used to install many
Microsoft products, including Office 2000 and Office XP, and is
even
available to third-party developers to include with their
programs.
Unfortunately, it's fraught with bugs, one of which is its
tendency
to
appear every time you start Office (or some other programs) and
begin a reinstallation or reconfiguration process. All you'll see
is the "Please
Wait" screen, followed by a progress bar. The problem is related
to
the This feature will be installed when required option (sometimes
called "Install on Demand"), used when installing some
applications.
In essense, Windows Installer starts to install a "feature" when
it
is
needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not
acknowledge
that
there is a serious flaw in thier installer software. Here are the
solutions we've come up with so far:

Solution #1:

a.. Reinstall the application in question, and don't choose the
This
feature will be installed when required for any of the optional
components. However, this may not solve the problem (which is the
very
bug we're talking about). We're currently looking for a way to fix
the
problem properly, but in the mean time, here's how to turn off the
"feature:"

Solution #2

a.. Open the Group Policy Editor by selecting Run from the Start
Menu,
and typing gpedit.msc. (If the file is missing, run mmc.exe
instead.
Then,
select Add/Remove Snap-in from the Console menu, click Add, and
double-click Group Policy. Click Finish, then Close, then Ok.)
b.. Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative
Templates \ Windows Components \ Windows Installer
c.. Double-click Disable Windows Installer to your right, click
Enabled,
and choose Always from the list. Click Ok when you're done.
d.. The change will take effect immediately. If you added a snap
in,
as described above, you don't need to "save changes to the
console."

e.. Note: If you encounter an error about the Administrator
Policy
the
next time you try to install an application, you'll have to
re-enable the Windows Installer temporarily

 

[Sharon F]

Hi.. I was trying to figure this out and came apon a site that has the
download for windows installer...
http://www.softwarepatch.com/windows/wininstallnt.html

and would like to know if anyone thinks this will fix the problem or if the
problem is on my computer and the same thing will occur?

Wesley is doing a fine job of helping you. Just wanted to mention (besides
the fact that this blocking of the permissions is very odd and probably the
"nut" of your issue) ... I know nothing good or bad about
softwarepatch.com but in general I'm not fond of tracking down MS updates
from any site but MS.

For the installer:
Version 3.0 is a part of Service Pack 2
Update to version 3.1 was offered through Windows Update. If unable to use
Windows Update for whatever reason, the same package is available from
Microsoft's download site:
http://www.microsoft.com/downloads/search.aspx?displaylang=en

Direct download link for version 3.1:
http://www.microsoft.com/downloads/...fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en

Knowledge Base article about the update:
http://support.microsoft.com/?id=893803

And you already have the link for the installer cleanup tool...

 

[Rainy]

thanks Sharon..Yes he is doing a great job ... I am wondering if SP2 is the
root of my problem.. I have heard a lot of negative about it.. and it seems
to me that my trouble with the installer came with SP2..

Or could I just remove the installer and use something else? an alternate
like I mentioned in another post... thanks Rainy

 

[Rainy]

I'm wondering if this might be the reason the installer comes up...the other
path that comes up in the installer is D:\MSOCache and I just did a search
to find out what it is.. Appears to be Microsoft Office 2003 installation
media that was put into a folder on my storage hard drive so that I would
not have to insert the cd during installation and maintenance.. and I can
remove this using Disk Cleanup...I see no reason to keep these files.. I
have no idea that this is the reason it's coming up.. but seems funny to me,
that it is asking for files for a program I no longer have... It may not
have anything to do with it.. but I am going to try.. I will get back to
you.. thanks for all the help.. Rainy

 

[Sharon F]

thanks Sharon..Yes he is doing a great job ... I am wondering if SP2 is the
root of my problem.. I have heard a lot of negative about it.. and it seems
to me that my trouble with the installer came with SP2..

Or could I just remove the installer and use something else? an alternate
like I mentioned in another post... thanks Rainy

I don't think SP2 is the root of the problem. Possibly a problem with the
installer. The installer is a common mechanism that programmer's tap into
to get their "setup.exe" files to install their software on your system
(some programmer's are better at accessing the installer's features than
others).

If an alternative is used, it's packed into the software's installation
executable (such as setup.exe). It's not something that you would add to
your system.

One of the reason's I gave you the links for the Windows installer is that
just like Windows components, sometimes reinstalling will "fix" odd
problems. I thought that's where you were going with it anyhow.

Between running the repair (which failed but might work after a reinstall?)
and reinstalling the installer (gee, that sounds redundant), maybe things
would fall back into place for you?

 

[Sharon F]

I'm wondering if this might be the reason the installer comes up...the other
path that comes up in the installer is D:\MSOCache and I just did a search
to find out what it is.. Appears to be Microsoft Office 2003 installation
media that was put into a folder on my storage hard drive so that I would
not have to insert the cd during installation and maintenance.. and I can
remove this using Disk Cleanup...I see no reason to keep these files.. I
have no idea that this is the reason it's coming up.. but seems funny to me,
that it is asking for files for a program I no longer have... It may not
have anything to do with it.. but I am going to try.. I will get back to
you.. thanks for all the help.. Rainy

The MSOCache folder is a spare copy of the files needed to install MS
Office. It is used by Office to perform "on the fly" repairs. No problems
result from deleting it other than having to find the MS Office CD when/if
a repair is needed or when some Office updates are performed.

 

[Rainy]

for some reason.. the MSOcache is greyed out when I go to disk cleanup.. is
there any harm in manually deleting it? I won't need these files.. the only
one I wanted was word, so I could have spellcheck for OE.. but I can do
without it.. Manual delete ok? thanks Sharon.. Rainy

 

[Rainy]

Hi Sharon, I just tried to reinstall the installer and found that the
administrator has set policies against this.. My goodness we are just going
round in circles aren't we..? This is so frustrating I can't begin to tell
you.. I do appreciate you responding.. and to tell you the truth, I was
wondering where "my tech" was.. thanks Sharon.. Rainy ps. not to say I don't
appreciate other techs too!

 

[Sharon F]

for some reason.. the MSOcache is greyed out when I go to disk cleanup.. is
there any harm in manually deleting it? I won't need these files.. the only
one I wanted was word, so I could have spellcheck for OE.. but I can do
without it.. Manual delete ok? thanks Sharon.. Rainy

It's normal for the folder to be greyed out. On my tablet PC, I deleted the
folder (limited hard drive space). On my desktop, I keep the folder.
Technically it would probably make more sense to do it the other way around
since the CD is handy at home but not when I'm out and about with the
portable.

For the permissions problem: Check this thread out from the Expert's
Exchange. They go over several checkpoints for "unblocking" installs. The
"gpedit.msc" tool they refer to is in XP Pro (not Home):

http://www.experts-exchange.com/Operating_Systems/Q_21539332.html

 

[Sharon F]

and to tell you the truth, I was
wondering where "my tech" was.. thanks Sharon.. Rainy ps. not to say I don't
appreciate other techs too!

Since you were wondering... Have a new nephew (5 days old) that needs
visiting and spend quite a bit of time exploring and learning more about
Vista these days (http://www.microsoft.com/windowsvista/default.mspx)

 

[Rainy]

You must be a subscriber.. I can't see the solution..
I had a friend send me his msiexec.exe I think that is what it is called..
too early for me here.. lol and I am going to try and drag it to the right
folder, assuming mine is corrupted.. I might need to rename the old one
first.. but I will see how that goes.. I will try and delete the MSOcache
folder.. this is really a crazy problem you know? Rainy