Windows 11’s November Hotpatch Is Breaking Some App Installs and Launches, and Microsoft’s Workaround Is a Registry Change
Microsoft confirms KB5132043, the November hotpatch, can stop some apps installing or launching with error 0xC0000099, and offers a Registry workaround. Who is affected, what to check first, and why we would not uninstall it.

Microsoft has confirmed that the November 2026 hotpatch for Windows 11, KB5132043, can stop some applications from installing, launching or running, and has published a temporary workaround that means editing the Registry on every affected PC. The Register reported the confirmation on Friday 20 November, and heise has covered it too. Microsoft’s guidance, as both outlets relay it, is that the fault hits PCs that took the hotpatch through Windows Autopatch and not PCs that took the standard November cumulative update. When we checked on the afternoon of Friday 20 November, Microsoft’s public page for the update still said it was not aware of any issues with it.
#What Microsoft has acknowledged
According to The Register, Microsoft says affected applications may fail during installation, launch or use, with errors such as “ERROR_ALLOTTED_SPACE_EXCEEDED (0xC0000099)”. Microsoft’s early investigation points to applications that load the 32-bit Windows Installer library, msi.dll. The problem is more common with 32-bit software, but 64-bit applications can be hit “under certain circumstances”, in Microsoft’s words as quoted by The Register. The Register adds that the list of casualties includes Outlook.
heise says Microsoft flagged the problem in its cloud admin centre, citing BleepingComputer. That matters in practice, because the public support page for KB5132043 covers the November 10 hotpatch for Windows 11 versions 24H2, 25H2 and 26H2, builds 26100.9911, 26200.9911 and 26300.9911, and its known issues section said Microsoft was not aware of any problems. Anyone who triages from that page alone would have concluded the update was clean.
#Who is exposed and who is not
This is a managed-fleet problem. Microsoft’s Autopatch documentation says hotpatch updates are monthly security updates that install without a restart, that they need Windows Autopatch, a Microsoft Intune quality update policy with hotpatch turned on, Windows 11 24H2 or later, virtualization-based security switched on, and the latest quarterly baseline. The November hotpatch needs the October 13 baseline, KB5127648, as a prerequisite, according to Microsoft’s KB page. The eligible licences listed include Windows 11 Enterprise E3 and E5, Microsoft 365 F3, Education A3 and A5, Windows 365 Enterprise and Microsoft 365 Business Premium.
Microsoft’s guidance, quoted by The Register, is that devices which installed the standard November 2026 monthly security update are not expected to be affected. The standard update for the same Windows versions is KB5132061. So the question to ask of a PC is not “is it Windows 11?” but “did it take KB5132043?”. A PC on a normal restart-required update ring is outside the problem. A PC on a hotpatch policy that has already installed the November package is inside it, and The Register notes that Microsoft made hotpatching the default in Windows Autopatch earlier this year. We think that means more managed devices are on that track than many administrators realise.
#The workaround, and a snag with its value
The temporary fix is a single Registry value. Both outlets give the same location: under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management, set HotPatchTableSize to 2000, then restart. The Register warns that the change is not for the faint of heart and that a backup is a good idea. heise says the value is a REG_DWORD, that the figure is hexadecimal, and makes an observation that deserves attention: the instruction is supposed to increase the value, but on the machines heise checked it was already set that way.
We think that detail should change how you roll this out. Two outlets agree on the key and the number, but they do not both say what base the number is in, and one of them found test machines that already had it. Take the exact value, data type and base from Microsoft’s own service alert in the admin centre, not from a news article or from this one, and read the current value on an affected PC before you overwrite anything. If the value is already at the figure Microsoft gives and the PC still fails, that is itself useful information for Microsoft’s support case.
The restart is the awkward part. The point of hotpatching is that the monthly security update takes effect without one. Having to restart every affected device to apply a workaround for a hotpatch fault takes away much of what the hotpatch policy was meant to save, and The Register did not miss the irony.
#Why we would not roll the hotpatch back
The tempting response is to remove KB5132043 from the affected devices. We would not, and heise’s advice is to use the workaround instead. heise’s reasoning is that the November security updates close vulnerabilities that are already being exploited in the wild, so uninstalling is not a sensible option. We have not independently confirmed that statement for every fix in the package, so treat it as heise’s account. Our own Patch Tuesday story for November lists the exploited flaw and the other fixes in the month, and it is worth a read before anyone proposes leaving machines unpatched. In our view a broken installer on some devices is a manageable cost, and an unpatched, exploited vulnerability is not.
There is a second reason to keep the patch: the fault is narrow. heise’s wording is that “some applications” are affected. That does not mean every Office install, every MSI-based setup or every hotpatched PC will fail. Most fleets will find a minority of devices and a handful of applications. The job is to find those quickly, not to treat the whole estate as broken.
#What we would do before the weekend
Our advice, in the order we would do it:
- Work out which devices took the hotpatch. In Intune and the Autopatch reports, filter for devices on the hotpatch quality update policy that have installed KB5132043, or check for the build numbers above. Everything else can wait.
- Look for the symptom before you apply a fix. Search your help desk tickets and your software deployment logs for 0xC0000099 and for installers or applications that began failing after November 10. If nothing is failing, the workaround is a decision rather than an emergency.
- Read the current
HotPatchTableSizevalue on one failing PC and one healthy PC, and write both down. - Back up the key, apply Microsoft’s value to a small pilot group using your normal configuration or script route, restart, and test the failing applications again.
- Only then widen it. Do not push a Registry change to the whole estate on the strength of a news story.
- Check the admin centre service alert again on Monday. Microsoft has not told us when a permanent fix is coming, and none of the reports we read gives a date, so assume the workaround will be needed for a while.
If you run software deployment tools such as Intune, Configuration Manager or a packaging pipeline, pause large installer jobs to hotpatched devices over the weekend. A failed deployment that retries all night produces noise that hides the real picture.
#A note for small firms on Business Premium
If your business has no IT team, one thing in this story may surprise you. Microsoft 365 Business Premium is on the list of licences eligible for hotpatching, so a small firm whose provider manages its PCs through Intune and Autopatch may be inside the affected group even though it has never heard the word hotpatch. Business Standard and Business Basic are not on that list in Microsoft’s documentation. The question to ask your IT provider is plain: “Are our PCs on the hotpatch update track, and have any of them had applications fail to open since 10 November?” If the answer is no to both, you can stop reading. If your provider says yes, let them do the Registry change, and ask them to test it on one PC first. Do not edit the Registry yourself.
#How it fits the pattern
Our Windows Update Watch for November already advised caution over a separate SQL Server linked server problem, which Microsoft documents for updates released from 13 October, and heise mentions that issue too. A hotpatch fault on top of it means November’s updates carry caveats on more than one track. We think the right lesson is not that hotpatching is unsafe, because the workaround is small and the fault narrow, but that a hotpatch ring needs its own pilot group in the same way a standard ring does. A smaller package that skips the restart is still a code change, and it deserves a test on a handful of machines before it reaches everyone.
What we expect next is a fix delivered either as a corrected package or in the December hotpatch cycle, but that is our reading and Microsoft has not said so. What would prove us wrong is Microsoft publishing a revised November package or a date for a permanent fix sooner. We will update this story if it does.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01The Register: Microsoft suggests Registry hack to work around hotpatch woes (20 November 2026)theregister.com
- 02heise online: Microsoft Patch Tuesday: Hotpatches cause app startup problemsheise.de
- 03Microsoft Support: November 10, 2026, Hotpatch KB5132043support.microsoft.com
- 04Microsoft Learn: Hotpatch updates in Windows Autopatchlearn.microsoft.com
- 05Microsoft Support: KB5132061, the standard November 2026 security update for Windows 11support.microsoft.com
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All news
Artificial IntelligenceGoogle Now Keeps Gemini Chats for About Two Months Even With History Off, Up From 72 Hours



Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.
Comments
Add a thoughtful note on Windows 11’s November Hotpatch Is Breaking Some App Installs and Launches, and Microsoft’s Workaround Is a Registry Change. Comments are checked for spam and held for moderation before appearing.