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.1K 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: Newest
  1. Anonymous
    2024-01-24T07:11:43+00:00

    Thanks for the info. I had no idea because usually I get updates and there is not much of a problem. I am running 500/500Mb/s internet and I had trouble when that update appeared to not update going from one website to another or back to update/security section. I read about the update and there are a half a dozen problems that could arise. One being run the troubleshooter and it pointed out for me to re-start. Going there 5 times a day now in hope the 4441 update would either finally disappear or fixed. Then the sitting for 30+ minutes after restart and read that to just wait instead of powering off. Until last year I have never done a scf scannow after some blue screen problems and also running a program to fix it. One was with RAM problems. One of the programs took over an hour. So after the blue screen problems which seemed to have been repaired we get the 4441 that won't update along with all the fixes some have touted that do not work (YT).

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-01-24T05:47:28+00:00

    About the KB 5034203, which goes to 100%... And then seems to start again, and stops at 20%. It has always been like that with this update just let it run... And it will continue updating after some minutes, and require restart. I have never had problem with this update.

    I always let the other updates get installed before hitting the Restart now-button.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-24T05:32:34+00:00

    As if Microsoft Windows 10 users need more problems on updates. Today there were two other updates. Kb5034582 update which stated to re-start your PC. I did and it came up okay. Then kb5034203 was ready to update to PC. It started slow and stopped then went to 100% but would not complete. Reading about it's problems from MS. One was to run the troubleshooter for updates. Did that and it stated to restart PC again. Closed everything and pwr re-start. I had the Do not shut down PC your windows updates. This went on for 30 minutes and I read the number one thing to do is wait. I did and finally re-booted. So now we have another update after the 4441 one that has failed and remains so. I can only say when you have a update not updating but trying to it slows down your processes. It needs to be fixed and other updates need to be tested for problems. MS states there is a fix but I can tell you for sure that 90% have no idea nor want to do this step that could wreck your PC even more. I can do the sfc scannow and others where you only have to let it run check for problems and fixes. Not even doing this partition that many have stated does not work. It has been 2 weeks and yet no fixes for a update that won't update. Then to have another that won't load until it is troubleshot and fixed. Users just want to use their PC without problems not caused by PC ,that uploaders do. First is run troubleshooters which can not even see this problem let alone tell you how to fix it. Then SFC and others that DO NOT WORK.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-23T21:52:40+00:00

    I can tell you guys right now what is going wrong, and it has annoyed me for the longest time. Because the drive our operating system is on is not disk 0, this update keeps failing. This nonsensical system of letting the motherboard choose the disk number, and it always choosing SSDs plugged into the SATA ports as the first numbers is so annoying, especially when most people put their operating systems on the faster NVME drives, but these drive slots never get designated as disk0 on the system.

    So this particular update keeps trying to look for a Windows Recovery Environment on disk 0, and keeps failing to find one if people have Windows installed on their NVME drives which never get labelled as disk 0, so the update just simply fails every time.

    If you tell the update to stop trying to look for Windows Recovery Environment ONLY on disk 0, maybe the update will finally work.

    Was this answer helpful?

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