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

SIW2 said:

Has anybody tried

reagentc /disable
then mount winre.wim
use dism to install the cab
https://www.catalog.update.microsoft...px?q=Safe%20OS
unmount commit
reagentc /enable

could optimize/export the wim to make it a bit smaller if desired

the updated winre.wim might not be much bigger than the original. If it is too big, then use a 3rd party tool to expand the recov partition before reagentc /enable.

It seems quite sensible to have a big recov partition anyway, about 1gb perhaps to avoid faffling in future.

I've done it or something similar, described here KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 . I had enlarged the recovery partition to around 2 GB (I could have enlarged it to more than 100 GB w/o any drawback, as I'm using a 240 GB SSD with 160 GB free only for Windows, and I'm not planning to use that free space for a data partition or other OS), and had failed many attempts with KB5034441 with all kinds of methods. This worked well in the first attempt. I suppose my problem with this update wasn't about sizes of partitions.

Checkout this link.
https://learn.microsoft.com/en-us/wi...-image-version

I'm about to do a fresh install of W10 and I'm wondering if this partition size issue has been fixed in the iso I will be downloading...anyone know?

To me the solution was my "recovery partition was on disk 1 instead of disk 0" BUT winre.wim is set to index 0 meaning it always try to find recovery in disk 0 instead of disk 1, so what i did was i deleted the recovery partition on disk 1 using this How to Delete a Windows Recovery Partition and created the new recovery in disk 0 using this method.

Resizing the partition fixes it but the caveat is there is always risk. I used 2000 as the partition size instead of the 750 Microsoft suggests based on some people still getting a failure at that size. It has to do with free space available as the partition gets larger. More space is needed. You can try 750 and see how it works. Here is the set of instructions I am using on our computers. DO NOT MESS WITH THE SMALL SYSTEM PARTITION OR YOU WILL HOSE THE SYSTEM.

https://support.microsoft.com/en-us/...9-24c8229763bf

"Windows 10 Windows 10, version 1607, all editions Windows Server 2016, all editions Win 10 Ent LTSC 2019 Win 10 IoT Ent LTSC 2019 Windows 10 IoT Core 2019 LTSC Windows Server 2019 Windows 10 Enterprise and Education, version 21H2 Windows 10 IoT Enterprise, version 21H2 Windows 10 Enterprise Multi-Session, version 21H2 Windows 10, version 22H2, all editions Windows 11 version 21H2, all editions Windows 11 version 22H2, all editions Windows 11 version 23H2, all editions"

from KB Article

cmd (run as administrator)

reagentc /info there should be a “Windows RE location” with a path to the WinRE directory

reagentc /disable

diskpart

list disk

select disk<OS disk index> This should be the same disk index as WinRE.

list part

select part<OS partition index>

If WinRE partition is adjacent to the OS use shrink desired=250 minimum=250 (however use shrink desired=750 minimum=750 if WinRE partition is not adjacent to the OS partition, e.g., WinRe is partition1 instead of 4. I use shrink desired=2000 minimum=2000 instead of 750. If they are not adjacent you will end up with an unallocated small partition where WinRE used to be)

select part<WinRE partition index>

delete partition override

list disk. Check if there is an asterisk character (*) in the “Gpt” column. If there is an asterisk character (*), then the drive is GPT. Otherwise, the drive is MBR. If it is MBR then use the code in the article instead for MBR drives. All ours are GPT. This code below is for GPT

create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

gpt attributes =0x8000000000000001

format quick fs=ntfs label=”Windows RE tools”

list vol (visual check to see if it looks right)

exit

reagentc /enable

reagentc /info


you might need winre.wim from windows.iso