Error 0X800f0922 when installing Windows update KB5012170

Thank you I will try your suggestions

Diogines

Same situation here: Windows 365 Cloud PC.

FWIW I have been attempting to solve the riddle of KB5012170 and the 0x800F0922 error.

What I found in the CBS.log:

2022-08-12 08:48:09, Info CSI 0000006a Secure Boot: 'Attempting to apply Secure Boot update'

2022-08-12 08:48:09, Info CSI 0000006b Secure Boot: 'The Secure Boot update could not be applied. This may be due to your BitLocker configuration (e.g. policy that disallows Secure Boot for integrity validation). Please suspend BitLocker before applying the Secure Boot update or fix the policy conflict.'

2022-08-12 08:48:09, Error CSI 0000006c@2022/8/12:15:48:09.066 (F) onecore\base\secureboot\servicing\advancedinstaller\securebootai.cpp(363): Error HRESULT_FROM_WIN32(1) originated in function Windows::WCP::SecureBoot::BasicInstaller::Install expression: hr
[gle=0x80004005]
2022-08-12 08:48:09, Error [0x01805a] CSI 0000006d (F) Failed execution of queue item Installer: Secure Boot Installer ({3a4bacaa-c2db-4cf6-8a6b-7d9dfd5155f1}) with HRESULT HRESULT_FROM_WIN32(1). Failure will be ignored: The failure was encountered during rollback; installer is reliable[gle=0x80004005]
2022-08-12 08:48:09, Info CSI 0000006e@2022/8/12:15:48:09.067 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3a4bacaa-c2db-4cf6-8a6b-7d9dfd5155f1};Microsoft-Windows-SecureBoot-FirmwareUpdate, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};75266us
2022-08-12 08:48:09, Info CSI 0000006f End executing advanced installer (sequence 76)

Seeking some explanation about 0x80004005 has not been completely successful.

The system with the problem is a Dell 9020 MT. TPM 1.2 . Secured Boot is not in use. BitLocker is disabled.

Two other systems have KB5012170 installed. BitLocker not enabled. One without any TPM; the other with TPM 2.0.

One difference between the problem system and the other two is the presence of the System Reserve volume in use on the problem child box. It is 500 MB in size and mostly occupied with about ~160 MB free. Running CHKDSK against the volume found no errors.

The following link concludes with a fix which is an upgrade in place of the OS, see: https://answers.microsoft.com/en-us/windows/forum/all/secure-boot-installer-phase-of-update-kb4541335/bf9f46dc-ba4a-4e52-8395-6a8d2609ff2b

.

Yes. I have opened a ticket with Microsoft and will let you know what I hear back. However I recommend you open one as well so they get visibility to this issue.

Me too - you'd think that would eliminate the "hardware / driver issue" wouldn't you?