Update KB5034441 fails to install

Anonymous
2024-01-14T12:58:19+00:00

So the other topic about this was lokced for who knows what reason, why lock a topic / problem that has not been resolved yet?

I keep getting notification every day about this update and as you know we cannot install it because of some problem. What I read in the other locked topic is that the update is something for bitlocker, I dont use bitlocker so do I need it? Also is there a way to set windows to ignore this update and stop reminding me about it ?

MS needs to fix this and not have people doing all kinds of risky steps in order to fix it. Most people wont know what to do when they see that the update can't be installed, many are not that good with technical windows stuff. So if anyone can tell me a way to tell windows to ignore this update thx.

EDIT: I just saw a video where they explained how to hide it using a tool from MS called WUShowHide, isnt there a way to hide it directly in windows without the need of downloading this tool?

Windows for home | Windows 10 | Windows update

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.

0 comments No comments
Answer accepted by question author
Ramesh 181.2K Reputation points Volunteer Moderator
2024-01-14T13:15:28+00:00

Hi Salvida,

From Windows 10, version 22H2 | Microsoft Learn

Issue details January 2024

The January 2024 Windows RE update might fail to install

Status Originating update History

Resolved N/A

KB5034441

2024-01-09 Resolved: 2024-04-30, 14:07 PT

Opened: 2024-01-12, 14:10 PT

Devices attempting to install the January 2024 Windows Recovery Environment update (KB5034441) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.

Resulting from this error, the following message might be displayed.

"0x80070643 - ERROR_INSTALL_FAILURE"

Important: If your Windows device does not have a recovery environment configured, you do not need this update (KB5034441). In this case, the error can be ignored.

To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:

Open a Command Prompt window (cmd) as admin.

To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".

Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.

The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action. For guidance on making this change, review the following resources:

A code script can be used to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE. See Extend the Windows RE Partition.

Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.

Completion of these manual steps will allow the installation of this update to succeed.

Affected platforms:

Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2

Server: Windows Server 2022

******************************************************************************************************

If you don't have WinRE enabled and don't plan to use it, you may simply hide the KB5034441 update using the WUShowHide.diagcab tool.

The tool can be downloaded from the following link:

https://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

Select the KB5034441 update and hide it.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

574 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-05-12T04:27:05+00:00

    In trying to install Widows 10, it didn't work.... "We couldn't install Windows 10 0x80070570-0x2000D"

    I tried again, this time choosing not to install updates during the repair, and it seems to have worked...... System restore is back and I can create restore points

    After updating and checking in view update history, it appears that that the dreaded update KB 5034441 has installed, but when I go to "Check for updates" it shows "Updates available" and the same KB 5034441 update "Status: installing 0%" Is it repaired or not ? ? ?

    At least I have system restore back and it seems to be working as I have managed to create two restore points.

    Once again, thanks for your perspectives and guidance.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-12T02:52:42+00:00

    Well I have the Recovery Environment's partition set to 508MB and got the error so what do I do?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-05-11T09:16:12+00:00

    Thank you ascidian99, having tried to run system restore and being told there are no restore points, then trying to create a restore point with the message "writer experienced a transient error (0x8004233F3), I turned off system restore, rebooted and tried again (with 232 GB space on the drive for system restore)...... without success. Using command prompt as administrator, I then ran... "sfc /SCANNOW" (to scan and repair) and the scan found and repaired corrupt files. Following a reboot, another attempt to create a restore point has resulted in the same transient error (0x800423F3), so no further forward. Once again thank you for your efforts and good wishes, Peter

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-05-11T09:08:49+00:00

    thanks!!!

    Was this answer helpful?

    0 comments No comments