Share via

Error 0x800f0922 installing windows update KB5066793 - rollback in phase 31 updating Channel Microsoft-Windows-Store/Operational

Pieter van der Meulen 5 Reputation points
2025-10-25T13:35:08.4166667+00:00

At the end of installing windows update KB5066793 (at 98%) the update rolls back and shows Error 0x800f0922 in windows update.

CBS.log shows the installation rolling back in "phase 31" with an error relating to registering the event channel for Microsoft-Windows-Store/Operational.

I found that an incomplete registration existed for the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Store/Operational. Because this channel it was listed in "wevtutil el" but wevtutil gp Microsoft-Windows-Store/Operational /ge gave an error ("Failed to open metadata for publisher Microsoft-Windows-Store/Operational. The system cannot find the file specified.") I emoved the "Operation" key from the registry and then rebooted and tried again. This did not help, same problem.

Running the windows update troubleshooter and DISM.exe /Online /Cleanup-image /Restorehealth and did not solve the problem. The Windows Store application itstelf seems to work OK. I can check for updates and was able to install an update that append to be available in the store.

From the CBS.log:

2025-10-25 12:42:20, Info CSI 00000a81 Begin executing advanced installer phase 31 index 0 (sequence 0) Old component: [l:0]'' New component: [l:0]'' Install mode: delta Smart installer: true Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998} Installer name: 'Events' 2025-10-25 12:42:20, Info CSI 00000a82 Registry root HKLM\Software: HKLM\Software 2025-10-25 12:42:20, Info CSI 00000a83 Registry root HKLM\System: HKLM\System 2025-10-25 12:42:20, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 96.

2025-10-25 12:42:22, Info CSI 00000a84 wevtconfig warning #77: Channel Microsoft-Windows-Store/Operational is declared by an existing provider Microsoft-Windows-Store-Client-UI{{53e3d721-2aa0-4743-b2db-299d872b8e3d}}. 
2025-10-25 12:42:22, Error CSI 00000a85 (F) Error HRESULT_FROM_WIN32(15010) in eventsXml: <events><provider guid="{9c2a37f3-e5fd-5cae-bcd1-43dafeee1ff0}" message="$(string.eventProviderName)" messageFileName="%SystemRoot%\System32\LicenseManager.dll" name="Microsoft-Windows-Store" resourceFileName="%SystemRoot%\System32\LicenseManager.dll" symbol="Microsoft_Windows_Store"><channels xmlns="http://schemas.microsoft.com/win/2004/08/events" xmlns:win="http://manifests.microsoft.com/win/2004/08/windows/events" xmlns:xs="http://www.w3.org/200[gle=0x80004005] 
2025-10-25 12:42:22, Error CSI 1/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <channel access="O:BAG:SYD:(A;;0x2;;;S-1-15-2-1)(A;;0x2;;;S-1-15-3-1024-3153509613-960666767-3724611135-2725662640-12138253-543910227-1950414635-4190290187)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)S:(ML;;NR;;;ME)" chid="WinstoreLog" enabled="true" isolation="Application" name="Microsoft-Windows-Store/Operational" type="Operational"> [gle=0x80004005] 
2025-10-25 12:42:22, Error CSI <logging> <maxSize>20000000</maxSize> </logging> </channel> </channels></provider></events> Software root Software System root System online=true [gle=0x80004005] 
2025-10-25 12:42:22, Error CSI 00000a86 (F) Error Configuration error. (15010) from InstrumentationManifestInstall at onecore\admin\wmi\events\config\manproc.cpp line 877 [gle=0x80004005]
 2025-10-25 12:42:22, Info CSI 00000a87@2025/10/25:10:42:22.208 CSI Advanced installer perf trace: CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};(null);1673099us 
2025-10-25 12:42:22, Info CSI 00000a88 End executing advanced installer (sequence 0) Completion status: HRESULT_FROM_WIN32(15010) 
2025-10-25 12:42:22, Error [0x01802b] CSI 00000a89 (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT HRESULT_FROM_WIN32(15010). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005] 
2025-10-25 12:42:22, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER] 2025-10-25 12:42:22, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER] 
2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report. 
2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20251025104214.log to WER report. 2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20251025103004.cab to WER report. 
2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20251024215546.cab to WER report. 
2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20251024212641.cab to WER report. 2025-10-25 12:42:22, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20251024205325.cab to WER report. 
2025-10-25 12:42:22, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2025-10-25 12:42:22, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
 2025-10-25 12:42:22, Info CSI 00000a8a Creating NT transaction (seq 2) 
2025-10-25 12:42:22, Info CSI 00000a8b Created NT transaction (seq 2) result 0x00000000, handle @0x6a4 2025-10-25 12:42:22, Info CSI 00000a8c Transaction UoW: {417934e0-b18f-11f0-8330-adbcca60b398} for BeginTransaction 
2025-10-25 12:42:22, Info CSI 00000a8d@2025/10/25:10:42:22.443 Beginning NT transaction commit... 2025-10-25 12:42:22, Info CSI 00000a8e Transaction UoW: {417934e0-b18f-11f0-8330-adbcca60b398} for CommitTransaction
2025-10-25 12:42:22, Info CSI 00000a8f@2025/10/25:10:42:22.443 CSI perf trace: CSIPERF:TXCOMMIT;5945 2025-10-25 12:42:22, Info CSI 00000a90 Creating NT transaction (seq 3) 2025-10-25 12:42:22, Info CSI 00000a91 Created NT transaction (seq 3) result 0x00000000, handle @0x6a4 
2025-10-25 12:42:22, Info CSI 00000a92 Transaction UoW: {417934e6-b18f-11f0-8330-adbcca60b398} for BeginTransaction 
2025-10-25 12:42:22, Info CSI 00000a93@2025/10/25:10:42:22.443 Beginning NT transaction commit... 
2025-10-25 12:42:22, Info CSI 00000a94 Transaction UoW: {417934e6-b18f-11f0-8330-adbcca60b398} for CommitTransaction 
2025-10-25 12:42:22, Info CSI 00000a95@2025/10/25:10:42:22.443 CSI perf trace: CSIPERF:TXCOMMIT;2260 
2025-10-25 12:42:22, Info CSI 00000a96 Begin executing advanced installer phase 31 index 0 (sequence 0) Old component: [l:0]'' New component: [l:0]'' Install mode: delta Smart installer: true Installer ID: {9f4ec79f-3a97-4772-b635-2899468900a2} Installer name: 'Mof' 
2025-10-25 12:42:22, Info CSI 00000a97 LastServiceReady is updated after the last reboot.Returning TRUE from isWinMgmtServiceReady. 
2025-10-25 12:42:22, Info CSI 00000a98 Done with waiting for IsWinMgmtServiceReady- creating mofInstaller 
2025-10-25 12:42:22, Info CSI 00000a99@2025/10/25:10:42:22.600 CSI Advanced installer perf trace: CSIPERF:AIDONE;{9f4ec79f-3a97-4772-b635-2899468900a2};(null);157798us 
2025-10-25 12:42:22, Info CSI 00000a9a End executing advanced installer (sequence 0)
Windows for home | Windows 11 | Windows update
0 comments
Answer recommended by moderator
  1. Ramesh Srinivasan 172.4K Reputation points Volunteer Moderator
    2025-10-30T09:53:15.5166667+00:00

    Please open Regedit.exe and delete this registry key:

    
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{53e3d721-2aa0-4743-b2db-299d872b8e3d}

    See if that resolves the issue.

    KB5066136 Update Rolls back with Error 0x800F0922 » Winhelponline

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl-L 2,360 Reputation points Microsoft External Staff Moderator
    2025-10-27T05:03:46.7766667+00:00

    Hello Pieter van der Meulen,

    Welcome to Microsoft Q&A forum. It's my pleasure to help you today.

    I understand that you are struggling with Windows update. The error you see point to whether an issue with the .NET framework or corruption in the system files.

    To fix the issue, please follow these steps:

    1. Run SFC scan
      • Type "Command Prompt" on the search bar and select "Run as administrator"
      • Type sfc /scannow and press Enter.
      • Restart your PC when it's done.
    2. Delete staged packages and clean up corrupted tasks
      • Type PowerShell on the search bar and select "Run as administrator"
      • Type these commands and press Enter after each:
      • Dism /english /online /get-packages /format:table | findstr /i "Staged"
      • Dism /online /remove-package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~14393XXXX
      • Identify the GUID of SecurebootEcodeUEFI using this command.reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /v ID
      • Delete the entry using these commands:
      • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Maintenance{GUID}" /f
      • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain{GUID}" /f
      • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks{GUID}" /f
      • reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.
      • Restart your PC and try again.
    3. Manually download the update. If the above steps cannot help. You can go to the Windows Update Catalog, find the KB, download it and install it manually.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

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.