Microsoft's November Windows 11 Hotpatch Is Breaking App Installs
Microsoft has confirmed that its November 2026 Windows 11 hotpatch breaks app installs and launches on enterprise PCs, throwing an error about allotted space. Home users are unaffected.

Microsoft has confirmed what enterprise IT teams have been reporting all week: the November 2026 Windows 11 hotpatch breaks app installs and launches. The company acknowledged the problem on November 19, after users reported printing issues and crashes in Citrix Workspace and Sage 50 following the November updates. One administrator traced the issue to a file in the update, and Microsoft's own analysis has now confirmed it. The Windows 11 hotpatch that was supposed to make patching easier is, for some machines, making software unusable.
The Windows 11 hotpatch problem
The issue is caused by a hotpatch update released this month, KB5132043, for OS builds 26100.9911, 26200.9911 and 26300.9911. Hotpatching is Microsoft's way of applying security fixes without a restart, and it is a genuinely useful feature for machines that cannot afford downtime. This particular hotpatch contains security improvements, but it also contains a file, msi_hotpatch.dll, that breaks something fundamental.
Affected devices show an ERROR_ALLOTTED_SPACE_EXCEEDED error, code 0xC0000099, when attempting to install, open or run certain applications. Microsoft's analysis shows the issue only affects applications that include the 32-bit Windows Installer Dynamic Link Library, known as msi.dll. That sounds narrow until you realize how many applications still ship a 32-bit installer component, including Microsoft Office and a long list of third-party business apps.
The service alert, tracked as WI1559710, describes installation, launch and runtime failures. In plain language: apps fail to install, apps fail to open, and apps that do open can fail while running. For an office worker, that means the tools they need for their job stop working, and the fix is not obvious.
Who is affected, and who is not
The scope is specific, which is both good and bad news. Systems in enterprise environments running Windows 11 version 24H2 or later and receiving the update via Windows Autopatch are affected. Devices managed by Intune or the Microsoft Graph API have had hotpatching automatically enabled since earlier this year, so the issue is hitting a larger number of managed devices than it would have a year ago.
Home edition devices are unaffected. Systems that received the standard November 2026 Patch Tuesday cumulative update, KB5132061, are also unaffected. That distinction matters: the problem is not the November security fixes in general, it is the hotpatch delivery mechanism specifically. If your machine got the regular cumulative update and a restart, you are fine.
This is the kind of bug that punishes the most organized IT departments. The companies that adopted Autopatch and hotpatching did exactly what Microsoft recommended. They automated patching to stay secure without disrupting users. Now they are the ones with broken apps, while the companies that patched the old-fashioned way are unaffected. That irony will not be lost on anyone who has to explain the outage to a manager.
The workaround, and what Microsoft has not said
Microsoft has recommended a registry change as a temporary workaround until a long-term fix is available. Registry edits are not something most users should attempt on their own, and in a managed enterprise environment they need to be deployed carefully, tested, and rolled back once a real fix ships. It is a workaround, not a solution, and Microsoft has not specified when a long-term solution will be available.
That last part is the frustrating one. A bug that breaks app installs across enterprise fleets deserves a timeline, even a rough one. Microsoft has confirmed the problem and published a workaround, but the absence of a fix date leaves IT teams in limbo: deploy a registry hack across hundreds of machines, or wait and hope the fix comes soon.
There is a broader lesson here about the November update cycle. The Samsung One UI 9.5 beta is testing new features for Galaxy phones, and Chrome 158 just shipped with faster releases. Every vendor is pushing updates faster, and the trade is always the same: speed against stability. Hotpatching was supposed to reduce that trade by removing restarts. This month, it introduced a different kind of disruption instead.
What IT teams should do today
First, check whether your fleet received KB5132043 through Autopatch. If it did, and users are reporting app failures with the 0xC0000099 error, you have found your cause. Second, test Microsoft's registry workaround on a small group before deploying it widely. Third, tell your users what is happening in plain language: a Microsoft update broke some apps, there is a temporary fix, and a permanent one is coming.
For home users, the advice is simpler: if you are on Windows 11 Home, you are not affected, and there is nothing to do. If you are on a work machine and your apps stopped working after a November update, tell your IT team and mention the hotpatch by name. It will save them an hour of troubleshooting.
Microsoft will fix this. The company has too much riding on hotpatching to let a bug like this linger. But the incident is a reminder that the plumbing of updates matters as much as the updates themselves. A security fix that breaks the software it is supposed to protect is not a security fix. It is a new problem wearing a patch's clothes.


