I distribute a freeware Visual Basic application which uses Wise installer.
It has been install on 10s of thousands of PCs over three years with few
problems. However, I have one user with Windows XP Pro and Office XP who
has developed a problem.
The freeware app was downloaded and installed and worked properly.
Suddenly, various functions in office, such as clicking on a link in an
email in outlook, or (I think) clicking the save button on Word launches the
application installer. If we cancel the applicaition install or let it
finish, it does not seem to make a difference, it keeps prompting for the
install.
We have tried to run spyware apps, anti virus scans,
reinstalling/uninstalling the freeware app but the problem will not go away.
We have not tried to reinstall Office or run repair in Office.
Does anyone have any information as too what could be causing this?
Thanks
Stephen
Vince Averello [MVP-Outlook] - 10 Nov 2005 18:52 GMT
Check your key paths or files to see if anything is causing them to be
changed which would trigger an MSI repair operation
>I distribute a freeware Visual Basic application which uses Wise installer.
> It has been install on 10s of thousands of PCs over three years with few
[quoted text clipped - 21 lines]
>
> Stephen
Stephen Simpson - 10 Nov 2005 20:11 GMT
It is strange to me that something in outlook is calling up the setup for
the Freeware application which was downloaded from the internet. I do not
even know where the setup program is being called f rom.
Stephen
> Check your key paths or files to see if anything is causing them to be
> changed which would trigger an MSI repair operation
[quoted text clipped - 25 lines]
>>
>> Stephen
Vince Averello [MVP-Outlook] - 10 Nov 2005 22:53 GMT
Did you write the installer? If so, crack it open and check out the MSI's
key paths & such. If you didn't write the installer it might be a bit
difficult to debug
> It is strange to me that something in outlook is calling up the setup for
> the Freeware application which was downloaded from the internet. I do not
> even know where the setup program is being called f rom.