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

itsme1 said:

So it's good.

From the Windows disk manager I also have nothing, the recovery partition does not display any size used, except the size of the partition.

OK, thanks for your help. I'll try rebooting and then backup again with FixFox open, since I didn't reboot after enabling recovery environment before. Then I'll try the recovery options on restart as you mentioned just to see what I get, so will be off line for a while. Thanks Again

That's an issue with Disk Manager

Speccy will show it is not empty.

Yes speccy among others.

Pentagon said:

@Andy Roid

It has never been updated
Disk1 - Partition 5 is ok?

Well, so far I have installed all hotfixes, cumulative and feature updates without problems. So I have no idea why the image is that old.
And yes, partition 5 is correct:

Code:

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

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk1\partition5\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 6504e12f-0db1-11e9-9ba8-a20163185d75
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.


C:\WINDOWS\system32>

I have looked through update history again and there are no errors, up until now.

Pentagon said:

I would extrakt a new WinRE.wim from the last ISO and replace the old one.
If you have 7z it's easy, if you run 7z as Administrator. It's very easy, if you assign a drive letter to your Recovery Partition first
diskpart
sel disk 1
sel par 5
assign letter=R
exit

When the replacement of the WinRe.wim is ready, remove the drive letter:
mountvol R: /d

Thanks, I will have to resize the partition as well as it may be too small.



Disk0 contains Linux. There is also old recovery partition at the beginning of disk, and this indicates that windows updates created one at the end, meaning it must have been updated at some point.

kitpzyxmsir said:

I blocked it. When I posted, I mentioned I experienced numerous problems around the same time as the update. I can't say that the two incidents were related, but I wasn't taking any chances.

I can always unblock it. My question is, when an update is issued, will I be still be offered it, or will I have to unblock it?

Nobody knows. That's why I said don't hide it and just leave the error message alone.

I have a unique problem. I followed the steps for creating the partition for the WinRe update (KB5028997), except I did not resize my OS partition to make room for the update. Instead, I just deleted my Recovery partition. Otherwise, everything went well until I tried to enable my WinRE partition the partition was not found and it remained disabled. I tried to re-enable it, I got the same error again. Tried rebooting and still got the same.

See below for screenshots of my results:







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

Kind regards,

tecknot

tecknot said:

I have a unique problem. I followed the steps for creating the partition for the WinRe update (KB5028997), except I did not resize my OS partition to make room for the update. Instead, I just deleted my Recovery partition. Otherwise, everything went well until I tried to enable my WinRE partition the partition was not found and it remained disabled. I tried to re-enable it, I got the same error again. Tried rebooting and still got the same.

See below for screenshots of my results:

... elided ...

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

Kind regards,

tecknot

This is why I just blocked the update until MicroSoft gets their act together and figures this sh*t out. I don't use BitLocker so the update really is meaningless to me.