Failed to bind to CLR error when executing custom actions

[cubt85iz]

Triage

Issues are triaged at online meetings, generally held alternate Tuesdays at 9:30 a.m. Pacific time (UTC-7/UTC-8). Meeting requests are posted in Discussions.

Discussions and support

Note that discussions are best held in Discussions. Please do not open issues requesting support or debugging help; first start a thread in Discussions and open an issue if the discussion suggests a bug in the WiX Toolset or that a feature request is appropriate.

Instructions

Read the sections above. Delete the Triage, Discussions and support, and Instructions sections and fill out the rest.

Bugs

If this issue is a bug:

• Which version of WiX are you building with?

4.0.1

• Which version of Visual Studio are you building with (if any)?

VS 2022 Enterprise 17.6.3

• Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?

Heatwave for VS2022 1.0.1

• Which version of .NET are you building with?

Target Framework is 4.7.2

• If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?

Sandbox is using 19041.3324

• Describe the problem and the steps to reproduce it.

Unable to execute custom actions when KB5011048 is installed. Installation logs report failed to bind to CLR. A sample project that reproduces the issue is available here: https://github.com/cubt85iz/SampleInstallation

• Describe the behavior you expected and how it differed from the actual behavior.

Installations should execute custom actions when directed.

[cubt85iz]

https://github.com/orgs/wixtoolset/discussions/7613