Could KB5132043 be stopping Citrix Workspace and 32-bit msiexec from running?

November 19, 2026 5 answers
Asked by Tavquni-8j

Citrix Workspace is failing to launch, install, or uninstall, and the 32-bit msiexec.exe under C:\Windows\SysWOW64 does not seem to start. Could the November hotpatch KB5132043 be involved, and how can I check?

Answers

9e~brindlecompass_576

It's a plausible lead. Try running C:\Windows\SysWOW64\msiexec.exe /? directly on an affected machine. If nothing appears, check Event Viewer for Hotpatch-Loader errors followed by an application error. Process Monitor may also show msi_hotpatch.dll loading during the failed launch.

Those signs can help narrow it down, but they don't prove the update is the cause by themselves. Compare the results with a similar unaffected device and check whether KB5132043 is installed on each.

Reply to this answer
Nexdori.3w

Removing KB5132043 and rebooting has been reported to restore msiexec and Citrix installation or removal. I'd test that on one affected device first, subject to your organization's update policy, rather than removing a security update across the fleet immediately.

Zavqueli+8d:

Also check what will reinstall it. If automatic updates remain enabled, removing it once may not keep the device clear of the hotpatch.

Reply to this answer
6j!parcelgauge_413

Don't assume every machine with that KB is broken. Workspace versions 26.3.20.31 and 25.7.1.9 have also been reported working on Windows 11 25H2 with the update installed. The exact trigger isn't clear, so record the Windows version, device architecture, Workspace version and installer behavior when comparing machines.

Reply to this answer
n.846!drivmelo

The symptoms may reach beyond Citrix. Other reports mention installers disappearing immediately, .NET updates failing with 0x80070643, printer problems and apps failing to start. Those are useful clues to investigate, not proof that the hotpatch caused every one of them.

Reply to this answer
8c+ferrulekite_264

For managed devices, check how your update policies handle hotpatches before planning a rollout change. One reported workaround was a remediation script to remove the KB while updates were paused, but the available policy controls and security consequences need checking in your environment.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions