*Even after resizing WinRE to 2GB*, KB5034439 fails on Server 2022 *Core* with error 0x8024200B

Anonymous
2024-01-12T08:29:38+00:00

Hello! We've now used the instructions at KB5028997: Instructions to manually resize your partition to install the WinRE update - Microsoft Support several times to solve the issue of KB5034439 failing to install. However, on Server 2022 Core, it still fails, even if the WinRE partition is resized to 2GB. The error message is different, though: "Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5034439)."

We've also tried disabling WinRE and removing the WinRE partition, but KB5034439 still shows up as an applicable security update.

How do we get this to install? Alternatively, how do we get it to stop showing as an applicable install if WinRE isn't present?

Thank you!

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

30 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-25T14:42:15+00:00

    @Radovan Drabik I may need to start doing this in our environment. Can anyone confirm that the only thing this update does is monkey around with the WinRE partition?

    Thanks

    0 comments No comments
  2. Anonymous
    2024-04-17T18:25:14+00:00

    Unfortunately this CAB fix can't be used on Windows Server core. No way to run it.

    0 comments No comments
  3. Anonymous
    2024-04-18T08:44:43+00:00

    The wushowhide.diagcab runs off a set of Powershell scripts that can still be run in the Powershell command line environment successfully (no GUI) without extra dependencies (even if they are called). I ran and tested it on Windows Core 2022 without modifying the scripts. All you need to do is unpack the cabinet file (Ex. wushowhide.zip [pcdust.com]) and execute it in the following manner to hide and unhide updates without errors. So the below guidance should give you enough information to hide and unhide any pending updates. To isolate and simplify things, I had the files mounted on a thumb drive in a wushowhide folder.

    Image

    0 comments No comments
  4. Anonymous
    2024-04-18T09:03:50+00:00

    Doh - of course I knew CAB files were zip files! Thanks, I'll give that a go.

    0 comments No comments
  5. Anonymous
    2024-03-25T15:35:04+00:00

    I followed these steps to hide the update K5034439:
    https://www.sysnative.com/forums/threads/issues-with-kb5034439-on-windows-server-2022-this-is-how-you-can-temporarily-hide-this-update.39739/

    You can temporarily hide this update with the following Microsoft tool (This tool can also be used to unhide this update).

    Note: If KB5034439 is offered again after it was set to hidden, then unhide this update and restart the server. Then attempt to update again and perform the following steps immediately after the installation of KB5034439 failed again.

    Download

    wushowhide.diagcab to hide an update.

    • Double click on the wushowhide.diagcab file and press Next.
    • Now the tool will search for updates and performs a scan to detect problems.
    • When this process is complete click on Hide updates.
    • Now an overview will appear with updates that have not yet been installed.
    • Select KB5034439and press Next.
    • When the troubleshooting has complete you can close the tool.

    This all worked and the failed update disappeared. But I did have a couple systems fail this update again this month even after suppression last month, as mentioned above. I am not running core but the tool will still prob work if launched from command prompt.

    I am not sure what all the update does. Would be nice to get some sort of feedback from Microsoft on this. Supposedly it was fixed in a later update but my servers are still wanting to apply this one.

    0 comments No comments