• DanM

    DanM

    @danm

    Viewing 8 replies - 1 through 8 (of 8 total)
    Author
    Replies
    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2531013

      Bad Board —  ASRock Z370 Pro4 OEM.

      Never did get an answer from ASRock on whether the board is the cause of the Windows Update problem.

      Fatal symptoms: after updating BIOS to the latest version, the board could not locate the Windows OS using BIOS Optimal Defaults, which it could do prior to the BIOS update.  But it would boot properly by setting SATA mode to AHCI, and disabling CSM.

       

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2530096

      I have checked the WMI registry, and it is good.

      By the way, I previously had some problems with this registry, but with help from support at Yamicsoft  it was resolved.

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2530094

      I have after some delay updated the BIOS on my ASRock Z370 Pro4OEM board to the latest OEM BIOS.  (Not as smooth as I had expected, with some odd surprises, but it is done and working.)

      Then I looked to retry KB5021233 but it is no longer available.  I proceeded with the current updates, and now I get the same error code 0x800f0922 for KB5022282.  I can only presume that this later package is actually failing for the same reason as the former, and on the same task.

      It remains likely that the Secure Boot portion of the BIOS is the area of concern.  I am still in contact with the excellent service at ASRock, and I will update again with any further results.

      Thank you to all those who offered suggestions.  All very helpful and thoughtful replies!

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2515370

      Bios L0.01  Very suspicious version number on an OEM board, not noted on the Asrock downloads page.  Asrock said to update to latest version.

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2515369

      See post below.  Asrock indicated possible BIOS issue causing the update to fail.

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2515368

      Thanks for the tip.  I will look into the Edge question.

      In the meantime, I I have contacted Asrock re. possible BIOS issues  on my Z370 Pro4 board.  They indicated it was likely there was a BIOS issue, given I have an OEM board with an unusual version.  I suspect the problem is in BIOS secure boot code, as others here have mentioned.  I am waiting for an appropriate time to update to the latest.

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2511074

      Mike: thanks for the tip.

      Secure Boot was disabled during previous tries. So I enabled it, installed default keys and set other defaults, but the update still failed.

      I have subsequently written to Asrock to inquire. From what I read in the device forums, it is possible that my UEFI is out of date but we shall see.

    • in reply to: Win 10 22H2 update KB5021233 install fails with 0x800f0922 #2510812

      Thank you to those who suggested I look at the BSOD thread! Interesting information. Fortunately I do not have the offending extra hidparse.sys file loose in \System32\.
      But it is in \System32\DriverStore\
      and four places in WinSxS\
      and two places in \servicing\LCU_Package
      I kind of doubt that is the reason for my installation error.

      The error itself is puzzling: 0x800f0922 People have over years reported various causes for this error in installing the update. The most common is that it identifies a download error, but in my case the package does seem to download correctly and fails near the end of the installation script. Less commonly, people have suggested DISM errors (none found), Insufficient space in the 500mb reserved partition (nope, at 58% after downloading), system update data (nope, I reset it), BIOS (not convincing), out of date .NET (nope, latest version as of 12/22/22, from manual download), VPN or Firewall (nope, install fails after restart apparently before loading these, besides which I tried it with these disabled).

    Viewing 8 replies - 1 through 8 (of 8 total)