Patch Optimization

Windows Installer can optimize patching to reduce the time that is required to apply patches to installed applications.

Windows Installer 2.0: Not supported. For versions of Windows Installer released before Windows Installer 3.0, patching runs a complete repair installation of the application, which can take significantly more time.

Windows Installer 3.0 and later: The patching process only changes the parts of an application that are modified by a patch.

Windows Installer 3.1 and later: Beginning with Windows Installer 3.1, patch optimization requires that all patches in the transaction have the OptimizedInstallMode property set to 1 (one) in the MsiPatchMetadata Table.

If a patch only modifies the following tables, Windows Installer 3.0 or later skips the actions that are associated with all the other tables, even if those actions are listed in the sequence tables of the original application installation package (.msi file).

• AdminExecuteSequence
• AdminUISequence
• Condition
• CustomAction
• File
• FileSFPCatalog
• InstallExecuteSequence
• InstallUISequence
• Media
• MoveFile
• MsiAssembly
• MsiDigitalCertificate
• MsiDigitalSignature
• MsiFileHash
• MsiPatchHeaders
• Patch
• PatchPackage
• Property
• Registry
• SFPCatalog
• TypeLib
• _Columns
• _Storages
• _Streams
• _Tables
• _TransformView Table
• _Validation

To turn off the patch optimization option, use the DisableFlyWeightPatching policy.