Microsoft has confirmed that the November 2026 Windows 11 hotpatch, KB5132043, can cause errors when installing, launching or running some applications, including Office and third-party apps, with the error ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099). The workaround Microsoft shared is a registry change, HotPatchTableSize set to 2000 under the Memory Management key, followed by a restart. This guide shows how to tell whether a device is affected, how to apply the workaround on one PC, and how to roll it out to many Intune-managed devices with a rollback plan.
One caution up front. As of 2026-11-20, the public Microsoft pages we opened do not list this issue. The details come from Microsoft's admin-center service alert WI1559710 as quoted by news outlets, so treat the registry value type and number base as something to confirm in your own alert text.
Who this is for and what you will have at the end
This guide is for Windows and Intune administrators who use hotpatch, and for anyone running a Windows 11 Enterprise or Business Premium PC that installed the November hotpatch and now has apps that will not open or install.
At the end you will have:
- A way to decide quickly whether a device is in scope (build number, hotpatch versus standard update).
- The workaround applied and verified on a pilot device.
- A detection and remediation script pair ready for Intune Remediations, with a rollback.
- A short watch list for when Microsoft publishes a permanent fix.
If you manage devices with update rings and hotpatch policies, the companion guide Configure Intune update rings and Windows hotpatch covers the policy side. For the wider month, see November 2026 Patch Tuesday.
What Microsoft has said so far
The sources fall into three layers, and it helps to keep them apart.
| Layer | What it says | Where we saw it |
|---|---|---|
| Public update page | KB5132043 was released 2026-11-10 for builds 26300.9911, 26200.9911 and 26100.9911; known issues: "Microsoft is not currently aware of any issues with this update." | support.microsoft.com/help/5132043 |
| Public release health | The Windows 11 24H2 and 25H2 pages (updated 2026-11-19 18:04 UTC) list SQL Server linked-server connections, USB audio and Remote Desktop issues, but not this one. | learn.microsoft.com release health |
| Service alert WI1559710 | Devices that installed the November 2026 hotpatch "might experience an error when installing, launching, or running some applications." The error is ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099). | Quoted by BleepingComputer, 2026-11-19, which saw it in the admin portal |
Per that reporting, Microsoft's current investigation suggests the issue occurs for applications that load the 32-bit Windows Installer DLL, msi.dll. It is more common with 32-bit applications, but 64-bit applications may be affected in some circumstances. Microsoft says the standard November Patch Tuesday security updates are not affected, only devices that received the hotpatch updates delivered through Windows Autopatch. No fix date has been given; the workaround applies "until a fix is available".
The public KB page and the release health pages can lag a service alert, so the gap is not proof the alert is wrong, but it does mean you should open the alert itself in your Microsoft 365 admin center under Service health before acting at scale.
Step 1: Decide whether a device is affected
A device is only in scope if all of these are true:
- It installed the November 2026 hotpatch, KB5132043, rather than the standard cumulative update KB5132061.
- It runs Windows 11 24H2 or later. KB5132043 covers 24H2, 25H2 and 26H2.
- It shows an error such as 0xC0000099 when an app installs, starts or runs.
Hotpatch only reaches devices that meet Microsoft's prerequisites: an eligible license (Windows 11 Enterprise E3 or E5, Microsoft 365 F3, Windows 11 Education A3 or A5, Microsoft 365 Business Premium or Windows 365 Enterprise), Windows 11 24H2 or later, the latest baseline, virtualization-based security running, and a Windows quality update policy in Intune with hotpatch turned on. Everything else receives the standard update, so Home PCs and ineligible devices are not on the hotpatch path.
Check one device
Open Settings > Windows Update > Update history and look for KB5132043 in the list. Then compare the build number. In PowerShell:
$cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
"{0}.{1}" -f $cv.CurrentBuild, $cv.UBR
Get-HotFix | Where-Object HotFixID -in 'KB5132043','KB5132061' | Select-Object HotFixID, InstalledOnA device on KB5132043 reports a build that ends in .9911 per the build numbers on Microsoft's page, for example 26100.9911. If Get-HotFix returns nothing, trust the build number and Update history.
Confirm hotpatch enrollment
Microsoft's hotpatch documentation gives two on-device checks. In Settings > Windows Update > Advanced options > Configured update policies, look for Enable hotpatching when available. In Event Viewer, filter for AllowRebootlessUpdates; a value of 1 means the device is enrolled in the Windows Autopatch update policy with hotpatch on.
Find devices across the tenant
In the Intune admin center, Microsoft documents a Hotpatch quality update report that shows per-policy device status (see the Windows Autopatch hotpatch pages); you can also filter your device inventory by OS version for builds ending in .9911.
Step 2: Apply the workaround on one PC
Microsoft's workaround, as reported, has four parts: back up the registry, set the value, close the editor and restart.
- Back up the registry. In Registry Editor choose File > Export for the Memory Management key, or create a restore point.
- Open Registry Editor (search for
regeditfrom Start) and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management- Find the value named
HotPatchTableSizeand set it to2000, then select OK. - Close Registry Editor and restart the device.
The open question: type and number base
None of the pages we could open states the value type or whether 2000 is decimal or hexadecimal. This matters because the two readings differ:
| Reading | Value in decimal | Value in hex |
|---|---|---|
| 2000 as a decimal number | 2000 | 0x7D0 |
| 2000 as a hexadecimal number | 8192 | 0x2000 |
The numbers are easy to check: 2 x 16^3 = 8192, and 2000 in decimal is 7 x 256 + 13 x 16 + 0 = 1792 + 208 = 2000, which is 0x7D0. In Registry Editor, the DWORD dialog has a Base choice of Hexadecimal or Decimal; the base you select when typing 2000 decides which number is stored.
Use the exact wording from your own alert. Also inspect the device first: if HotPatchTableSize already exists, note its type and data before you change it, because other reporting suggests it may already be set on some machines, which we could not verify. The same key already holds the documented Arm64 hotpatch setting HotPatchRestrictions as a DWORD, which is a reason to expect a DWORD here, not proof.
Step 3: Verify the fix
After the restart:
- Confirm the value stuck:
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management' -Name HotPatchTableSize- Reopen the app that failed, or rerun the failing installer, and check that the 0xC0000099 error is gone.
- In Event Viewer, filter the Application log for
hotpatch. Microsoft's documentation says the inbox hotpatch monitor logs an event when it detects a problem, and on a critical error the device installs the standard update. - Confirm the device is still on the hotpatch track: Enable hotpatching when available should still appear under Configured update policies.
Step 4: Roll it out with Intune Remediations
A one-off registry edit does not scale and does not survive a reimaged device, so use a detection and remediation pair. Intune Remediations live under Devices > Manage devices > Scripts and remediations, where you choose Create script package.
Check licensing first
Microsoft's Remediations page lists Windows Enterprise E3 or E5 (included in Microsoft 365 F3, E3 or E5), Windows Education A3 or A5, or Windows VDA per user, and requires devices to be Microsoft Entra joined or hybrid joined and MDM enrolled running Windows Enterprise, Professional or Education. Hotpatch eligibility also includes Microsoft 365 Business Premium, which that Remediations licensing list does not name. If you are a Business Premium shop, confirm Remediations licensing before you plan around it; otherwise deploy the same script as a standard PowerShell script from Intune.
Detection script
The detection script must exit with code 1 when the issue is detected; any other exit code, including empty output, means the remediation script will not run.
# Detect_HotPatchTableSize.ps1
# Replace $Expected with the exact value from your service alert.
$Expected = 2000 # decimal 2000 = 0x7D0. If your alert says hexadecimal 2000, use 8192.
$Key = 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management'
$Name = 'HotPatchTableSize'
$ubr = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').UBR
if ($ubr -ne 9911) { Write-Output "UBR $ubr, not in scope"; exit 0 }
$current = (Get-ItemProperty -Path $Key -Name $Name -ErrorAction SilentlyContinue).$Name
if ($current -eq $Expected) { Write-Output "Already set to $current"; exit 0 }
Write-Output "In scope, HotPatchTableSize is '$current'"
exit 1The UBR check assumes devices on KB5132043 report .9911, from the build numbers on Microsoft's update page. Adjust it if you later find a different UBR on affected devices.
Remediation script
# Remediate_HotPatchTableSize.ps1
$Expected = 2000 # keep identical to the detection script
$Key = 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management'
$Name = 'HotPatchTableSize'
$old = (Get-ItemProperty -Path $Key -Name $Name -ErrorAction SilentlyContinue).$Name
New-Item -Path 'C:\ProgramData\Contoso' -ItemType Directory -Force | Out-Null
"$(Get-Date -Format s) previous HotPatchTableSize='$old'" |
Add-Content 'C:\ProgramData\Contoso\hotpatch-workaround.log'
Set-ItemProperty -Path $Key -Name $Name -Value $Expected -Type DWord
Write-Output "Set $Name to $Expected; restart required"The script does not restart the device: Microsoft's Remediations guidance says not to put reboot commands in detection or remediation scripts. The log line records the previous value so you can roll back.
Package settings
On the Settings step, upload both files. Microsoft's recommended configuration for the page's sample scripts is Enforce script signature check set to No and Run script in 64-bit PowerShell set to No; pilot the package and confirm the value appears on the device. Assign to a pilot group, set the Schedule (Once, Hourly or Daily), and watch Device status under the package.
Because the registry change needs a restart, plan the restart through your normal update ring restart settings and deadlines rather than from the script.
Roll back
To undo the change, restore the logged previous value, or delete the value if it did not exist before, then restart. Keep the pre-change log and your registry export together.
Should you pause hotpatch or uninstall instead?
Both options exist, and both have costs.
| Option | What it does | Cost |
|---|---|---|
| Registry workaround | Keeps the hotpatch and its security fixes; fixes the app error per Microsoft | Restart needed; value details to confirm |
| Edit the quality update policy so hotpatch is no longer set to Allow | Devices fall back to the standard cumulative update path | Needs a restart for each cumulative update; check the exact option label in your tenant |
| Uninstall the hotpatch | Microsoft documents it for unexpected issues: uninstall the hotpatch, install the LCU, restart | Restart; device leaves the hotpatch cycle until the next baseline |
The documented rollback reads: "Automatic rollback of a hotpatch update isn't supported but you can uninstall them," and uninstalling is quick but requires a restart. Security updates fix vulnerabilities that attackers can exploit, so do not strip a device of the update without installing the standard one. We recommend the registry workaround rather than uninstalling; the uninstall row is listed only because Microsoft documents it.
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| Error 0xC0000099 on a device on KB5132061 | Not this issue | Microsoft says the standard update is not affected; look at the app, disk and permissions instead |
| Workaround set but the app still fails | Wrong number base or type, or no restart yet | Re-read the alert text, confirm DWORD and base, restart |
| Value reverts after a reboot | A policy or script is overwriting it | Check other Intune scripts and Remediations targeting the key |
| Detection script never fires | UBR is not 9911 or the device is on the standard update | Run the PowerShell check in Step 1 |
| Intune shows the Remediation as failed | Exit code or encoding problem | Microsoft says scripts must be UTF-8 and the detection script must use exit 1 to trigger remediation |
| Devices can no longer get hotpatch | VBS stopped running or the baseline is missed | Microsoft's alert "Hotpatch - VBS not running" and the hotpatch troubleshooting steps |
What to watch next
- The service alert WI1559710 in the Microsoft 365 admin center, which is where Microsoft updates guidance first.
- The Windows 11 24H2, 25H2 and 26H2 release health pages and the KB5132043 page, where a known-issue entry and a resolution should appear.
- Your December plan: December is also a planned hotpatch month on Microsoft's calendar, so a fix may arrive as a hotpatch or an out-of-band update. Check the hotpatch calendar before you tell users whether to expect a restart.
Checklist
- Identify devices on KB5132043 (build ending
.9911); ignore devices on KB5132061. - Read the service alert for the registry value type and number base.
- Export the registry key; apply the workaround on a pilot PC and restart.
- Confirm apps launch, and the hotpatch policy still shows on the device.
- Deploy the detection and remediation pair to a pilot group, then widen.
- Keep the previous-value log for rollback.
- Watch release health for the permanent fix, then remove the workaround deliberately.
See also
- Package Win32 Apps for Intune with IntuneWinAppUtil and Detection Rules
- Windows Autopilot error codes: fix 0x80180014, 0x800705b4 and more
- Silent BitLocker encryption with Intune and recovery key escrow to Entra ID
What we checked
- Opened the KB5132043 support page on 2026-11-20: release date 2026-11-10, builds 26300.9911, 26200.9911 and 26100.9911, and it says Microsoft is not currently aware of any issues with the update.
- Opened the Windows 11 24H2 and 25H2 release health pages on 2026-11-20 (page timestamps 2026-11-19 18:04 UTC): neither lists this issue yet.
- Cross-checked the issue wording across two secondary reports, BleepingComputer and WindowsForum quoting it: both give ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099), the msi.dll explanation, the registry path, the value name and the data
2000. Neither states the value type or number base; both say no fix date. - Compared Microsoft's hotpatch documentation (Windows Autopatch) with the Intune Remediations page: the hotpatch eligible-license list includes Microsoft 365 Business Premium, while the Remediations license list does not, which is why the licensing caution is in Step 4.
- Recalculated the number base: decimal 2000 is 0x7D0 (7 x 256 + 13 x 16), and hexadecimal 2000 is 8192 (2 x 4096).
- Confirmed from the Remediations page that remediation scripts run only when the detection script exits with
1, that scripts should be UTF-8 and that reboot commands should not be in the scripts. - Not checked: we did not reproduce the error, did not test the scripts on a live tenant or device, and could not open Microsoft's service alert itself; the workaround details are as reported on 2026-11-19 and 2026-11-20.
Last tested: 2026-11-20
References
- KB5132043 hotpatch update page
- Windows 11, version 24H2 known issues and notifications
- Windows 11, version 25H2 known issues and notifications
- Hotpatch updates (Windows Autopatch)
- Use Remediations to detect and fix support issues (Intune)
- BleepingComputer: Microsoft confirms app installation, launch issues after hotpatch
- WindowsForum: Windows 11 Hotpatch KB5132043 triggers 0xC0000099 app errors
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.