Hi, We're having a very frustrating problem with a custom action that is used to optionally clean up configuration files when uninstalling, if the user checks a specific checkbox. It should be noted that this action runs on UNinstall only.
The custom action works fine on XP, and fine on Vista if either UAC is turned off, or if the MSI is started from a command window with elevated admin rights. Despite setting Impersonate="no" and Execute="deferred", when UAC is enabled and the MSI package is run under an administrator account (but with the normal UAC token), the custom action is just completely ignored. It silently fails - no error messages at all. It seems that the VBScript doesn't even get called, because we dumped some message boxes inside the code, and they never appeared (but they work fine of course under the other scenarios described above). Here's the code for the custom action: <CustomAction Id="RemoveConfigFiles" BinaryKey="RemoveConfigFiles" VBScriptCall="RemoveConfigFiles" Impersonate="no" Execute="deferred" Return="ignore" /> Is this a bug with WiX? I'm using build 3.0.4805.0, but I also tried it against an earlier 3.0 build. The package is being compiled for Windows Installer 4.0 (tried it with 3.0 initially) - but this made no difference. Regards, Edward Forgacs ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
