Windows 11 - KB5012170 fails to install in PDM 18.0.0

Discussion in 'Windows Guest OS Discussion' started by fpmalard, Aug 10, 2022.

  1. Mark Fine

    Mark Fine Kilo Poster

    Messages:
    480
    I can ditto everything you've just said, right down to the early-2013 running Catalina. Eliminating the TPM Chip in the configuration and changing the EfiSecureBoot from 1 to 0 worked for me yesterday. Now I find it hilarious how Parallels suddenly releases an alleged fix for this the very next day. #smh
     
  2. Consonanza.

    Consonanza. Bit Poster

    Messages:
    10
    I can confirm that the latest update (18.0.2 - 53077) has resolved this issue (for me at least). I unhid the offending KB5012170, refreshed the Windows update and it appeared and installed immediately.
     
  3. ParallelWorlds

    ParallelWorlds

    Messages:
    1
    I upgraded to 18.0.2 (53077) and my Windows 11 VM still refuses to install KB5012170 - 0x800f0922
     
  4. Oliver_Ebert

    Oliver_Ebert Bit Poster

    Messages:
    3
    Same here.... :(
     
  5. KonstantinO

    KonstantinO Parallels Developers

    Messages:
    38
    For anyone who still have an issue on 18.0.2 (53077), could you try to restart (not suspend or shutdown) VM before try to install KB5012170.
     
    Last edited by a moderator: Sep 16, 2022
  6. Oliver_Ebert

    Oliver_Ebert Bit Poster

    Messages:
    3
    Hi Konstantin,
    I just did, as you advised. But unfortunately the update still won't install. I always got the error: 0x800f0922.
    Best regards,
    Oliver
     
  7. Bubbles55

    Bubbles55 Bit Poster

    Messages:
    7
  8. ParallelsU457

    ParallelsU457 Bit Poster

    Messages:
    2
    I was able to successfully install KB5012170 on Windows10 after upgrading to Parallels 18.0.2 (without having to resort to removing the TPM chip, etc.).
     
  9. LauraS7

    LauraS7 Bit Poster

    Messages:
    1
    I am also having this issue. I downloaded the latest hot fix (v. 18.0.2) and still cannot install the update and am getting error 0x800f0922. I've also tried restarting the VM as suggested above with no luck.
     
  10. Oliver_Ebert

    Oliver_Ebert Bit Poster

    Messages:
    3
    Just for your information:
    After installing the Windows 11 22H2 update and the following updates, the update, which could not bei installed (KB5012170) is no longer presented as an update. So for me the problem is resolved.
     
  11. BrockC

    BrockC Bit Poster

    Messages:
    1
    This issue still stands for me... even with 18.0.2
     
  12. sutepanushikind

    sutepanushikind Bit Poster

    Messages:
    5
    try to restart VM (not suspend or shutdown).
    If it doesn't work try:
     
  13. Harryw5

    Harryw5 Bit Poster

    Messages:
    1
    Update errors can frequently occur due to system files that got corrupted.If you are confronting the 0x800f0922 mistake at whatever point you attempt to refresh your gadget, the issue exists in the obsolete UEFI/BIOS.You can either cripple the constant assurance highlight on your enemy of malware or briefly uninstall the application. The two techniques work, and it involves your inclination. Once finished, you ought to start the download and establishment cycle of the KB5012170 update and check whether it settle the issue.
     
  14. JonD8

    JonD8 Bit Poster

    Messages:
    2
    I've been rebooting and retrying this update for a month and I'm still not able to install the update. Windows must be detecting I'm using one of the vulnerable firmware's it's trying to add to the block list, that's what the 0x800f0922 means as far as I know. Is there any way to check firmware version of my VM?

    My Parallels is updated to Version 18.0.2 (53077), and I'm using an Intel MBP (MacBookPro16,1)

    Thanks,
     
  15. KathyL2

    KathyL2

    Messages:
    1
    I am running 18.0.2 I've tried the TPM removal, the switching the EFIboot. I've reset the Windows Update service. I've restarted. Problem remains.
     
  16. TH8

    TH8 Bit Poster

    Messages:
    4
    I have the same issue - upgrading to Parallels Desktop 18 for Mac (version 18.0.3) still does not fix this issue.
     

Share This Page