KB…441 tragedy for non Woody users

Topic

New Reply

I hate to criticize Microsoft because MS really has an amazing system. However, why do you keep sending out KB..441 when you are not going to fix it and it is broken?

Do you know what that does to the average home user that does not use Woody for help?

Just to see, I purposely did not block 441 as Susan suggested. So for the last several months it is offered, and everything seems normal until I notice my status of “Downloading” is not really downloading after 30 minutes. KB441 secretly hangs the system. Being an astute Woody user I know at that point to do a restart (an irritating delay) that kicks the update working again. This month a Windows Malware update then got hung so another restart was required (more irritation).

The problem is the unknowing home user probably does not realize the system is hung and waits for hours for the update to complete – if it even does. They then probably have to call a help service. This is a tragedy for these people.

Microsoft, do the right thing and either fix KB441 or stop sending it out as an update!!

2 users thanked author for this post.

SupremeLaW, Cybertooth

Reply | Quote

Replies

1.  Hmmm, do you think the “…unknowing home user…” has given up and decided to ditch Win 10 and purchase a Win11 device? Sharp way to force upgrade of hardware and O/S.
2. I used a method described on this site to expand the recovery partition. However how can I be sure that it contains a valid ‘image’ to recover the O/S and if it doesn’t how can I populate the partition?

1 user thanked author for this post.

J9438

Reply | Quote

Months ago, following AskWoody advice, I used WUSHOWHIDE to hide KB…441. Problem solved.

Well, no. About a month later, MS again pushed KB…441 onto my update list despite my having rejected it. So again, hide the beast. Done.

Well, no. A few days ago KB…441 appeared again on the list of updates that failed to complete.

Made a third attempt to hide KB…441. Any bets this time hiding will have a permanent effect?

 

1 user thanked author for this post.

J9438

Reply | Quote

I use WuMgr and hid KB….441 when it first appeared.  It has remained hidden and is not being pushed with Windows Update.

https://github.com/DavidXanatos/wumgr

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

3 users thanked author for this post.

J9438, lmacri, Alex5723

Reply | Quote

MikeAL8 wrote:

unknowing home user…” has given up and decided to ditch Win 10 and purchase a Win11 device?

There is no difference between Win 10 and 11.

1 user thanked author for this post.

J9438

Reply | Quote

Alex5723 wrote:

There is no difference between Win 10 and 11.

The KB5034441 January 2024 WinRE update for Windows 10 only applies to Win 10 v21H2 and Win 10 v22H2.

The equivalent KB5034440 January 2024 WinRE update for Windows 11 only applies to the outdated Win 11 v21H2. AFAIK you will not be offered one of these problematic January 2024 WinRE updates if you use Win 11 v22H2 or Win 11 v23H2.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

J9438

Reply | Quote

I know this may sound like a stupid suggestion, but I cannot tell you how many times I have kicked off updates of various kinds and the first status I get is “checking system for ….”.

Would it be so terribly hard to put some code up front in KB441 to check the size of the recovery partition and then either advise “recovery partition too small” and exit without hanging up the whole system or “recovery partition too small do you want update to expand it -yes, no”. (I don’t know if it can be expanded by the system but I would think some complex code could at least try and either succeed or do a clean exit if not possible).

But then again, that should only be a temporary solution until MS comes up with a permanent solution because we don’t want KB441 presenting “forever”.

1 user thanked author for this post.

Cybertooth

Reply | Quote

The solution I applied was mentioned by @krcportero in a post of June 18^th 2024 and subsequent links and I eventually followed the instructions under paragraph “Fix 0x80070643 error in windows 10”

This certainly appears to have increased the Recovery Partion size.

What does concern me is a lack of evidence that the partition contans a vaild Windows 10 Pro Recovery image and do not wish to start an experimental recovery in case things turn out bad !

Does the Win 10 recovery processes give a warnings before it starts and allowing an abort if the recovery image is invalid?

Meanwhile I’ll stagger on with W10 for anoth year.

Link to krcportero’s post:  #2681748

 

Reply | Quote

MikeAL8 wrote:

What does concern me is a lack of evidence that the partition contans a vaild Windows 10 Pro Recovery image

Hi MikeAL8:

Run the command reagentc /info in an elevated command prompt with Administrator rights to check the status of your Windows Recovery Environment (WinRE). I also posted additional fsutil and Dism commands in my 04-Jul-2024 post # 2685481 in Susan Bradley’s KB5034441 has led us astray, in a horrible way that you can run to check other WinRE attributes.

If reagentc /info shows your WinRE partition is located somewhere other than Disk 0 / Partition 3 then you will have to modify my sample fsutil and Dism commands. For example, that reagentc /info command my own WinRE is enabled and located on Disk 0 / Partition 4.

If those reagentc, fsutil and Dism commands run correctly and show your Windows Recovery Environment (WinRE) is enabled then this would not guarantee an actual recovery would run correctly, but this should give you some confidence that your WinRE image file (winre.wim) is present and valid.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

MikeAL8

Reply | Quote

@lmacri

Thanks – I’ll try your sugestions.

If all else fails I fall back on Macrium Reflect Free  Fingers  x’d I’ll not need Sys Restore.

Reply | Quote

why not simply hold shift while choosing Restart? It will boot into RE. Go a few layers in, and then just back out.

Reply | Quote

a wrote:

why not simply hold shift while choosing Restart? It will boot into RE. Go a few layers in, and then just back out.

Hi krism:

Perhaps I misunderstood. MikeALB said in post # 2685944 that they “do not wish to start an experimental recovery in case things turn out bad“. I assumed that meant they wanted to check their WinRE image without actually entering the recovery environment.

There are a few simple tasks MikeALB could run from the initial WinRE menu options (e.g., opening a command prompt from Troubleshoot | Command Prompt – see the MS Tech Community blog Windows Recovery Environment Explained for an overview) before backing out but I’ll leave it to MikeALB to decide how far they want to take their testing.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

Reply | Quote

reagentc /info will only tell you if the pointer is there. Doing what I suggested will actually go to the RE partition and show you a few layers of the options without actually doing anything, unless, of course, you tell it to restart and hit enter. Note, it will NOT tell you which partition it is using so don’t go deleting partitions unless you have a recent image. Also note that if you delete a partition and have linux partitions above it, grub will not find them and you will have to do some mickey mouse.

 

note – I have 2 recovery partitions above C: 4 and 5. reagentc /info says 4 but 5 is the one that I expanded to 3GB to allow that KB to run successfully. I could delete 5 but then I would have to waste a bit of time getting linux to run and I am, above all, lazy.

Reply | Quote

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"WinREVersion"="10.0.19041.9999"

add this registry value and the update will vanish (system restart or WU rescan needed)

Reply | Quote

We enter that value as a new “String Value” (that later shows up as the type “REG_SZ”), correct?

Reply | Quote

Yes

1 user thanked author for this post.

Bob99

Reply | Quote

abbodi86 wrote:

add this registry value and the update will vanish

Hi abbodi86:

The attached  screenshot shows my winre.wim image was updated to Version 10.0.19041 Build 3920 after the January 2024 KB5034441 WinRE update was installed on my Win 10 machine (see post # 2685481 for the Dism command used). Note that Windows Update successfully installed KB5034441 even though my WinRE partition did not have the recommended 250 MB of free disk space.

If users apply your registry edit and manually change their WinRE version to a high number like 10.0.19041.9999 does that mean any future security update released for WinRE will not be offered to their machine? I’m guessing your workaround is not specific to KB5034441.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

Reply | Quote

Yes, all future KB5034441-alike updates would be supressed
it’s just a workaround if it fails installation

Reply | Quote

I installed KB 5034441 in Jan 2024 with no problems and I have a small (120 GB) C: drive.
The Windows RE partition after the update is only 980 MB in size (that’s less than 1 /120th of the drive – 0.8%). Just how small is the Windows RE partition on these systems that fail to run this update or what percentage of the drive does it need to be?

As far as checking the recovery files:

You can review your Backup images and Restore points to make sure they are there by:
Entering rstrui in Run box, press Enter to open System Restore Window. Press Next to go to the next page. Click box next to Show more restore points (and image backups). Click the Cancel button after viewing and NO recovery action is started and NO changes will be made.

Another more in depth check of an image backup file for recovery is to see how large the backup image is compared to the Windows drive it is an image of. When a Backup image fails it will be a significantly smaller in size than the size of the drive it is an image of (unless you use compression). Images of the Windows drive made by Windows will be where you selected to store the images in a folder named WindowsImageBackup. The size of the backup should be with 10% the size of the drive it is a backup of.

There is no way to view the restore points without some serious folder access changes (kept in the System Volume Information folder); however you can view the specifics of them as well as how much space they take with the following commands in an Administrator Command window:

vssadmin list shadows (has info on all restore points and backup copies for all drives)

vssadmin list shadowstorage (has info for allocated and used storage space for restore points for each drive)

HTH, Dana:))

Reply | Quote

lmacri wrote:

If users apply your registry edit and manually change their WinRE version to a high number like 10.0.19041.9999 does that mean any future security update released for WinRE will not be offered to their machine? I’m guessing your workaround is not specific to KB5034441.

My Windows 10 Home updated without any problems and yielded the following WinRE version number: 10.0.19041.3920.
Maybe changing that Registry value to that version number will prevent KB50334441 from installing as “seeing” that version already installed and yet leave the door open for future versions to update.

HTH, Dana:))

Reply | Quote

KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024

IMPORTANT This update is not needed and will not be offered if your Windows Recovery Environment (WinRE) meets any of the following conditions (This is a lie) :

If the WinRE recovery partition does not have sufficient free space.

If the WinRE recovery partition was manually updated by using the procedure in Add an update package to Windows RE and is already up to date.

If the WinRE image has a version greater than or equal to version 10.0.19041.3920. To determine the version of your WinRE image, check the WinREVersion registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion.

If your running PC does not have a WinRE recovery partition. To verify if you have WinRE enabled, run the following command in an elevated command prompt: reagentc /info. If WinRE is enabled, you will see Windows RE status in the output with a value of Enabled. In this scenario, this update might be needed…

NOTE This update requires 250 MB of free space in the recovery partition to install successfully…

KB5034440: Windows Recovery Environment update for Windows 11, version 21H2: January 9, 2024

2 users thanked author for this post.

J9438, lmacri

Reply | Quote

Alex5723 wrote:

IMPORTANT This update is not needed and will not be offered if your Windows Recovery Environment (WinRE) meets any of the following conditions (This is a lie) :

Hi Alex5723:

Thanks for the heads up.

Those release notes were just modified yesterday (09-Jul-2024). When you say the information in those release notes is a lie, does that mean you ran Windows Update after 08-Jul-2024 on a machine with a WinRE recovery partition that had less than 250 MB of free disk space,  and that KB5034440 (Win 11 v21H2 only) or KB5034441 (Win 10 v21H2 or v22H2 only) was still offered and failed to install?

I can’t test because KB5034441 installed successfully on my Win 10 Pro v22H2 machine back in January 2024.

EDIT:

See today’s 10-Jul-2024 Neowin article Microsoft posts requirements for KB5034441/KB5034440 updates that cause “0x80070643” error for further information on the recent edits made to the release notes for these Jan 2024 WinRE updates.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v128.0.0 * Microsoft Defender v4.18.24050.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

J9438, Alex5723

Reply | Quote

I may test that statement by unhiding KB5034441 later today.

Update : KB5034441 is not listed as hidden in WUmgr any more.

1 user thanked author for this post.

J9438

Reply | Quote

strange

I checked registry key
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion”
on my dad’s old Toshiba laptop and I get this:

“WinREVersion”=”10.0.19041.4529”

that’s right – 4529

perhaps I re-installed Windows 10 via in-place upgrade using an updated June 2024 ISO image which probably had most of the June 2024 updates integrated into the ISO (including the WinRE update).

KB5034441 is no longer offered thru WU for me.

1 user thanked author for this post.

abbodi86

Reply | Quote

attached is the pic of the WinREVersion reg entry in RegEdit set to version 10.0.19041.4529 as proof:

re-installed Win10 22H2 home using the updated June 2024 Win10 (build 19045.4529) ISO install media, the kind that MVS/MSDN subscribers get each month.

edit – Microsoft should provide newer Win10 ISO install media that includes at least the KB5034232/KB5034441 WinRE update thru either the W10 Media Creation Tool or thru the Win10 download page (which both still offer the outdated 19045.3803 build from Dec. 2023), like the newer ones MVS/MSDN users get regularly.

Reply | Quote

EP wrote:

attached is the pic of the WinREVersion reg entry in RegEdit set to version 10.0.19041.4529 as proof:

Hi EP

I noticed your UBR (Update Build Revision) is 4598, which is the 25-Jun-2024 KB5039299 Preview build (OS Build 19045.4598). If you install the July 2024 Patch Tuesday updates I assume your UBR would change to 4651 (OS Build 19045.4651).

I installed the KB5034441 WinRE update back in Jan 2024 and my July 2024 Patch Tuesday aren’t scheduled to install until tomorrow morning, and here’s what I currently see in my Win 10 Pro v22H2 registry :

————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v128.0.0 * Microsoft Defender v4.18.24050.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

Reply | Quote

Alex5723 wrote:

I may test that statement by unhiding KB5034441 later today. Update : KB5034441 is not listed as hidden in WUmgr any more.

After reading that and @EP ‘s below that

KB5034441 is no longer offered thru WU for me.

I decided to look in wushowhide (after changing GP to zero days delay for Quality Updates) and voila, KB5034441 was gone from the list of hidden updates within wushohide!

I wonder if MS finally pulled it, lock, stock, and barrel??

1 user thanked author for this post.

Alex5723

Reply | Quote

https://support.microsoft.com/help/5034441

see the IMPORTANT note, the update won’t be offered for all anymore, only if it can be successfully installed

4 users thanked author for this post.

J9438, Cybertooth, Alex5723, PKCano

Reply | Quote

Alex5723 wrote:

Update : KB5034441 is not listed as hidden in WUmgr any more.

Update : KB5034441 is (re)listed as hidden in WUmgr

Reply | Quote

abbodi86 wrote:

see the IMPORTANT note, the update won’t be offered for all anymore, only if it can be successfully installed

See, reporting issues to Woody makes a difference.

Thank you, Woody, for bringing this to Microsoft’s attention.

Thank you, Microsoft, for following Woody users and solving our issues.

Reply | Quote

I have had KB 5034441 hidden via winshowhide since Dec/Jan? It is suddenly gone as of from winshohide as of July 11 ( as per @Alex5723) and to this day. Never installed.
I have been following all the threads. I recall in Jan I had 480 of 500 Healthy Recovery partition as per disk mgnt.

I looked at this thread, both @EP and @Imacri  pics above, and mine does not show WINRE via regedit (Admin)? – yet It shows with the commands?
Do I really have a winre (recovery partition) or not? (And note the age/build of WinRE via command prompts – anyone know have an inkling of what is going on?) No July updates applied yet.

FWIW: UEfi, secure boot on, Tpm 1.2, no bitlocker etc

Reply | Quote

Deo wrote:

Do I really have a winre (recovery partition) or not?

Your reagentc screenshot clearly shows you do have a winre recovery partition located on disk 0, partition 4.

However, your DISM screenshot shows it’s Service Pack Build: 3562 not the new 3920 update that was included in KB5034441.

If you still want to update it now that KB5034441 is no longer being offered, visit Microsoft’s KB5034957: Updating the WinRE partition on deployed devices to address security vulnerabilities in CVE-2024-20666 page for a PowerShell script and instructions on how to manually update WinRE.

BTW, I used that script to update on of my two Windows 10 22H2 PC’s and it works without needing to increase the size of the recovery partition!

1 user thanked author for this post.

Deo

Reply | Quote

Noads quote ” …If you still want to update…” (Tried to quote semi post/wouldn’t??)
Is it odd that I have no WINRE in my registry, or is that that a norm or any harm in having it not show in regedit??

n0ads wrote:

update on of my two

Thus is it necessary to do the PS script?

If so, I will search for how to implement a script, as the MS site isn’t clear. ie. copy whole script into notepad and then copy into powershell? Even if it says it’s for windows 11 as well as my Win 10?

Seems I DO have a WINRE, just not showing up in regedit for some reason. Hmm.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

This script is for Windows 10, version 2004 and later versions, including Windows 11.

So yes, the script works for ALL versions of Windows newer than Windows 10 2004.

Deo wrote:

the MS site isn’t clear. ie. copy whole script into notepad and then copy into powershell?

Copy the script into notepad and then save it to a known location on your PC with a file name that ends in .ps1.

• Attached is the copy of PatchWinREScript_2004plus.ps1 that I used in zipped format.

Then you must download the correct Safe OS update from the Microsoft catalog and save it in the same location.

• If you’re running Windows 10 22H2 x64, it’ll be KB5034232

Start a Powershell prompt in Admin mode (i.e. Run as Admin), CD to the location containing both files, and then run the following command:

.\Name-of-your-powershell-script.ps1 -packagePath "name-of-the-Safe-OS-update-you-downloaded.cab"

Note: if you use my attached script and downloaded the above Windows 10 22H2 x64 Safe OS update, the command will be:

.\PatchWinREScript_2004plus.ps1 -packagePath "windows10.0-kb5034232-x64_ff4651e9e031bad04f7fa645dc3dee1fe1435f38.cab"

Reply | Quote

Your “disk 0” (disk zero) layout in Disk Management is typical:

|   System Reserved  |  C: system software  |  WinPE partition  |

FYI:  “509 MB” appears to be the default size for the WinPE partition, i.e. the one that needs to be larger for THE PROBLEM Windows Update to install correctly without error(s).

The Chris Waite procedure at YT should work for you.

Bear in mind that his procedure “shrinks” C: by a smaller amount.

We used Partition Wizard to “shrink” our C: system partition.

Visually, your C: system software partition simply needs to “shrink” by about 1 GB (a generous amount that we know works).

Then, your WinPE can be enlarged to 1,509 MB.

Then, try Windows Update.

Hope this helps.

Reply | Quote

lmacri wrote:

EP wrote:

attached is the pic of the WinREVersion reg entry in RegEdit set to version 10.0.19041.4529 as proof:

Hi EP

I noticed your UBR (Update Build Revision) is 4598, which is the 25-Jun-2024 KB5039299 Preview build (OS Build 19045.4598). If you install the July 2024 Patch Tuesday updates I assume your UBR would change to 4651 (OS Build 19045.4651).

I installed the KB5034441 WinRE update back in Jan 2024 and my July 2024 Patch Tuesday aren’t scheduled to install until tomorrow morning, and here’s what I currently see in my Win 10 Pro v22H2 registry :

————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v128.0.0 * Microsoft Defender v4.18.24050.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783

but I have currently NOT installed the July 2024 update (KB5040427), Imacri

skipping it in favor of the upcoming late July preview patch [KB5040525]

Reply | Quote

We succeeded by following the relatively simple procedure demonstrated by Chris Waite in this YT video:

https://www.youtube.com/watch?v=t-8gFRrEiCU&t=938s

We tried his sequence using 2 different approaches:

(1)  we created UNALLOCATED space to the left of the WinPE partition, using the Partition Wizard software;  new size of the WinPE partition is 1,509 Megabytes

(2) we tried to create the same UNALLOCATED space using the SHRINK option in Disk Management, but the Chris Waite procedure did NOT work with this approach.

After succeeding with (1), Windows Updates installed AOK with no apparent errors.

 

As such, THE PROBLEM results from a WinPE partition that needs to be larger for THE PROBLEM update to install correctly without any error message(s).

 

p.s.  I should add that our NTFS partitions are all MBR, because we recently upgraded an aging XP PC with Windows 10 x64 that we purchased from Newegg on a 21H2 OEM DVD.  Reportedly, MBR drives support a maximum of 4 discrete NTFS partitions.

Hope this helps.

 

Reply | Quote

skipping it in favor of the upcoming late July preview patch [KB5040525]

a follow up to my earlier post – the KB5040525 preview update was released on Tuesday afternoon a little after 2pm pacific local time as build 19045.4717

so the “UBR” value would have a build of 4717 after installing KB5040525 on one of my Win10 pcs

1 user thanked author for this post.

SupremeLaW

Reply | Quote

SupremeLaW wrote:

(1)  we created UNALLOCATED space to the left of the WinPE partition,

There is nothing to the left of WinRE partition on my laptop, so this solution doesn’t fit everyone.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

As far as I have been able to determine, THE PROBLEM is a WinPE partition that is simply too small for the PROBLEM UPDATE to install without failing.

Permit me to think out-loud …

Can you possibly post a screen shot of Disk Management?

It appears your “partition0” (partition zero) is the “System Reserved” partition.

Then, your “partition1” (partition one) is WinPE i.e. to the left of C: .

So, using process of elimination, I’m guessing that your “partition2” (partition two) is C: .

Capable software like Partition Wizard may work for you, as follows:

(1)  shrink C: by 1,500 Megabytes (1.5GB)

(2) make sure the freed space is recognized as “UNALLOCATED” by Disk Management and Partition Wizard

(3) copy your existing WinPE to that newly “UNALLOCATED” space, using all 1,500 MB

(4) delete the source WinPE (the one to the left of your C: system partition) and make sure it appears as “UNALLOCATED” to Partition Wizard and Disk Management

(5)  try Windows Update

(6)  if (5) fails, you can always reverse the above steps and copy your new WinPE back to its original location to the left of C: .

Hope this helps.

Reply | Quote

SupremeLaW wrote:

Can you possibly post a screen shot of Disk Management?

There is no “partition0”.
Partition 1 is WinRE
Partition 2 is EFI
Partition 3 is Reserved
Partition 4 in C:

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks for that screen shot:  this helps me visualize accurately your situation:

This is what I would try, if I were you and that layout of “Disk 1” were my PC:

Your WinRE partition needs to be enlarged, but withOUT making any changes whatsoever to your EFI and Reserved partitions.

My strong preference is to rely on Partition Wizard, because it has been so reliable for me for many years.  Even if you need to purchase a license, it’s WORTH IT!!

If you don’t want to purchase a license, contact that vendor and ask if their “free trial” version can be run to shrink C: and copy your WinRE partition to the UNFORMATTED space created by shrinking C: .

As such, here’s what I would do with my licensed copy of Partition Wizard:

(1)  shrink your C: system partition by at least 1,500 Megabytes (1.5 GB) i.e. 499MB+1,000MB ~= 1,500MB

(2) make sure the newly freed space is recognized as “UNFORMATTED”

(3) run Partition Wizard to copy the contents of your original WinRE partition to all of that UNFORMATTED space, so as to leave no more UNFORMATTED space there

(4)  make a backup copy of your original WinRE partition, just as a fail-safe e.g. in case you decide you need to “roll-back”

(5) delete the original 499MB WinRE partition, so that space is recognized as UNFORMATTED

(6) try Windows Update here, to test whether (or not) the failing Windows Update now finishes without error(s).

Hope this helps 

Reply | Quote

p.s.  I also remember finding HELP documentation at the Partition Wizard website.  That HELP documentation addresses specifically this problem of Windows Update failing because the WinRE partition is not large enough.

GOOD LUCK!

Reply | Quote

Google site:partitionwizard.com KB5034441

finds e.g.:

How to Increase Recovery Partition Size?  Here’s A Full Guide

https://www.partitionwizard.com/partitionmagic/increase-recovery-partition-size.html

see “Method 2.  Use MiniTool Partition Wizard”

2 users thanked author for this post.

Alex5723, Cybertooth

Reply | Quote

Thanks.
I find it too much hassle for something that doesn’t need updating as the chance of hacking (disabled or enabled) BitLocker is nil.

In my response I just wanted to point that not all PCs are equal.

1 user thanked author for this post.

SupremeLaW

Reply | Quote

Thanks.

Other people reading here might have the same partition layout.

It’s also valuable to learn about third-party utility software that works as advertised.

1 user thanked author for this post.

Alex5723

Reply | Quote

“KB..441” is back again today and blocked again today.

1 user thanked author for this post.

Deo

Reply | Quote