Windows 11 and KB5132061: Install Stuck at 99%, Microsoft Confirms and Prepares an Automatic Fix
According to Punto Informatico, some PCs cannot complete the November Windows 11 update: Microsoft has confirmed the issue and started an automatic repair.
✨ Riassunto AI
Windows 11's November update, KB5132061, fails to install on a share of PCs: Windows Update gets stuck at 99%, loops, or returns one of the codes 0x80070306, 0x800f0989 and 0x800f0993. According to Punto Informatico, which read Microsoft's official page, the company has confirmed the issue and is rolling out an automatic repair: internet-connected devices should be fixed within 24-48 hours from 10am Pacific on November 11, with no user action needed. One user traced the cause to Windows Sandbox, but Microsoft's page does not mention it: the two accounts diverge, and this article reports both.
Update KB5132061 shipped on Tuesday, November 10, 2026, for Windows 11 versions 26H2, 25H2 and 24H2, with builds 26300.9974, 26200.9974 and 26100.9974, Punto Informatico reported on November 12, citing Microsoft's official documentation. Among the changes, the outlet lists the customizable context menu and cloud restore for the operating system.
The network has followed a similar case: iOS 27.2.1, Apple's fixes and a point still open.
According to Punto Informatico, some users cannot complete the installation through Windows Update: in most cases the process stalls at 99% or enters an endless loop, and error messages with codes 0x800f0993, 0x80070306 or 0x800f0989 appear. The problem persists even when installing manually the update downloaded from the Microsoft Update Catalog, and DISM and SFC commands do not resolve it.
On the cause, the two sources diverge. According to Punto Informatico, a user analysed the CBS.log file and linked the failure to Windows Sandbox: turning the feature off lets the update install. Microsoft's support page confirms the issue exists but does not mention Windows Sandbox. The outlet itself flags the difference: "Non ci sono riferimenti alla Windows Sandbox" — there are no references to Windows Sandbox — it writes, adding that Microsoft has released the fix anyway. On another point the divergence is in the numbers: Microsoft's page describes the installation problem in relation to KB5127936 and limits it to "Windows 11, version 24H2, Enterprise and Education editions only", while Punto Informatico ties it to KB5132061 on 26H2, 25H2 and 24H2.
For the scope, this article follows Microsoft's official page, which limits the case to 24H2 in Enterprise and Education editions; for the technical cause it follows Punto Informatico, which attributes it to a user and not to a company statement. As for the repair, Microsoft's page says it runs automatically on internet-connected devices using Windows Update: "All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT". No manual action is required, and anyone still facing problems after 48 hours should contact Microsoft support.
KB5132061 also contains other fixes, according to the official page: the fault that stopped USB Audio 1.0 devices from starting, with error code 10 in Device Manager; HDMI and DisplayPort audio that could fail on certain AMD graphics cards; and error 87 when adding a printer published in Active Directory, introduced by the October update. There is also a change affecting PowerShell: signature verification now accepts only valid UTF-8 encoding, so scripts saved with a different encoding may no longer pass validation and must be saved in UTF-8 with a BOM and signed again.