Tech News

Windows 11 Hotpatch KB5132043 Breaks Office Apps: Microsoft’s Registry Fix

Published By Shivam Sharma6 min read
Windows 11 update screen with a registry editor window, illustrating Microsoft's HotPatchTableSize workaround for the faulty November hotpatch

What the November hotpatch broke

Microsoft has told IT administrators that its November 2026 Windows 11 hotpatch can stop applications from installing, launching, or running normally, in a service alert reported by BleepingComputer, and it has shared a registry workaround until a permanent fix is ready. The affected apps include Office and third-party applications, according to BleepingComputer, which first reported the confirmation on 19 November. The Register, which covered it on 20 November, specifically names Outlook among the affected apps. The offending update is KB5132043, released on 10 November 2026.

Affected devices may show errors such as “ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099)” when installing, launching, or running some applications, according to Microsoft’s service alert, quoted by BleepingComputer. Microsoft’s investigation points to applications that load the 32-bit Windows Installer DLL, msi.dll. The problem is more common with 32-bit software, but it can also affect 64-bit applications “under certain circumstances”, according to Microsoft, quoted by both outlets. That is the whole defect in one sentence: apps that load the 32-bit Windows Installer DLL fail after the hotpatch, and Microsoft has not said why beyond that link.

The update in question is a hotpatch, which is a security update that does not require a device restart. Hotpatch update packages are significantly smaller than standard cumulative updates, and Microsoft’s goal is to streamline installation and improve compliance, according to Microsoft, quoted by The Register. This hotpatch covers Windows 11 versions 24H2, 25H2 and 26H2, and hotpatching requires an eligible subscription and the necessary management and security configuration. The irony of this particular defect is hard to miss: a no-restart update that ends up requiring a registry edit and a restart anyway.

How do I fix the Windows 11 hotpatch app error?

Set the HotPatchTableSize registry value to 2000 and restart the device. That is the workaround Microsoft shared in a service alert to IT administrators, to use until a permanent update ships. Back up the registry first before you change it.

  1. Open the Start menu, type regedit, and select Registry Editor from the search results to begin.
  2. Use the folders in the left pane to navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management, the folder Microsoft names.
  3. Find the HotPatchTableSize key in the right-hand panel, open it, set the value to 2000, and click OK.
  4. Close the Registry Editor, then restart the device so the new HotPatchTableSize value takes effect.
  5. Check that the affected apps install and launch normally after the restart, and repeat the steps if errors persist.

Microsoft’s own warning, quoted by BleepingComputer, is worth following exactly: “Before you modify the registry, back it up and make sure that you know how to restore it if a problem occurs.” The Register puts it more bluntly, calling the workaround “not for the faint of heart” and saying a backup is a good idea before diving in. Editing the registry is the kind of step that should be done by an IT administrator on a managed device, not by guessing. If the device is managed by your organisation, ask your IT team to apply the workaround rather than editing the registry yourself.

Who is affected, and who is not

The scope is narrow, and that narrowness is good news for most Windows users. Only devices that installed the November 2026 hotpatch through Windows Autopatch, on Windows 11 version 24H2 and later, are affected. Devices that installed the standard November 2026 monthly security update, the regular Patch Tuesday cumulative update, are not expected to be affected, according to Microsoft. The table below is built from Microsoft’s own statements.

How the update arrived Affected?
November 2026 hotpatch (KB5132043) via Windows Autopatch Yes, on Windows 11 versions 24H2, 25H2 and 26H2
Standard November 2026 monthly security update (Patch Tuesday) No, not expected to be affected
Windows 11 versions earlier than 24H2 No, this hotpatch covers versions 24H2, 25H2 and 26H2 only

Windows Autopatch is Microsoft’s cloud service that automates Windows and Microsoft 365 updates for businesses. Microsoft first announced it in April 2022, and it has been generally available since July 2022, free for customers with a Windows 10 or 11 Enterprise E3 licence or greater, according to BleepingComputer. That means the affected population is devices managed through Autopatch, not home users on the standard update path. If your device gets its updates through your organisation’s Autopatch setup and you are on Windows 11 version 24H2, 25H2 or 26H2, you are in the affected group. If your device installed the standard November 2026 monthly security update instead of the hotpatch, you are not.

Nine days from release to confirmation

The timeline below is our own reconstruction from the sourced dates. It is the original data point in this story, and it shows how long the defect ran before Microsoft confirmed it.

Date What happened
13 October 2026 Baseline update released, a prerequisite for the November hotpatch
10 November 2026 KB5132043 hotpatch released
19 November 2026 Microsoft confirms the defect via a service alert to IT admins (BleepingComputer, 05:35 ET)
20 November 2026 The Register covers the confirmation and the registry workaround (13:39 UTC)

Nine days passed between the hotpatch release on 10 November and Microsoft’s confirmation on 19 November. During that window, no workaround had been published. That is a long time for a defect that breaks Office and Outlook, and it is the gap that makes this story more than a routine patch note. The confirmation came through a service alert to IT administrators, not a public blog post, which is why the first tier-1 report arrived from BleepingComputer on the morning of 19 November rather than from Microsoft’s own channels.

Why this one stung

Hotpatching became the default in Windows Autopatch earlier in 2026, not an opt-in. Microsoft said in March 2026 that it would turn on hotpatch security updates by default for eligible Windows devices managed through Windows Autopatch, via the Microsoft Graph API and Microsoft Intune, after the May 2026 Windows security updates were installed, according to BleepingComputer. The Register notes the same change and adds its own dry comment: at the time, it asked “What could possibly go wrong?” and, thanks to November’s hotpatch, it now has its answer.

The default matters because it defines the blast radius. The affected population is not a small experimental group that chose to try rebootless updates. It is the default update path for eligible Autopatch-managed Windows 11 24H2, 25H2 and 26H2 devices that kept hotpatch enabled and took the November hotpatch. A defect in a default update reaches further than a defect in an opt-in one, and the workaround, a registry edit plus a restart, is exactly the kind of manual step that hotpatching was supposed to eliminate. That is why this story is not just about one bad update. It is about a default that turned a routine security patch into a week of broken apps for the administrators who trusted it.

What to watch next

Whether Microsoft ships a permanent fix, and in which update it arrives, since the registry workaround is explicitly temporary until a fix is available. Whether the December hotpatch carries the fix or the defect, since the same Autopatch default will push it to the same devices. Whether Microsoft changes how it validates hotpatches before they go out, since a defect that breaks Office took nine days to confirm. And whether the standard Patch Tuesday path stays clean, since Microsoft has said devices on the regular monthly update are not expected to be affected, and that line is the one that separates a contained enterprise problem from a much larger one.