cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
hjsunj
Level 6

Why is the uninstallation so slow?

The uninstallation process cost 2 hours! And the most time was cost at

"validating the installation.."

I don't know if this situation was caused by our project since our project has a large size 9.52GB.

So my question is:
If the project size caused this problem, do we have any way to improve the uninstallation speed?
If it's not the project size issue, how should I solve the problem?

Many thanks.
Labels (1)
0 Kudos
(11) Replies
RobertDickau
Flexera Alumni

That text is displayed while the InstallValidate action is running, and the MSI help describes what that action does.

Out of curiosity, and only for testing, does it make any difference if DISABLEROLLBACK is set?
0 Kudos
hjsunj
Level 6

Thanks, Robert!

I'll try DISABLEROLLBACK!
0 Kudos
InstallGuy007
Level 2

I've noticed that with every newer version of installshield, it seems to get slower. My software has more files and more custom actions in it but it shouldn't be this slow.

installguy,
http://www.classyselection.com
0 Kudos
RobertDickau
Flexera Alumni

Hmmmm... For an MSI project (which I gathered the question to be about), the InstallShield version used to create the installer generally shouldn't make a difference, since it's the OS/Windows Installer service that carries out the installation. The number and types of custom actions can make a difference, of course.
0 Kudos
hjsunj
Level 6

I have noticed that only Vista have the problem!
The following is the log of InstallValidate when uninstalling on Vista!

Vista

Action Start 12:58:10: InstallValidate.
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: BindImage
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: ProgId
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: SelfReg
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: Extension
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: Font
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (C0:94) [12:58:10:890]: Note: 1: 2205 2: 3: Class
MSI (s) (C0:94) [12:58:10:937]: Note: 1: 2205 2: 3: _RemoveFilePath
MSI (s) (C0:94) [14:11:35:987]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: BindImage
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: ProgId
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: SelfReg
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: Extension
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: Font
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2205 2: 3: Class
MSI (s) (C0:94) [14:11:35:987]: Note: 1: 2727 2:
MSI (s) (C0:94) [14:12:00:658]: Note: 1: 2727 2:
MSI (s) (C0:94) [14:12:00:658]: PROPERTY CHANGE: Modifying REMOVE property. Its current value is 'All'. Its new value: 'ALL'.
MSI (s) (C0:94) [14:12:00:658]: Doing action: RemoveExistingProducts
Action Finish 14:12:00: InstallValidate. Return 1.
0 Kudos
Guido_Jansen
Level 3

Content removed because of duplicate.

Guido
0 Kudos
Guido_Jansen
Level 3

Content removed because of duplicate.

Guido
0 Kudos
Guido_Jansen
Level 3

Dear,

I think I know why, at least I solved it for my installation. I have a setup with about 20.000 files. It takes more than an hour to deinstall. If I disable the RestartManager (new feature from Vista), uninstall only takes 5 minutes !!

I now disabled it systemwide (http://msdn.microsoft.com/en-us/library/aa368298(VS.85).aspx) and will do new tests with disabling it only for my application.

I think Acresso should provide an answer to why this has such a bug performance impact and how it should be improved.

Best Regards,

Guido
0 Kudos
MichaelU
Level 12 Flexeran
Level 12 Flexeran

Hi Guido, I appreciate your concern with the performance of large MSI packages. However this is determined by a conjunction of the underlying technology (Microsoft's Windows Installer) and the packaging methodology used. For the former, only Microsoft can explain or address the performance concerns. For the latter, so long as your package doesn't have unnecessary extra components and files (for example a separate component for each and every text file in a single directory), there's probably little that can be changed on your end.
0 Kudos
Guido_Jansen
Level 3

Dear Michael,

Thank you for your answer! First, in my case, I'm happy to see that with this action I can resolve the item.

About my installation, I have about 7 components, out of which 5 are dynamic ones. And still this behaviour occurs. The dynamic components refer to a rather large directory structure. What should I do to prevent that those components are so costly ?

Best Regards,

Guido
0 Kudos
MichaelU
Level 12 Flexeran
Level 12 Flexeran

Windows Installer on Windows 7 is supposed to have performance improvements. If performance is your primary concern, though, I'd recommend testing an InstallScript project (not InstallScript MSI) to see if it's more to your liking. But actually using it assumes that you are not required to generate an .msi file.
0 Kudos