Windows 11 26H2 KB5132061 repeatedly fails with 0x800F0922 / EventsInstaller 0x80070057, some systems enter BSOD boot loop

Michael Blount 0 Reputation points
2026-11-16T20:05:10.6533333+00:00

We are experiencing a widespread Windows 11 26H2 servicing issue in a managed business environment affecting multiple systems.

Affected systems are running Windows 11 Pro 26H2, build 26300.x.

We initially identified the issue in our early test/deployment patch group. Some systems successfully roll the update back and return to Windows, while others enter a persistent BSOD boot loop after the reboot and never complete servicing or rollback.

We have now reproduced the servicing failure on a system that had just been reset and was otherwise healthy.

Controlled reproduction:

  • System was reset using Reset this PC / Keep my files.
  • System reached build 26300.9725 successfully.
  • DISM component-store check reported no corruption.
  • SFC was clean.
  • KB5127694 was installed successfully.
  • Microsoft-Windows-WLAN-AutoConfig/Operational was functional before the next update attempt.
  • We then attempted KB5132061.
  • The update staged successfully and requested a reboot.
  • During servicing, CBS shows Microsoft-Windows-OneCoreUAP-Wlansvc transitioning from 26100.9711 toward 26100.9974.
  • CBS subsequently records failure in eventsinstaller.dll / EventsInstaller with 0x80070057 (E_INVALIDARG).
  • CBS initiates rollback and the package ultimately fails with 0x800F0922 (CBS_E_INSTALLERS_FAILED).
  • KB5132061, KB5121794, and Microsoft-Windows-FodMetadataServicing-Desktop-Metadata consequently report 0x800F0922.

Relevant CBS failure sequence includes EventsInstaller processing the Microsoft-Windows-WLAN-AutoConfig event configuration immediately before the advanced installer failure and rollback.

After rollback, wevtutil gl "Microsoft-Windows-WLAN-AutoConfig/Operational" reports:

type: Admin

owningPublisher:

On the controlled test system, the WLAN publisher metadata that was readable before the KB5132061 attempt was no longer enumerated correctly afterward.

We verified that C:\Windows\System32\wlansvc.dll itself rolled back to the previous binary. The live file SHA256 matches the previous WinSxS payload rather than the 26100.9974 payload, suggesting the file rollback completes while some Event Log/provider servicing does not.

More severe behavior:

On some affected systems, rather than successfully rolling back, the system enters a BSOD boot loop immediately after the reboot phase of servicing. These machines never appear to progress far enough to perform the normal CBS rollback. The CBS logs stop immediately before the reboot and no subsequent servicing entries are created.

We have observed stop errors including MEMORY_MANAGEMENT and CRITICAL_SERVICE_FAILED on affected systems.

Troubleshooting already performed:

  • DISM /RestoreHealth and component-store checks
  • SFC
  • Windows Update component reset
  • Manual update installation
  • Reset this PC / Keep my files
  • In-place upgrade/repair installation on another affected system

An in-place upgrade repaired component-store/SFC health on one machine but did not prevent subsequent updates from failing with 0x800F0922.

Reset this PC produced a clean system in our controlled test, but installing KB5132061 reproduced the servicing failure afterward.

Because multiple production systems are involved, we have paused further deployment rather than continuing invasive remediation.

Questions:

  1. Is there a known issue with KB5132061 / the 26100.9974 servicing payload involving EventsInstaller and Microsoft-Windows-OneCoreUAP-Wlansvc?
  2. Is there a Microsoft-supported remediation for systems already failing with 0x800F0922?
  3. Is there a supported recovery procedure for machines that enter the BSOD boot loop before CBS can perform rollback?
Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

2 answers

Sort by: Most helpful
  1. Chance Maurice Niyonzima 825 Reputation points Independent Advisor
    2026-11-16T21:22:14.47+00:00

    Hello Michael,

    Thank you for posting your question on the Microsoft Windows Forum!

    Since you've reproduced the failure on a freshly reset device and the issue is affecting multiple systems, this doesn't appear to be a typical component-store corruption issue.

    I'm not aware of a published Microsoft known issue linking KB5132061, EventsInstaller (0x80070057), and WLAN-AutoConfig. Given the impact and the BSOD reports, I agree with your decision to pause deployment while the issue is investigated.

    One question: do the affected devices share the same wireless adapter or WLAN driver version? That may help determine whether the issue is tied to a specific driver stack.

    Microsoft References

    I hope this information helps. If so, please click Accept Answer and consider upvoting it. This helps other community members find useful solutions more quickly.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-16T20:06:23.12+00:00

    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:

    1. Keep the affected quality-update ring paused.
    2. If KB5132061 actually installed on any device and remains uninstallable, open the paused ring and select Uninstall → Quality → OK.
    3. 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:

    1. Troubleshoot → Point-in-time restore, if a pre-update restore point exists.
    2. Otherwise, Troubleshoot → Advanced options → Uninstall updates → Uninstall latest quality update.
    3. 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
    
    1. 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

    1. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100 ...
    2. Windows 11, version 26H2 known issues and notifications
    3. KB5132061 fails with 0x800F0922 on 26H2 Home China, event manifest ...
    4. Manage Windows Update ring policies
    5. DISM Operating System Package (.cab or .msu) Servicing Command-Line Options
    6. Recovery options in Windows | Microsoft Support
    7. Quick Machine Recovery in Windows | Microsoft Support
    8. Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.