Win 10 22H2 update KB5021233 install fails with 0x800f0922

Topic

New Reply

Tried several times to install the latest 22H2 update, KB5021233.  Apparently no trouble downloading and doing preliminary install.  Then, after first restart, fails at 97%.  After recovery and restart, Update panel shows it failed with 0x800f0922.

My system:  Asrock Z370 Pro 4.

Pre-install:  firewall and vpn disabled.
SFC showed no errors.
DISM CheckHealth and ScanHealth showed no errors.
KB5020872 installed correctly today 12/22/2022 just prior to KB5021233 failure.
KB4023057 installed correctly 12/10/22.
KB5020687 installed correctly 12/9/22

Reply | Quote

Replies

Follow the thread at :

https://www.askwoody.com/forums/topic/several-windows-10-versions-affected-by-blue-screen-issue/

1 user thanked author for this post.

Mike

Reply | Quote

DanM.  Here’s a direct link to where you want to start. Not saying that this will help but it’s a good place to begin reading.

https://www.askwoody.com/forums/topic/several-windows-10-versions-affected-by-blue-screen-issue/#post-2510432

1 user thanked author for this post.

DanM

Reply | Quote

Thank you to those who suggested I look at the BSOD thread! Interesting information. Fortunately I do not have the offending extra hidparse.sys file loose in \System32\.
But it is in \System32\DriverStore\
and four places in WinSxS\
and two places in \servicing\LCU_Package
I kind of doubt that is the reason for my installation error.

The error itself is puzzling: 0x800f0922 People have over years reported various causes for this error in installing the update. The most common is that it identifies a download error, but in my case the package does seem to download correctly and fails near the end of the installation script. Less commonly, people have suggested DISM errors (none found), Insufficient space in the 500mb reserved partition (nope, at 58% after downloading), system update data (nope, I reset it), BIOS (not convincing), out of date .NET (nope, latest version as of 12/22/22, from manual download), VPN or Firewall (nope, install fails after restart apparently before loading these, besides which I tried it with these disabled).

Reply | Quote

Did you check this post out over on the device forums? Perhaps you’re one of the people that posted. There are some additional ideas.  What about disabling secure boot?

https://forum.asrock.com/forum_posts.asp?TID=24817&OB=DESC

1 user thanked author for this post.

DanM

Reply | Quote

Mike: thanks for the tip.

Secure Boot was disabled during previous tries. So I enabled it, installed default keys and set other defaults, but the update still failed.

I have subsequently written to Asrock to inquire. From what I read in the device forums, it is possible that my UEFI is out of date but we shall see.

Reply | Quote

@DanM –

What’s the date and version number of your BIOS? That will help determine if there’s an update out there for it.

If you’re not too sure just how to get it, there’s a way from within Windows that you can find this info out. Use the System Information utility that’s on the Start Menu.

Left click on the Start menu, and scroll down the list of “folders” and installed apps to a folder-looking item that says “Windows Administrative Tools” and click on it. Now, on the list that just opened, scroll down the list until you see an item labeled “System Information” and click on it. That will bring up all kinds of info about your system.

In this window, make sure “System Summary” is highlighted in the list on the left side. Once it is, look through the list on the right side, and you should see a listing that says “BIOS Version/Date” that should be located right under the listing for which processor you have. I.E., you’ll see an entry that says “Processor” and the next entry below it should be the one that says “BIOS Version/Date”. On my system, the BIOS Version/Date is the 11th one down on the list.

This listing shows the currently installed version and date of your system’s BIOS/UEFI firmware, and may even show the name of the actual manufacturer of your BIOS, such as Award or AMI (American Megatrends, Inc.).

Reply | Quote

Bios L0.01  Very suspicious version number on an OEM board, not noted on the Asrock downloads page.  Asrock said to update to latest version.

Reply | Quote

https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#kb5012170-might-fail-to-install-and-you-might-receive-a-0x800f0922-error

The same error code as KB5012170.

Reply | Quote

@DanM did you manage to fix this? I’m running into the same issue

Reply | Quote

I’m noticing these errors in the CBS.log.

 

2023-01-04 22:40:47, Error                 CSI    000009c3@2023/1/5:06:40:47.688 (F) Logged @2023/1/5:06:40:47.550 : [l:49 ml:50]'MOF (install online) $(runtime.wbem)\netprofm.mof'
[gle=0x80004005]
2023-01-04 22:40:47, Error                 CSI    000009c4@2023/1/5:06:40:47.688 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]
 [
'An error occurred while creating object 1 defined on lines 14 - 39:
0X80041002 Class, instance, or property 'EventTrace' was not found.
'
]
[gle=0x80004005]
2023-01-04 22:40:47, Error                 CSI    000009c5@2023/1/5:06:40:47.688 (F) CMIADAPTER: AI failed. HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]
	Element:
	''
[gle=0x80004005]
2023-01-04 22:40:47, Error                 CSI    000009c6@2023/1/5:06:40:47.688 (F) CMIADAPTER: Exiting with HRESULT code = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)].
[gle=0x80004005]
2023-01-04 22:40:47, Error      [0x018020] CSI    000009c7 (F) Failed execution of queue item Installer: Mof ({9f4ec79f-3a97-4772-b635-2899468900a2}) with HRESULT 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)].  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]



2023-01-04 22:41:19, Info                  CSI    00000a5b The queue has completed running, and AI failures have occured.
2023-01-04 22:41:19, Info                  CSI    00000a5c ==Error Summary Start==
2023-01-04 22:41:19, Error                 CSI    00000a5d (F) Installer: Mof	Binary Name: cmiadapter.dll	ErrorCode: 80041002	Phase: 32	Mode: Install (upgrade)	Component: Microsoft-Windows-NetworkProfile-CIM, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]
2023-01-04 22:41:19, Info                  CSI    00000a5e ==Error Summary End==
2023-01-04 22:41:19, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2023-01-04 22:41:19, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2023-01-04 22:41:19, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0
2023-01-04 22:41:19, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
2023-01-04 22:41:19, Info                  CBS    Setting original failure status: 0x800f0922, last forward execute state: CbsExecuteStateResolvePending
2023-01-04 22:41:19, Info                  CBS    Attempting to remove poqexec from SetupExecute
2023-01-04 22:41:19, Info                  CBS    Removed poqexec from SetupExecute.
2023-01-04 22:41:19, Info                  CBS    Configured poqexec to not pend to SetupExecute.
2023-01-04 22:41:20, Error                 CSI    00000a5f (F) Installer: Mof	Binary Name: cmiadapter.dll	ErrorCode: 80041002	Phase: 32	Mode: Install (upgrade)	Component: Microsoft-Windows-NetworkProfile-CIM, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]
2023-01-04 22:41:20, Info                  CSI    00000a60 Rolling back transactions...



2023-01-04 22:45:24, Error                 CSI    000009c0@2023/1/5:06:45:24.897 (F) Logged @2023/1/5:06:45:24.730 : [l:49 ml:50]'MOF (install online) $(runtime.wbem)\netprofm.mof'
[gle=0x80004005]
2023-01-04 22:45:24, Error                 CSI    000009c1@2023/1/5:06:45:24.898 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]
 [
'An error occurred while creating object 1 defined on lines 14 - 39:
0X80041002 Class, instance, or property 'EventTrace' was not found.
'
]
[gle=0x80004005]
2023-01-04 22:45:24, Error                 CSI    000009c2@2023/1/5:06:45:24.898 (F) CMIADAPTER: AI failed. HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]
	Element:
	''
[gle=0x80004005]
2023-01-04 22:45:24, Error                 CSI    000009c3@2023/1/5:06:45:24.898 (F) CMIADAPTER: Exiting with HRESULT code = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)].
[gle=0x80004005]
2023-01-04 22:45:24, Error      [0x018020] CSI    000009c4 (F) Failed execution of queue item Installer: Mof ({9f4ec79f-3a97-4772-b635-2899468900a2}) with HRESULT 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)].  Failure will be ignored: The failure was encountered during rollback; installer is reliable[gle=0x80004005]
2023-01-04 22:45:24, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2023-01-04 22:45:24, Info                  CBS    Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CBS.log to WER report.
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20230105035928.cab to WER report.
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20230105024929.cab to WER report.
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20230105020438.cab to WER report.
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20230104234843.cab to WER report.
2023-01-04 22:45:24, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20221224215006.cab to WER report.
2023-01-04 22:45:24, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-01-04 22:45:24, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Reply | Quote

See post below.  Asrock indicated possible BIOS issue causing the update to fail.

Reply | Quote

I have seen one cause of error 0x800f0922  in connection with the attempted uninstall of Edge. It had to do with a misconfiguration in the Edge installation location. There are other posts in the same time frame as this one discussing this issue. Use search “800f0922” on this site to find more info.

See the bottom half of this post #2372696.

1 user thanked author for this post.

DanM

Reply | Quote

Thanks for the tip.  I will look into the Edge question.

In the meantime, I I have contacted Asrock re. possible BIOS issues  on my Z370 Pro4 board.  They indicated it was likely there was a BIOS issue, given I have an OEM board with an unusual version.  I suspect the problem is in BIOS secure boot code, as others here have mentioned.  I am waiting for an appropriate time to update to the latest.

Reply | Quote

I too was encountering unending rollbacks and error 0x800f0922 with the December 2022 Windows 10 update (and then the January one as well).

The solution posted here for fixing a corrupted WMI repository allowed me to install the January update successfully: https://answers.microsoft.com/en-us/windows/forum/all/2022-12-cumulative-update-for-windows-10-version/aa8f5cda-fd44-46ad-902f-4bcb02ab2b03

For the Acronis article referenced, I did only the “If the problem remains after consistency check, rebuild the WMI repository” portion in the expanded bottom portion of the post (after doing the prior steps referenced directly in the Microsoft answer).

Note that in my case my CBS log under C:\Windows\Logs\CBS\ (actually the rotated-out one named CbsPersist_20230112025339.log) contained the exact error posted in the solution. For me, I could find the error details by searching the log for “Rolling back”. Your mileage may vary, but I hope this helps!

1 user thanked author for this post.

DanM

Reply | Quote

I have checked the WMI registry, and it is good.

By the way, I previously had some problems with this registry, but with help from support at Yamicsoft  it was resolved.

Reply | Quote

I have after some delay updated the BIOS on my ASRock Z370 Pro4OEM board to the latest OEM BIOS.  (Not as smooth as I had expected, with some odd surprises, but it is done and working.)

Then I looked to retry KB5021233 but it is no longer available.  I proceeded with the current updates, and now I get the same error code 0x800f0922 for KB5022282.  I can only presume that this later package is actually failing for the same reason as the former, and on the same task.

It remains likely that the Secure Boot portion of the BIOS is the area of concern.  I am still in contact with the excellent service at ASRock, and I will update again with any further results.

Thank you to all those who offered suggestions.  All very helpful and thoughtful replies!

Reply | Quote

Bad Board —  ASRock Z370 Pro4 OEM.

Never did get an answer from ASRock on whether the board is the cause of the Windows Update problem.

Fatal symptoms: after updating BIOS to the latest version, the board could not locate the Windows OS using BIOS Optimal Defaults, which it could do prior to the BIOS update.  But it would boot properly by setting SATA mode to AHCI, and disabling CSM.

 

Reply | Quote

Tried everything and nothing worked.

But after reinstalling Edge update went thrue.

Windows 10 home.

Reply | Quote