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
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: update.exe V E R Y Y Y slow for large patches
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 20, 2008
07:17 PM
update.exe V E R Y Y Y slow for large patches
I notice that it takes 1 - 2 minutes from the time I double click on Update.exe to the time that the prompt to run the exe appears on Windows XP. The patch / service pack is large, weighing in just under 300 MB and I know it has something to do with windows explorer.
I cannot reduce the size of the patch, unfortunately. However, is there anything I can do to help alleviate the pain for the consumer? The patch will be downloaded from the web. Is there a way to display an hourglass or give some indication that update.exe is running?
Most users are going to double click on this package 100 times and then call tech support telling us that the patch does not work.
I cannot reduce the size of the patch, unfortunately. However, is there anything I can do to help alleviate the pain for the consumer? The patch will be downloaded from the web. Is there a way to display an hourglass or give some indication that update.exe is running?
Most users are going to double click on this package 100 times and then call tech support telling us that the patch does not work.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2008
02:20 AM
you know how it works... if it cannot be fixed it is documented 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2008
10:40 AM
If it's taking a long time between double-click of update.exe and a prompt from Windows as to whether it should be allowed to run, this is probably due to Windows verifying a digital signature on the exe. Try removing the signature (or building without it), and see if the behavior changes. If that results in preferable behavior, though, You'll have to weigh the options between performance and digital signature's security.