Error 0X800f0922 when installing Windows update KB5012170

Question

I have tried disabling the firewall and still receive the same error. Can anyone help solve this problem?

Answer 1

i get error 0x800f0922 with update KB5016616.

help me!!!!!!!!!!

Answer 2

I had the same issue with KB5016616 as KB5012170 which were together as a group and both failed twice, in my case. However, after I went ahead and accepted the "Feature update" from Windows 21H1 to 21H2 that I'd been holding back on for the past several months, KB5016616 installed successfully on Windows Update next attempt.

Answer 3

In case this helps anyone in the same position as me...

I noticed this KB5012170 had failed twice last week. It's been years since I've had a failed update installation that wasn't quickly resolved. When I drilled down into the KB information and saw the update has to do with Secure Boot, TPM, Secure Processor I knew it was doomed to fail (for me). This is because earlier this year I had for several weeks attempted to understand/resolve my particular issue with those features in Windows 10 and for any possible upgrade to Windows 11. I tried all of the suggested solutions found here and elsewhere, including downloading the full update from the Microsoft Catalog.

I have an AMD Ryzen 5 2400G APU. This is, unfortunately, AMD's first-generation Zen CPUs that is NOT on Microsoft's list of compatible processors. Even though when I purchased the CPU in 2019, I made sure it and my motherboard natively supported Secure Boot and TPM having read that those would be potential issues in the "near" future. I have Secure Boot and TPM 2.0 both enabled in my motherboard UEFI settings. I was always able to see both features active in Windows 10 under the two required areas.

Device Manager / Security Devices / Trusted Platform Module 2.0

and

Windows Settings / Windows Security / Device Security / Security Processor Details

Information about Trusted Platform Module (TPM)

Manufacturer: AMD (AMD)

Manufacturer version: 3.34.0.4

Specification version: 2.0

PPI Specification version: 1.3

TPM Specification sub-version: 1.38 (3/1/2018)

PC client spec version: 1.01

Status

Attestation: Not Ready

Storage: Ready

However, no matter whether I clear or reset TPM keys using Windows built-in method or via UEFI setup, I am unable to change the 'Not Ready' status. I am now assuming that is because Windows Security and related Windows Update recognize my ineligible CPU. I wish the errors generated would confirm this, but they are too generic or ambiguous.

I do not have BitLocker enabled.

There is nothing the hardware manufacturers, AMD or ASRock, can do as long as Microsoft does not allow my CPU/APU. I don't have the newest firmware available for my motherboard model installed BUT I do have the newest firmware installed that is recommended by ASRock for my Raven Ridge generation APU.

Like others, I am also unable to convert my MBR primary drive to GPT (another requirement of Secure Boot) even using MBR2GPT with /allowFullOS switch enabled. I receive the error, ValidateLayout: Last partition too close to the end of the disk and haven't been able to achieve success by resizing a few times either the primary or recovery partition by single digit percentages. I'm too nervous to be any more aggressive about resizing. I don't want to corrupt my system doing something I don't entirely grasp 100%. When I test the drive and/or partitions I receive no errors regarding integrity or corruption.

Hardware/System specs:

Edition: Windows 10 Home

Version: 21H2

Installed on: ‎3/‎11/‎2021

OS build: 19044.1889

Experience: Windows Feature Experience Pack 120.2212.4180.0

Processor: AMD Ryzen 5 2400G with Radeon Vega (11) Graphics, 3.59 GHz

Installed RAM: 16.0 GB (13.9 GB usable)

System type: 64-bit operating system, x64-based processor

Motherboard: ASRock Fatal1ty AB350 Gaming-ITX/ac

So, I will attempt to hide this Windows Update and any subsequent future updates related to the same issue using the wushowhide.diagcab patch method described here. Thanks to all who responded.

Answer 4

Thanks David. I also have systems affected by this issue which appeared after last patch Tuesday (started appearing 10th of August) and since the error code is a repeat offender that goes back four years, I've been trying all sorts of things discussed in the forum to no avail.

Answer 5

I had the same issue with KB5016616 as KB5012170 which were together as a group and both failed twice, in my case. However, after I went ahead and accepted the "Feature update" from Windows 21H1 to 21H2 that I'd been holding back on for the past several months, KB5016616 installed successfully on Windows Update next attempt.

i already have 21H2