We had (and still have) issues with 3.6 & Trend Officescan. It objects to the way that the burn setup.exe is extracted into temp & then writes to the RunOnce registry key. OfficeScan sees this as malware behaviour & blocks it. Even though everything is signed.
If you havent signed everything then you might try that. Havent found a way around this & was hoping that maybe 3.7 would do something slightly different. Haven't tried it yet, but given your post I'm not optimistic. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Bootstrapper-application-installation-tp7583949p7583951.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
