Description:
ICE75 verifies that all Custom Action Type 17 (DLL), Custom Action Type 18 (EXE), Custom Action type 21 (JScript), and Custom Action Type 22 (VBScript) custom actions are sequenced after the CostFinalize action. These types of custom action use an installed file as their source. ICE75 checks the InstallUISequence Table, InstallExecuteSequence Table, AdminUISequence Table, and AdminExecuteSequence Table. Note that the CostFinalize action is required in these sequence tables.

This ICE75 custom action is only available for Windows Installer version 2.0 or later.

Concerns:
ICE75 posts an error if it finds a custom action using an installed file as a source file that is not sequenced after the CostFinalize action.

Additional information:
These Custom action types are all “Run from installed files”. This means simply that the files must be installed first before actions can call them. This is only done after CostFinalize.

Alternatively you can use "run from installation" versions (or Type 1, 2, 5 and 6), then the file/script will be stored in the Binary Table, and the restriction does not apply. However, for most operations the installation should have already taken place!

Examples of possible errors:
CustomAction Table:

AdminUISequence Table:

AdminExecuteSequence Table:

1. CostFinalize is missing from 'AdminUISequence'. CustomAction1RunFile is a custom action whose source is an installed file. It must be sequenced after the CostFinalize action.

2. CustomAction2DLLCall is a custom action whose source is an installed file. It must be sequenced after the CostFinalize action in the AdminExecuteSequence table.

This error must be solved:
Place the Custom Actions after the CostFinalize action.