What Microsoft confirmed
BleepingComputer reported Microsoft's warning, which was issued as a service alert to administrators. Microsoft said that devices that installed the November 2026 hotpatch update "might experience an error when installing, launching, or running some applications." The visible symptom is errors similar to "ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099)".
Microsoft has also given an early explanation. "Current investigation suggests this issue occurs for applications which load the 32-bit Windows Installer DLL, found as msi.dll." The company added that it "can happen more frequently with 32-bit applications, but can also occur for 64-bit applications under certain conditions."
According to the report, the alert covers systems running Windows 11 24H2 and later, and both Office and third-party applications can be affected. Microsoft's own wording only says "some applications." That doesn't mean every Office install, every MSI-based setup or every hotpatched PC will break.
The update involved
Microsoft's support documentation names the November hotpatch as KB5132043. The page is titled for the November 10, 2026—Hotpatch KB5132043 (OS Builds 26300.9911, 26200.9911, and 26100.9911) release, and Microsoft says the Hotpatch update for Windows 11, version 26H2, 25H2 and 24H2 (KB5132043) includes security improvements.
| Windows 11 version | Hotpatch build (KB5132043) |
|---|---|
| 26H2 | 26300.9911 |
| 25H2 | 26200.9911 |
| 24H2 | 26100.9911 |
The public KB page is behind the service alert. It still says Microsoft is not currently aware of any issues with this update. If you rely on the KB page's known-issues section, you won't see this problem there yet. Check your admin service alerts.
Section summary: KB5132043, the November 10 hotpatch for Windows 11 24H2, 25H2 and 26H2, can cause 0xC0000099 errors in some apps that load the 32-bit msi.dll. Microsoft has acknowledged the issue in a service alert, but the public KB page doesn't list it yet.
Who is affected and who isn't
This is a problem for managed enterprise fleets, not home PCs. Microsoft said the known issue should not impact systems that have installed the standard November 2026 Patch Tuesday security updates, but only those that have installed the hotpatch updates pushed through the Windows Autopatch service.
Only certain devices get hotpatches. Microsoft's Autopatch FAQ lists the requirements:
- an eligible license, such as Windows 11 Enterprise E3/E5, Education A3/A5, Microsoft 365 Business Premium or Windows 365 Enterprise
- Windows 11 24H2 or later on the current baseline
- an x64 AMD/Intel CPU (Arm64 hotpatching is now generally available, with extra steps)
- Intune management with a hotpatch-enabled Windows quality update policy
- Virtualization-based Security enabled
Microsoft's November KB lists the October baseline, KB5127648, as a prerequisite for this hotpatch.
How can you tell which track a device is on? According to Microsoft's FAQ, hotpatched devices report a different KB number and OS version than devices that got the standard restart-required update. Microsoft's release information lists the standard November update for these versions as KB5132061. A device on build 26100.9911, 26200.9911 or 26300.9911 with KB5132043 installed is in the affected group.
Section summary: Only hotpatch-enrolled devices on KB5132043 are in scope. Devices on the regular November cumulative update (KB5132061) are not affected by this particular issue, according to Microsoft.
The workaround: increase HotPatchTableSize
Microsoft's temporary fix is a registry change. As reported, administrators have to edit the Windows Registry to increase the HotPatchTableSize. The steps:
- Open Start, type
regedit, and select Registry Editor. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. - In the right-hand panel, locate the "HotPatchTableSize" registry key, open it, and set the Value to "2000".
- Click OK. Then close the registry editor and restart the device.
Microsoft also warns that before you change the registry, you should back it up and make sure you know how to restore it.
Things to keep in mind before you push this across a fleet:
- The fix needs a restart. You chose hotpatching to avoid reboots, but this workaround requires one. Schedule the restarts.
- The value's format isn't specified. The reported steps say "2000" but don't say whether that's hexadecimal or decimal, and they don't say what to do if
HotPatchTableSizedoesn't exist. Follow Microsoft's service alert for those details rather than guessing. - This is a stopgap. Microsoft has offered it only until a fix is available. Keep track of which devices you changed so you can reverse the setting once the permanent fix ships, if Microsoft recommends that.
The error name is a useful clue. An "allotted space exceeded" error alongside a registry setting with "TableSize" in its name suggests the hotpatch infrastructure is running out of room in a fixed-size table, and raising the limit gives it more. That reading is our own, based on the names. Microsoft hasn't published a root-cause analysis.
Section summary: On affected devices, set HotPatchTableSize to 2000, back up the registry first and restart. Treat it as temporary and keep a list of the changed machines.
Admins had already traced it to the MSI hotpatch
Administrators were reporting problems before Microsoft's alert. Neowin covered reports of broken printing, Citrix and Sage after the November updates. In one case, an administrator found that the 32-bit Windows Installer executable, msiexec.exe, located in the C:\Windows\SysWOW64 folder, was also failing to start. Using Process Monitor, they traced the problem to msi_hotpatch.dll, which had been updated as part of November's hotpatch KB5132043.
That fits Microsoft's statement that 32-bit msi.dll consumers are the ones failing. Neowin also reported that uninstalling the update and restarting Windows apparently brought everything back to normal. On Microsoft's Q&A forum, one administrator dealing with print spooler failures wrote that "We've had luck installing the non hotpatch version: KB5132061, which resolved the issue."
There's one complication. Neowin also cited reports from 25H2 users that identified KB5132061 as the culprit, and removing that update brought the affected Sage modules back. Microsoft says the standard update shouldn't trigger the msi.dll problem. Those Sage reports are either a separate issue or something not yet understood, so don't assume KB5132061 fixes every November problem.
Microsoft's Autopatch FAQ confirms that switching tracks is supported. Admins can manually install the standard monthly update from the Microsoft Update Catalog. The device then gets standard updates until the next baseline month and rejoins the hotpatch schedule afterwards. Uninstalling the hotpatch and switching to the standard update are community workarounds, not Microsoft's official guidance for this issue. The registry change is the official one.
Triage checklist for admins
- Find affected devices. Look for KB5132043 and builds ending in
.9911in Intune or your inventory tool. - Match the symptoms. Look for 0xC0000099 or ERROR_ALLOTTED_SPACE_EXCEEDED errors during install, launch or runtime, especially in 32-bit apps and anything that calls Windows Installer.
- Check the logs. Microsoft's FAQ says hotpatch errors are recorded in the event logs and suggests searching the System log for "hotpatch."
- Pause the rollout. Autopatch lets you pause or roll back quality updates through update rings if KB5132043 hasn't reached all your rings yet.
- Test the workaround on one device first, then roll it out with a scheduled restart.
What this means for hotpatching
Hotpatching patches Windows binaries in memory, and Microsoft's FAQ says that includes binaries loaded by third-party processes. That's why it can install without a reboot. It's also why a fault in one hotpatched component like the Windows Installer DLL can affect Office, printing tools, Citrix and line-of-business software at the same time.
The timing is awkward. In March, Microsoft said it would turn on hotpatching by default for eligible devices managed through Intune and the Microsoft Graph API once the May 2026 security updates were installed. More organizations are now on the hotpatch track, some without opting in, so a regression like this one reaches more machines.
None of this means you should drop hotpatching. Applying security fixes without restarts is still useful. It does mean hotpatches should go through the same pilot rings as regular updates. Microsoft's FAQ already recommends testing hotpatch releases, and November shows why.
The bottom line
- Affected: Windows 11 24H2, 25H2 and 26H2 devices that installed hotpatch KB5132043 through Windows Autopatch.
- Symptom: ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099) errors when installing, launching or running some apps, most often 32-bit apps that load
msi.dll. - Not affected, per Microsoft: devices on the standard November Patch Tuesday update.
- Official workaround: set
HotPatchTableSizeunderHKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Managementto 2000, after backing up the registry, then restart. - Permanent fix: not released yet.
If you've applied the workaround or switched to the standard track, let other admins know in the WindowsForum Windows Update and enterprise deployment threads whether it worked.
References
- Microsoft confirms app installation, launch issues after hotpatch - BleepingComputer BleepingComputer · 2026-11-19T10:35:05+00:00
- Windows 11 KB5132043 KB5132061 break printing, Citrix, and Sage - Neowin neowin.net
- November 10, 2026—Hotpatch KB5132043 (OS Builds 26300.9911. 26200.9911, and 26100.9911) | Microsoft Support support.microsoft.com