Within the HKEY_CLASSES_ROOT\Installer\Products\ registry key a VALUE exists that connects the MSI to it's transform MST file so removing this VALUE will allow the normal un-install process to complete. Fix: Break the link between the transform and the MSI. Whichever setting this property is affecting it allowed the install but not the un-install. Reason: Rogue property set via an MST transform on install.Ī PROPERTY was found that was set via a transform when the original application was installed ADDDEFAULT=ALL. Using MSIZap seems to work but the subsequent install of the next version results in mis-match errors. On 30+ servers a vendor supplied MSI needed to be updated to the next version however the application would not un-install using any standard removal methods with various switches and will not upgrade to the next version.
Remove Registry VALUE on Install in Basic MSI Problem: Existing install of an MSI application will not un-install. I decided on a vbscript in a custom action to the remove the folder and all it's contents, triggered when the application is uninstalled.Ĭreate a VBScript Custom Action that is stored within the CA and complete as per below, you can find the VBScript here. Fix: Script the removal of the folder during uninstall.
Natively an MSI will only remove files that were installed by itself.or if they've been added to the removefiles table, however we have no idea of the name of the files that will need to be removed so we need a catch all solution. The application is a standard client/server setup with application updates being applied to the server which then disseminate to all clients which means files are present on the client that weren't put there by the MSI itself.
Delete Folder on Uninstall of MSI Problem: Application remnants remain after uninstall.Īfter uninstalling a particular MSI some remnants remain of the application files in the ProgramFiles folder.
0 kommentar(er)
