This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Thanks!
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2004
09:26 AM
Program Updates and InstallShield’s Attitude…
There is an ongoing stream of complaints concerning Program Updates. This unwelcome “feature” is installed without the user’s knowledge and permission, and apparently there is no way to remove it. This comes pretty close to the definition of spyware… Users complain about irate customers and even lost business upon discovery of Program Updates on customers’ computers.
InstallShiled have been pretty much ignoring the posts here as well as direct emails asking for a one-time utility to remove Program Updates from infected computers. There are sporadic vague references to a “feature request” but no timeline for the availability of a fix.
What do others think about how is InstallShield handling this situation? Should we start considering competitive products?
InstallShiled have been pretty much ignoring the posts here as well as direct emails asking for a one-time utility to remove Program Updates from infected computers. There are sporadic vague references to a “feature request” but no timeline for the availability of a fix.
What do others think about how is InstallShield handling this situation? Should we start considering competitive products?
(8) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2004
11:41 AM
I don't find this Update Manager to be "spyware" but a very useful tool and a great feature. Imagine every company that shipped the gdiplus.dll with security flaw would have used Update Manager - then they could easily notify thier customers and send them a fix. Sometimes I dream I wouldn't have to visit the web sites of Apple, Macromedia, Real, Adobe, etc. to make sure I'm using the latest version of their players and viewer, that include the latest security fixes.
However if you decide not to use Update Manager you can remove it from your setup with a single click as descibed in topic Disabling Automatic Update Notification for a Project
For end users who feel the need to get rid of Update Manager (and not just switch it to manual mode) I think there's knowledge base article HOWTO: Uninstall Update Manager
However if you decide not to use Update Manager you can remove it from your setup with a single click as descibed in topic Disabling Automatic Update Notification for a Project
For end users who feel the need to get rid of Update Manager (and not just switch it to manual mode) I think there's knowledge base article HOWTO: Uninstall Update Manager
Stefan Krueger
InstallSite.org
InstallSite.org
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2004
11:58 AM
Stefan,
Thank you very much fro your replay and reference to the uninstall utility – it did the job. I am still puzzled by the fact that InstallShield hasn’t bothered to reply to posts here and to emails sent to them on that topic.
There is no disagreement that Update Manger could be we good tool, if implemented correctly, i.e. as an uninstallable user option. Users of this forum reported complaints from their customers about this option appearing on their computers and not trusting it. In my case it appeared after installing a mere demo version of InstallShield that I wanted to test….
In any case, thanks again for the info.
Thank you very much fro your replay and reference to the uninstall utility – it did the job. I am still puzzled by the fact that InstallShield hasn’t bothered to reply to posts here and to emails sent to them on that topic.
There is no disagreement that Update Manger could be we good tool, if implemented correctly, i.e. as an uninstallable user option. Users of this forum reported complaints from their customers about this option appearing on their computers and not trusting it. In my case it appeared after installing a mere demo version of InstallShield that I wanted to test….
In any case, thanks again for the info.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2004
01:34 PM
So it turns out to be more of a communication problem (explain users what it is for) than a technical issue. I agree that installing Update Manager with a trial version may not be of much use. On the other hand, it's one of the features of the software you are evaluating.
Making it easier to uninstall Update Manager is a risk as it can be shared between multiple applications from multiple vendors.
Making it easier to uninstall Update Manager is a risk as it can be shared between multiple applications from multiple vendors.
Stefan Krueger
InstallSite.org
InstallSite.org
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 15, 2004
10:11 PM
You should bear in mind that that uninstall utility does not completely remove the update service. It leaves behind files and registry keys.
If the merge module were written correctly, uninstall would not be too much of a risk due to the reference counting of components.
If the merge module were written correctly, uninstall would not be too much of a risk due to the reference counting of components.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 16, 2004
09:38 AM
Can you list the files & reg. keys? thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 16, 2004
01:52 PM
The files are in %ProgramFiles%\Common Files in the InstallShield folder and the registry keys are the keys required to register the COM components for the agent. You can determine them by looking at the tables in the ISUS.msm merge module if you desire.
I'm currently working on a version of the merge module that will solve most of these installation and removal problems. If you note my post from a few days back you'll note there are serious problems with the installation using administrative installs. I hope to have this finished in a couple of days.
I hope to get InstallShield to accept my changes and replace their module with my module (it is actually much more robust and it is obvious InstallShield did not spend much effort in its development). I'm going to be willing to give it to them at no cost if they agree to support and use it.
I've had to do this because I've not had success getting them to fix what I consider fairly fundamental problems.
I'm currently working on a version of the merge module that will solve most of these installation and removal problems. If you note my post from a few days back you'll note there are serious problems with the installation using administrative installs. I hope to have this finished in a couple of days.
I hope to get InstallShield to accept my changes and replace their module with my module (it is actually much more robust and it is obvious InstallShield did not spend much effort in its development). I'm going to be willing to give it to them at no cost if they agree to support and use it.
I've had to do this because I've not had success getting them to fix what I consider fairly fundamental problems.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 18, 2007
01:11 AM
I attempted to not include the Macrovision merge module (components) Manager in my basic msi builds. It would not go away.
In 'Direct Editor' I located the Table 'IsMergeModule', and deleted the related Row. Builds then occurred without a problem.
This is no doubt a bug. I had turned of the update service altogether 'No', and also 'No' for the 'Manager' and the components kept being part of all project builds.
In 'Direct Editor' I located the Table 'IsMergeModule', and deleted the related Row. Builds then occurred without a problem.
This is no doubt a bug. I had turned of the update service altogether 'No', and also 'No' for the 'Manager' and the components kept being part of all project builds.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 18, 2007
07:03 AM
Hello Bryantlk,
Have you submitted this either via the website or through support as a bug?
Regards,
Kelly
Have you submitted this either via the website or through support as a bug?
Regards,
Kelly
bryantlk wrote:
I attempted to not include the Macrovision merge module (components) Manager in my basic msi builds. It would not go away.
In 'Direct Editor' I located the Table 'IsMergeModule', and deleted the related Row. Builds then occurred without a problem.
This is no doubt a bug. I had turned of the update service altogether 'No', and also 'No' for the 'Manager' and the components kept being part of all project builds.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)