[wix-users] fw:FirewallException and msiexec/qn causes a hang

Rob Mensching rob at firegiant.com
Mon Oct 3 09:12:16 PDT 2016

Do you have any VBScript custom actions? If not, I'd look at what is running VBScript as part of install. Script during install not a great combination.

 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Rod Widdowson
Sent: Monday, October 3, 2016 7:24 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] fw:FirewallException and msiexec/qn causes a hang

A user saw this some time ago.   I have reproduced it but I haven't yet started down the track of finding a small reproducer.  I'm
asking here before I do so in case someone can say tell me what's wrong.

The customer reported symptom is "the installer hangs".

I have reduced it to this component:

       <Component Id="procrun_32_Firewall" Directory="PROCRUNROOT" Guid="{F93B8D9F-7BBA-4D79-995D-4AC20FF158E4}" KeyPath="yes">
             <Condition>Not NO_FIREWALL</Condition>
             <fw:FirewallException Id="Win32Shibd_idp" Program="[#file_procrun_32_service]" Name="Win32Shibd_idp" Description="The Shibboleth IdP" Protocol="tcp" Scope="any" />

Which is actually bundled up into a merge module which is then sucked into my installer.   

If I run the installer /qb it installs just fine.  
If I run /qn NO_FIREWALL=true (skipping the component[*])it installs just fine.

But if I try to run /qn I get the "hang" : which in fact is a hard loop.  Poking at this with widbg I found an interesting stack:


Any suggestions?


[*] Yes I know, it's a different property, I do the required massage in the installer to convert it to the merge module property.

More information about the wix-users mailing list