Keep KB5132061 blocked in the deployment rings and open a Microsoft Support for Business case with servicing logs and crash dumps; Microsoft does not currently document the reported EventsInstaller/WLAN failure as a known issue or publish a case-specific remediation.
Current known-issue status
KB5132061 is the November 10, 2026 security update that advances Windows 11 26H2 to build 26300.9974.^1^
The following combination is not currently listed on the Windows 11 26H2 release-health page:
-
EventsInstaller failing with 0x80070057
-
Microsoft-Windows-OneCoreUAP-Wlansvc or WLAN event-manifest registration
- Final servicing result
0x800F0922
-
MEMORY_MANAGEMENT or CRITICAL_SERVICE_FAILED boot loops
The documented KB5132061 installation problem instead lists 0x80070306, 0x800F0989, and 0x800F0993, with an automatic repair delivered to eligible Internet-connected Windows Update clients. That published repair cannot be assumed to cover 0x800F0922 or the observed event-provider failure.^1^ The release-health page likewise lists no matching WLAN/EventsInstaller issue.^2^
A similar Q&A report associates KB5132061 and 0x800F0922 with event-manifest registration, but it is not an official known-issue declaration or remediation.^3^
Do not apply unrelated 0x800F0922 fixes for EFI partition space, licensing-folder permissions, or corrupted scheduled tasks unless CBS contains their corresponding signatures. Your CBS sequence identifies a different advanced-installer path.
Systems that still boot
There is no published supported repair for the specific WLAN publisher state. Since DISM, SFC, update-cache reset, reset, manual installation, and repair installation have already failed, avoid repeating them or manually rebuilding WINEVT/provider registry data across production devices.
For Intune update rings:
- Keep the affected quality-update ring paused.
- If KB5132061 actually installed on any device and remains uninstallable, open the paused ring and select Uninstall → Quality → OK.
- Expect the uninstall request to be sent immediately and a required restart not to be deferrable. Intune also pauses quality updates when that rollback is initiated.^4^
This does not help systems where installation already rolled back, because KB5132061 is no longer installed.
BSOD boot-loop recovery
Have the BitLocker recovery key available before entering Windows Recovery Environment (WinRE). Then use these options in order:
- Troubleshoot → Point-in-time restore, if a pre-update restore point exists.
- Otherwise, Troubleshoot → Advanced options → Uninstall updates → Uninstall latest quality update.
- If Windows still cannot boot, select Advanced options → Command Prompt and identify the offline Windows volume—it may not be
C: in WinRE:
diskpart
list volume
exit
dir C:\Windows
dir D:\Windows
- Run
RevertPendingActions against the identified offline Windows installation:
dism /Image:D:\ /Cleanup-Image /RevertPendingActions
Replace D: with the actual Windows volume. This operation is specifically intended for boot failures caused by pending servicing actions and must target the nonbooting offline Windows image; it must not be run with /Online against a running OS.^5^
If these options fail, Microsoft’s supported recovery sequence proceeds to Reset this PC, cloud rebuild, or reinstallation from OEM/Windows installation media; those options can remove applications, settings, or data.^6^
Quick Machine Recovery can automatically obtain a cloud remediation only when Microsoft has published one for the detected widespread boot issue. If no remediation exists, it returns the device to the traditional WinRE options.^7^
Microsoft escalation package
Collect data before another installation attempt on a reproducible machine:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned -Force
.\TSS.ps1 -CollectLog DND_SETUPReport
Run TSS from elevated Windows PowerShell, not PowerShell ISE. This collection includes CBS, Windows Update, servicing, policy, and setup diagnostics.^8^
Attach:
- TSS output and complete
C:\Windows\Logs\CBS
- System and WLAN-AutoConfig event-log exports from before and after failure
-
wevtutil gl output showing the missing publisher
-
C:\Windows\Minidump, or the kernel/memory dump from each stop code
- Exact model, firmware, storage and WLAN driver versions
- Update-management policy and ring assignment
- A timeline correlating CBS shutdown with the first bugcheck
Request escalation as a reproducible Windows servicing/EventsInstaller failure with a potential pre-rollback boot impact, rather than as a generic 0x800F0922 incident.
References
- November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100 ...
- Windows 11, version 26H2 known issues and notifications
- KB5132061 fails with 0x800F0922 on 26H2 Home China, event manifest ...
- Manage Windows Update ring policies
- DISM Operating System Package (.cab or .msu) Servicing Command-Line Options
- Recovery options in Windows | Microsoft Support
- Quick Machine Recovery in Windows | Microsoft Support
- Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios