Office won’t open, an installer quits halfway, or an app that worked yesterday now throws ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099). You probably checked your free disk space first. That isn’t the problem. The Windows 11 hotpatch error 0xC0000099 comes from Microsoft’s November 2026 hotpatch, KB5132043, and it only hits PCs that receive hotpatches through Windows Autopatch.
Below is how to tell in 30 seconds whether your PC is one of them, the temporary registry workaround Microsoft gave IT admins, and what to do if you are not the admin.
Error 0xC0000099 appears on Windows 11 24H2, 25H2 and 26H2 PCs that installed hotpatch KB5132043 (10 November 2026) through Windows Autopatch. Apps that load the 32-bit Windows Installer file msi.dll fail to install, open or run. Microsoft’s temporary workaround is to set the registry value HotPatchTableSize under Memory Management to 2000 and restart. Home PCs on the normal November update (KB5132061) are not affected. No permanent fix was out as of 22 November 2026.
- vCause: the November hotpatch KB5132043 breaks apps that load msi.dll, mostly 32-bit apps such as Office.
- vTop fix: back up the registry, set HotPatchTableSize to 2000, then restart.
- vEscalation: on a work PC, send your build number to IT instead of editing the registry yourself.
Why the hotpatch error 0xC0000099 happens
Hotpatches are security updates that install without a restart. Microsoft plans eight hotpatch months and four restart-required baseline months each year. They are only offered to managed business PCs: Windows 11 Enterprise E3 or E5, Education A3 or A5, Microsoft 365 Business Premium or F3, and Windows 365 Enterprise, with virtualization-based security turned on.
The November 2026 hotpatch, KB5132043, shipped on 10 November for builds 26100.9911 (24H2), 26200.9911 (25H2) and 26300.9911 (26H2). After it installed, Microsoft confirmed in its admin center alert WI1559710 that some apps fail with ERROR_ALLOTTED_SPACE_EXCEEDED. The failure happens in apps that load the 32-bit Windows Installer library, msi.dll. It shows up more often with 32-bit apps, but 64-bit apps can hit it too.
Two things the error is not. It is not a full disk, so deleting files won’t help. Nor is it boot error 0xc0000098, a corrupted boot configuration error that fills search results because the number looks almost the same. If your PC starts and only some apps fail, you are dealing with 0xC0000099.

How to fix Windows 11 hotpatch error 0xC0000099
Fix 1: Check if KB5132043 is installed (30 seconds)
Confirm the hotpatch is actually on the PC before you change anything.
- Open Settings > Windows Update > Update history.
- Look under Quality Updates for KB5132043.
- Press Win + R, type
winverand press Enter. A build ending in .9911 means the hotpatch is in place.
If you see KB5132061 instead (builds ending in .9974), you got the standard Patch Tuesday update. Those PCs are not affected by this bug, so the cause is something else. Skip to the “Still not working?” section.
Fix 2: Restart once before anything else
Restart the PC and try the app again. A restart will not remove the hotpatch, but it rules out a stuck installer or a half-finished update. If the error comes back after a clean restart, move on to the registry workaround.
Fix 3: Back up the registry key
Export the key you are about to change. This gives you a one-click way back.
- Press Win + R, type
regedit, press Enter and approve the prompt. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. - With Memory Management selected, choose File > Export and save the .reg file somewhere safe.
- Double-click HotPatchTableSize and write down its current value and whether Base is set to Hexadecimal or Decimal.
Microsoft’s own steps to back up the Windows Registry cover the full export and import process.
Fix 4: Set HotPatchTableSize to 2000 and restart
Apply Microsoft’s temporary workaround.
- In the same Memory Management key, double-click HotPatchTableSize.
- Change Value data to 2000 and click OK.
- Close Registry Editor and restart the PC.
- Open the app that failed. It should install or launch normally.
Why this works: Microsoft has not published a detailed explanation. The value name points to a table Windows sizes for hotpatch data, which fits an error about allotted space rather than disk space. Raising it is the change Microsoft tested.

Fix 5: Uninstall the hotpatch and install the standard update
Roll back if the workaround is not an option. The Windows Autopatch hotpatch documentation says hotpatches do not roll back automatically. An admin can uninstall KB5132043 and install the standard cumulative update instead. That path needs a restart, which is the very thing hotpatching avoids, so most teams will use it only on PCs where the registry edit is blocked.
On a work PC? Send this to IT instead
Most hotpatch PCs are company laptops, and you may not have admin rights. Don’t fight the registry. Send your helpdesk three things: the exact error text, your build number from winver, and the name of the app that failed. Mention alert WI1559710 (26H2), WI1559711 (25H2) or WI1559712 (24H2) so they can find it fast.
Still not working? Try this
If KB5132043 is not installed, this bug is not your problem. Repair the app instead: open Settings > Apps > Installed apps, click the three dots next to it, and choose Modify (Office offers Quick Repair there) or Advanced options > Repair, depending on the app.
November was rough for Windows updates in general. Activation scripts failed with error 0x80041008 until Microsoft’s 13 November update KB5136483 fixed it on 23H2. Printing complex Word documents with hidden zero-size images also broke and was still open as of 22 November. If your symptom matches one of those, it is a different bug with a different fix.
Still stuck on a hotpatch PC after the registry change? Check the hotpatch was really the trigger by comparing with a colleague’s PC on the same build, then open a ticket with Microsoft support through your admin center.
Frequently asked questions
What is the Windows 11 November 2026 hotpatch bug?
It is a known issue in hotpatch KB5132043, released 10 November 2026. Some apps that load msi.dll, including Microsoft Office, fail to install, launch or run with ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099). Microsoft confirmed it in admin center alert WI1559710 and related alerts.
Am I affected if I updated Windows normally?
No. Home and small business PCs that got the regular November update, KB5132061, are not affected. The bug only hits managed PCs that receive hotpatches through Windows Autopatch on Windows 11 24H2, 25H2 or 26H2.
Does error 0xC0000099 mean my disk is full?
No. The name sounds like a storage problem, but the error comes from the hotpatch, not from your drive. Freeing disk space will not fix it. The registry workaround or a rollback to the standard update will.
Is there a permanent fix yet?
Not as of 22 November 2026. Microsoft has not announced a date. The public KB5132043 page still lists no known issues, so admins should watch the Microsoft 365 admin center and the Windows 11 release health dashboard for the fix.
Should I undo the registry change later?
Once Microsoft ships a permanent fix, restore the value you wrote down or import the .reg file you exported. Keep that backup until then.
The Bottom Line
Check your build first. If it ends in .9911 and KB5132043 is listed, back up the Memory Management key, set HotPatchTableSize to 2000 and restart. Not the admin? Send IT your build and the error text. On KB5132061, this bug isn’t yours, so look at the app itself. For other Windows checks, see how to find out what motherboard you have, and if Office macros are next on your list, here is how to enable macros in Excel.



