Merge module validation in Orca fails on well-formed merge module

[barnson]

Windows Build Number

Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0

Processor Architecture

AMD64

Memory

64GB

Storage Type, free / capacity

C: NVMe 35GB/127GB; X: NVMe 282GB/284GB; Z: 377GB/599GB

Relevant apps installed

WiX v3.14.5721.0

Traces collected via Feedback Hub

n/a

Isssue description

The merge-module validation module mergemod.cub in Orca v5.0.22000.194 from the Windows 11 SDK v10.0.22000 fails. When running validation in inner loop, the build fails and validation must be disabled to continue work.

The failure occurs in a well-formed merge module fails when executing ICE103:

Action 18:39:33: ICE103. 
Action start 18:39:33: ICE103.
MSI (c) (34:E8) [18:39:33:886]: Invoking remote custom action. DLL: X:\Tmp\MSI3AEA.tmp, Entrypoint: ICE103
CustomAction ICE103 returned actual error code 1154 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (34:98) [18:39:33:890]: Note: 1: 1723 2: ICE103 3: ICE103 4: X:\Tmp\MSI3AEA.tmp 
MSI (c) (34:98) [18:39:33:890]: Note: 1: 2205 2: X:\Tmp\ICE30AE.tmp 3: Error 
MSI (c) (34:98) [18:39:33:890]: Note: 1: 2228 2: X:\Tmp\ICE30AE.tmp 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1723 
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.  Action ICE103, entry: ICE103, library: X:\Tmp\MSI3AEA.tmp 

The attached .zip file contains WiX authoring for the merge module, the merge module itself, and the verbose MSI log generated during validation.

Repro6567.zip

See also wixtoolset/issues#6567.

Steps to reproduce

• Open MergeModule2.msm in Orca.
• Choose Tools|Validate.
• For Evaluation file, select Merge Module Validation Suite.
• Uncheck Show "INFO" messages.
• Choose Go.
• After completion, choose Copy Results, yielding these results.

Execution	ERROR	There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.  

Expected Behavior

Validation should succeed without failure or error.

Actual Behavior

Validation fails, essentially crashing in the MSI custom action.