Error 0X800f0922 when installing Windows update KB5012170

I've subscribed to this community topic and just got notified. Glad you and others got it worked out like I finally did. To be fair, the GPT requirement was actually explained earlier in this thread by 沉桀贺, rodnay, and myself and alluded to by others here. It's a hardware issue. Granted, Microsoft complicates the matter in their KB5012170 article by stating there is an "ongoing investigation" which implies an eventual possible fix. But there is NO FIX possible if your hardware doesn't meet the minimum requirements of the KB5012170 update. OEMs can't fix the issue with a BIOS update alone either. OEMs don't have control of the partition type of our boot drives. Like I implied before, it's just unfortunate that the Windows Update application doesn't recognize that a system doesn't meet the hardware requirements. If it did, Windows Update could simply SUPPRESS any mention of KB5012170 entirely for platforms that don't comply with ALL the system requirements like Secure Boot, TPM, UEFI, GPT partition (vs. MBR). Including that tidbit of info in their KB article months ago would have cleared up all the confusion.

Here's one for THE SHOW....

after months of attempts by windows update to install this update it finally slipped in on October 13th... i had given up trying everything as i've never had secure boot set on this box... Lo and Behold... all the failed attempts at installing KB5012170 disappeared from the update history log... Hmm i thought to myself, self, ya know - that is weird... just cleaning up the mess left in the log by the problematic child i suppose....

Well, it gets even better !!!!!

Today, Update attempted to install this little critter again and you guessed it... IT FAILED.... AaaaHaHaHaHa...

So, i ask you to tickle yourself all over just to make sure you're not sleeping...

Did it really successfully install on the 13th - a mere 3 days ago or was that Update just dreaming up the perfect date, what kind of restaurant to go to and whether to do a movie afterwards or just back to someones pad and crash.... LOL

Just disable Windows Update with this:

https://github.com/WereDev/Wu10Man/releases

Microsoft is trying to destroy your Windows 10 installation to nudge you towards a new Windows 11 machine.

As mentioned in a previous reply, I DO have a motherboard that supports Secure Boot, TPM, UEFI, GPT partitions, which are prerequisites for the KB5012170 update. However, I still miss out on Windows 11 support due to my ineligible 1st-generation AMD Ryzen APU.

After backup of my important data in case of OS/boot drive corruption, I decided to tackle my MBR vs. GPT drive issue again. I was finally able to move/resize the problem partitions on my primary system C:/ drive using an awkward and tedious combination of Paragon Hard Disk Manager 17 (which I happen to have a license for), and Windows 10 'DISKPART' and 'MBR2GPT' commands. Then I was able to successfully convert that MBR drive to GPT without data loss, disable CSM in BIOS, and restart Windows. Windows Update was able to install KB5012170 on its next attempt.

Where I feel Microsoft is failing is that in their KB5012170 topic article they continue to state there is an ongoing investigation which implies an eventual possible fix down the road from them or from some OEMs of some systems -- even worse they fail to clearly list or link to the system requirements for KB5012170. No OEM can fix the 'Error 0X800f0922' installation issue with firmware if the platform on the motherboard doesn't even support Secure Boot, TPM, UEFI, GPT partition requirements. On a board that does support them, it needs to be clearer in OEM and Windows documentation how to enable each feature so all are actively present. A reasonable fix from MS might be to figure out a way to better detect systems that don't meet the system requirements and NOT offer the KB5012170 update at all through Windows Update on those systems. MS should also offer within the KB article a link to the solution they used to when specific security updates could not be installed.

https://social.technet.microsoft.com/wiki/contents/articles/53184.show-or-hide-updates-utility-fixing-automatic-installation-of-a-problematic-update-in-windows-10-version-1903.aspx

Sorry, I realize this update from me is wordy but I'm too tired to go back and edit.

Good luck all !

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

.