Your custom action is currently only scheduled to run in the InstallExecuteSequence
. If your install runs through the InstallUISequence
then the Feature
will still get enabled. The InstallUISequence
is unless you explicitly specify to run the install 'quietly'.
Fortunately, the fix is easy. Add the following as a peer of the InstallExecuteSequence
:
<InstallUISequence>
<Custom Action="find" Before="CostInitialize">Not Installed</Custom>
</InstallUISequence>