KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 Win Update

tecknot said:

I have a unique problem.

If anyone can point me to a solution to get my partition enabled, I would greatly appreciate it.

tecknot

Many points to consider.
You run WIN 10 & WIN 11 on the same disk and you have 2 EFI-Partitions. Is the one in Partition 6 active and for WIN 11?
"The Windows RE image was not found." Do you know where it is and can you find it?
If you know where it is, follow steps in post 174. Change numbers and letters accordingly.
It is possible to have 1 Recovery Environment for 2 Operating systems. For that you have to use bcdedit commands.

Is there anybody who can see a sense in @AK6DN 's reply?

The problem with using the Minitool Partition Wizard solution is the location of my existing recovery partition on my system drive. As you can see it's the very first partition on my drive and not the fourth partition which would put it right after my Windows 10 C: partition. Where it is currently located there is no way I can expand it's size! I have no idea why it's in that position other than something I read about very early installations of Windows 10 putting the recovery partition in that spot buy default. I'm assuming later windows installation media changed that location to after the system C: partition. I thought about shifting all the partitions to the right into the unallocated space at the end of my drive to allow me to increase the size of my position one recovery partition but there was this one strange partition that I couldn't move with the Minitool software. In fact this partition only showed up in the Minitool program and was invisible when using the Disk Manager program. I wasn't comfortable trying the Microsoft solution because again it looked to me like that solution was assuming the position of the Recovery partition to be located immediately after the Windows 10 C: partition. Luckily I came across another solution located here Create recovery partition in Windows 10/11 UEFI - YouTube . This solution allowed me to extract information from my existing recovery partition that I could then use to convert a normal partition, which I could create anywhere and any size in any free space available, into a recovery partition and then completely delete the old recovery partition. This is what I needed, a way of creating a somewhat larger recovery partition in the free space immediately after my Windows 10 C; partition. I choose a partition size of 1024 MB for my new Recovery Partition. As my old original recovery partition couldn't be moved or expanded this was a way to recreate a brand new larger recovery partition in a new location. Unfortunately the solution again relies on command line instructions like Microsoft's solution but at least unlike Microsoft's solution the purpose of the commands is clearly explained. It's probably a good idea though to make a full system backup image of your drive just incase the unthinkable happens. There was one small glitch in the procedure that created a small issue for me. When you create your normal partition don't assign it a drive letter otherwise it appears as a drive in the Windows file Explorer. Microsoft claims in their procedure that you give the recovery partition the name "Windows RE tools" but I left this blank as well and it didn't seem to hurt anything. After completing this procedure I was successfully able to install the Windows update. It only took up 524 MB of the 1024MB on my new recovery partition. Just a little too large for my original 500 MB recovery partition. Below is what my system drive partitions looked like after completing this procedure. Hopefully this helps someone else who has a recovery partition location similar to mine just in case the Microsoft fix doesn't arrive.

I've just caught up on the last few days of posts on here & Wilders, & read that this update has been pulled (finally). So I unhid it, & then ran WU, & sure enough it was offered again. It obviously still fails. I'm running Win 10 home, so I don't need it.

Strange that it has been pulled for some & not others.

It is still showing with an error in WU on my work machine, but at least on that one WU has stopped re-trying to install it automatically. Last time it tried was 2 days ago. Can't hide it on that one as I don't have the required privileges. (Actually our IT dept may have disabled it back end).

Going to re-hide it on my own laptop though. Won't bother unhiding it on the other 2 home laptops it also failed on.

@Andy Roid

Just rightclick on (C:) and shrink your C-Partition. That is too big!
After reagentc /disable
you can delete the existing Recovery Partition.
Then create the new one.
Exchange the WinRE. wim with a new WinRE. from an ISO.

catspyjamas said:

I've just caught up on the last few days of posts on here & Wilders, & read that this update has been pulled (finally). So I unhid it, & then ran WU, & sure enough it was offered again. It obviously still fails. I'm running Win 10 home, so I don't need it.

Strange that it has been pulled for some & not others.

It is still showing with an error in WU on my work machine, but at least on that one WU has stopped re-trying to install it automatically. Last time it tried was 2 days ago. Can't hide it on that one as I don't have the required privileges. (Actually our IT dept may have disabled it back end).

Going to re-hide it on my own laptop though. Won't bother unhiding it on the other 2 home laptops it also failed on.

yes i never hidden it i even asked my brother if he hid it yesterday didn't despite i download the show hide tool on 11th but like i said yes it been pull on my machine however if i look at windows update history it will say that it failed this past sun very odd

i restarted computer so basically in a nutshell since it's not there since yesterday not saying error failed to install retry anymore computer up to date

In some further detective work around the net it seems it is only being offered if you run WU manually. If you let it automatically check for updates it will not be re-offered (once the error has disappeared off WU, which it apparently it may do after a time - I did observe that on one of my own before I hid it to stop it coming back).

So it's become one of those updates you'll get if you seek it but you won't if you don't. Still gonna keep it hidden, as I like checking for updates. Part of my morning PC housework.

@Ivan Petrov
Powershell:
PS C:\WINDOWS\system32> Get-Hotfix
and check if Security Update KB5034441 is installed or not

Struggling10 said:

First “reagentc /info” didn’t show disabled but also didn't show any files, just listed possible switch commands. So I did “reagentc /enable” and “reagentc /info” again and files did show (see below)

C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 35a1c40f-476c-11eb-98f6-8871ce2ad6e1
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.


C:\Windows\system32>

But after calling up disk management, recovery partition still showed 100% free, not sure if it should show anything there like other partitions. But just for experiment I’ll try MS backup again with FireFox open.

Disk Management does not give you the proper value. I had the same issue. You need to use MiniTool Partition Wizard to get how much is in the partition.

JohnD