Bootcamp Windows 10 22H2 KB5012170 Error: 0x800f0922

I have the exact same problem when trying to update Windows 10 on an iMac 5k 2020 with Boot Camp.

I think it is important to install every security updates to maintain a stable and secured OS.

Apple needs to make a patch or any other solution so users are not struck here.

Please Apple, come forward we need your help here.....

No solution, but maybe a hint:

I have the same problem on an iMacPro 2017, i. e. Win10 with Bootcamp, KB5012170 produces 0x800f0922. Tried all standard remedies.

No such problem on an old MacPro 2013 with Bootcamp and Win10, i. e. KB5012170 was installed without any problems.

No solution, but just to add

iMac (Retina 5K, 27-inch, 2022) has the same issue. I wonder if it relates to the T2 Chip in any way, as the older iMacs are okay. The iMac Pro, iMac (Retina 5K, 27-inch, 2022) and 2019 16" MacBook Pro have a T2 Chip.

I have the same problem with this update (KB5012170) error (0x800f0922).

This update partly concerns the DBX boot system... which concerns security with TPM... but which according to Microsoft must not be blocking to be installed (TPM or not, the patch is able to installed) except that no, there is a bug with the update on some machines depending on the BIOS or other side updates.

It's been 6 months that Microsoft has not been able to correct the problem of this update. The fact that MACs are equipped with the T2 chip does not help.

After being unable to install Windows 11, now Windows 10 beginning to suffer from Microsoft's negligence, signs that mark the beginning of the end of Windows on our Macs... Now we must implement a 100% migration schedule on MacOS-intel and thus prepare the migration to Apple-silicon... and having to change professional software...

Same problem here (MacBookPro16,1) searching for hours to find a fix but not successful so far.

At the moment is looks like not a bootcamp or mac problem as the problem is widely spread also for native windows systems. According to this article https://winfuture.de/news,133551.html it already appeared in a patch in August 2022 already and occurs now again. The article also referes to an official statement from MS: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#2883msgdesc. So it is quite possible that MS has to fix something first before we call out for Apple to help I guess.

Actually it's not just a BIOS update but a change in the motherborad BIOS setting of any Windows based desktop/laptop PC would settle the conflict and let you install the Windows 10 22H2 KB5012170 update.

In any Apple computer you have no access to the BIOS. It's "restricted area" for users because of the hardware/software structure Apple uses...it's simply not designed to be changed or updated by end users.

If I may reenter the discussion: Still no real solution, i.e. KB5012170 works with older Macs (like my Mac Pro 2013) but not with more recent ones with T2 security chip (like my iMac Pro 2017) or such like.

Trying to figure out and understand what the update tries to do and what are the risks not to apply it I found a interesting contribution of Susan Bradley, https://www.computerworld.com/article/3683213/the-trials-and-tribulations-of-microsoft-s-kb5012170-patch.html . She mentions something you might call the ostrich-like method, namely block the update KB5012170. Then you will not see it any more, but you could decide later to make it available again. Fortunately, she links to a website with relevant tools, https://blockapatch.com/ . And, surprise, toll number one is a Microsoft tool, wushowhide.diagcab. I used it and selected KB5012170 to disappear. And it disappeared (after a restart).

Please, be very careful to estimate the risks with and without KB5012170!!!

since this is T2 chip related... let's hope Apple works on a fix with Microsoft... a fix that if it involves the T2 chip... let's hope they also enable TPM and Secure Boot with the fix, so Windows 11 could be officially supported and update from 10 to 11 via Windows Update!

Just adding in on the topic. I’m also having the very same issue. 2019 Intel 16.1 MacBook Pro. Also running the latest software on both Mac and windows. Don’t know about you but it’s kind of annoying having that unsolved update. Most of the times I couldn’t even finish the download, then, one day the update managed to be downloaded and ready to be installed but sadly, after a reboot, the update wasn’t successfully installed and it had to roll back the installation.

I have the same exact issue! Nice to know I am not the only one. I thought there was something wrong with my Mac. I hope Apple releases a fix soon, as I use both Windows and Mac OS Ventura on my 2020 MacBook.

Yes Microsoft recommends updating the BIOS... for those who have an update to do!... the others? Microsoft is behind a BIOS update... visibly at MS they have been bothered with this update since August 2022. PCs are also affected (not all...) hence Microsoft's total incomprehension. Well, that's when you want to impose bogus security (TPM) to secure a "universal" OS... reverse of glory...

In short, the cup is full... anyway the end of Windows on MAC is inevitable. So now we have to prepare for it. A choice to be made, a waiver to be made: Windows with a PC or MacOS on a Mac!!!

It's the end of the two worlds together. The most complicated are the pro software that you have to find on MAC if you still want MAC... (and good luck for the players).

I have the same issue. 2019 Intel 16.1 MacBook Pro.

For me this issue is especially problematic, because it seems to be a mandatory update for Easy Anti Cheat, so I cannot play games anymore using Easy Anti Cheat. Updated a game and since then EAC is unable to launch the game. It's really frustrating, I pretty much use Windows only for gaming.

Same here. iMac 2020. After getting again and again this problem, i was making a clean new install of WIN10.

before that i was getting sure and save my files on an external USB drive. But my drive crashed, it was just bad luck. ALL my files is gone. And after that perfect new white install - you know what ? - SAME F/ PROBLEM.

APPLE GET IT TOGETHER - PLEASE

MBP 2019 16, Monterey 12.6.3, same issue.

It does look like the writing is on the wall, but it'd be nice to eke out some more time with Bootcamp.

Anyone try monkeying around with the partition with a 3rd party tool and live to tell the tale?

EDIT: Re-reading the thread I opted to block the offending update. But I guess I'll start budgeting for a gaming PC. :(