Wix安装程序无法升级InstallShield产品，部分文件未安装求助

Hey Refael, let's break down why your WiX MajorUpgrade isn't updating all files when targeting that InstallShield-derived product.msi. Here are the most common culprits and actionable steps to fix them:

1. Windows Installer File Versioning Rules #

Windows Installer only replaces a file if:

• The new file has a higher version number than the installed one, OR
• The file has no version info and you've configured REINSTALLMODE to force overwrites.

If you see lines like this in your log:

File: C:\Path\To\File.dll; Won't Overwrite; Existing file is of equal or greater version

That means your updated file's version isn't higher than the already installed one. Fix this by bumping the file's version number, or adjust the REINSTALLMODE property to force overwrites (more on that below).

2. MajorUpgrade Element Configuration #

Double-check your WiX MajorUpgrade setup to ensure it's properly triggering the upgrade:

• Confirm the UpgradeCode in your WiX project exactly matches the one in product.msi (case-sensitive—use Orca to verify the MSI's Property table).
• Ensure your MajorUpgrade element has settings that allow the upgrade:

  <MajorUpgrade
      AllowDowngrades="no"
      AllowSameVersionUpgrades="yes"
      MigrateFeatures="yes"
      Schedule="afterInstallInitialize" />
  

  The Schedule="afterInstallInitialize" is critical—it ensures the upgrade logic runs at the right time to replace files and settings.

3. REINSTALLMODE Property #

The default REINSTALLMODE value (omus) might not force overwrites for all scenarios. To ensure all files are replaced, add this property to your WiX project:

<Property Id="REINSTALLMODE" Value="amus" />

Here's what each letter means:

• a: Force reinstallation of all files
• m: Rewrite registry entries
• u: Update system files
• s: Replace shortcuts

4. Component KeyPath & Conditions #

• KeyPath Issues: If a component's KeyPath is a registry entry (not the file itself), Windows Installer might skip updating the file even if it's outdated. Ensure components with critical files have KeyPath="yes" set on the file (WiX auto-sets this if the component only contains one file, but verify anyway):

  <Component Id="MyAppComponent" Guid="*" KeyPath="yes">
    <File Id="MyAppExe" Source="bin\MyApp.exe" />
  </Component>
  

• Component Conditions: Check if components for missing files have conditional logic that's preventing them from being installed during the upgrade. For example, a condition like VersionNT >= 6.1 might block installation on older OSes if not intended.

5. InstallShield-Specific Quirks #

Some InstallShield MSIs use custom actions, shared components, or merge modules that can interfere with WiX upgrades:

• Look for custom actions in your log that might be aborting file installation (search for "Skipping action" or "Return value 3").
• Check if any components are marked as "Shared" (in Orca's Component table, the Shared column)—shared components use different upgrade logic and might need explicit handling.

1. Use Orca to confirm your WiX MSI's UpgradeCode matches product.msi exactly.
2. Scan your log for entries related to the missing files—this will give you the exact reason they're not being installed.
3. Test with REINSTALLMODE="amus" to rule out versioning-related skips.
4. Verify component KeyPaths and conditions for the problematic files.

Let me know what you find in the log, and we can narrow it down further!

内容的提问来源于stack exchange，提问作者Refael Sheinker