8.0
This issue typically occurs when a vendor modifies details of an existing VIB (for example, VIB name, vendor name, or version).
During the upgrade, the existing VIB on the ESXi host and the new VIB being introduced both attempt to claim the same file path.
Since two VIBs cannot claim the same file (unless they are identical), the upgrade fails with an integrity.fault.HostUpgradeRunScriptFailure error.
Engage with Hardware Vendor to get advise about which VIBs should or not be present in the image and which should be removed from the ESXi to prevent this behavior