asyncwait | Wait, Don't sleep | Continuous Deployment library

You can't use session["BUFFER.SIZE"] in a deferred custom action.

To pass a property from the MSI into a deferred custom action you need to use another action to set the value and then read that value in your custom action using a slightly different mechanism.

On the wixtoolset page for custom action you'll see it has a special mention in the Property description pointing to this microsoft article which talks about how getting context in a deferred custom action works.

An important thing to note about the second action is that its property value must be an exact match to the deferred custom action's Id value.

I Fix It After Change

UPDATE: I didn't like what I suggest below (custom action use), and Bob Arnson (WiX coder) reminded me that heat.exe (WiX's general purpose "harvester" / XML markup generator tool) might do the job:

Have you tried changing your Return to "ignore" or "check" on these last two custom actions? My guess is that the netsh command finds some mapping between your cert name and the install folder (??) and holds the directory open so the installer can't delete it because it's open somewhere. The asyncWait is keeping some process going until the end of the install and then checks the return code at the end. If you use "ignore" or "check" it will run synchronously and when you get to the point of removing the install folder, nothing is holding the path open so it can be removed.

Just moving comment to answer. Not entirely sure of the actual mechanism being used here but it seems through some method netsh ends up opening a handle on the directory so it could not be deleted during the uninstall.

I have no direct answer, but one that should help you to figure it out by yourself:

1. Open the MSI package using a tool like Orca (included in Win SDK) or InstEd (my personal preference).
2. Navigate to the InstallExecuteSequence table.
3. Lookup the record of the WiX custom action that creates the user and copy the Action identifier of that record.
4. Use that identifier for the After attribute of the element .

As requested here is the answer. The element you are trying to click has an Event that is called by what appears to be JavaScript.

The page code:

onclick="$get('ctl31_ctl04_ctl11').control.OnValidValueClick(this, 'ctl31_ctl04_ctl11_divDropDown_ctl00');

You need to call that event in order to execute the code on the page that powers that button.

The simplified code is: