Unable to update (KB5034441) using below links

You're shrinking the wrong partition if you get this error. The instructions state that you must shrink the OS partition first, then delete the recovery partition, and finally create a new recovery partition of the previous size PLUS the size that you shrunk the OS partition by.

Honestly I'd rather not have to mess about with shrinking partitions etc at all. Are Microsoft going to create an update fix? It's been several weeks....

I'm also waiting for the fix. Just in case anyone from Microsoft can use the information, here's my experience in following the instructions to manually resize the WinRE partition:

1. on an old laptop running Win10 Pro and an AMD A8-5545 CPU, mechanical hard drive, the process worked perfectly.
2. on a desktop running Win10 Pro, a Core i5-7640X CPU and an SSD, I got the error message saying the system partition could not be shrunk -- even though there are hundreds of Gb unused on the drive. No joy.
3. on a laptop running Win10 Pro, a Core i5-4300U CPU and an SSD, initially the WinRE partition was 510Mb. I went through the process of shrinking the system partition, then deleting and re-creating the WinRE partition and got no error messages -- but the newly created WinRE partition was again 510Mb! The process had not used the newly freed space to create a larger WinRE partition. Since the table created by the "list partition" command only shows partition sizes in whole Mb or whole Gb, I cannot tell whether the system partition (100 Gb) really was shrunk by 250 Mb or not. After a reboot I tried the process a second time, same result. I have no idea why.

I've spent too much time on this already. Waiting for the fix.

BTW, I do use BitLocker to encrypt USB thumb drives, and then to read the encrypted thumb drive. Am I at risk until this gets fixed?

We automated this in our deployment console via powershell code and also a diskpart script executed via powershell. I noticed that alot of our systems we had to decrypt bitlocker to get this to work, especially the reagentc.exe /enable command. Time consuming, but it seems to work alot better. Once the update installs, I re-enable bitlocker and let in encrypt. I also automated that in the console.

reagentc.exe /disable 

get-partition | where-object {$_.type -eq 'recovery'} | Remove-Partition -confirm:$false 

diskpart.exe /s c:\newpartre.txt 

reagentc.exe /enable 

Here is the diskpart script getting called above:

select disk 0 

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

gpt attributes =0x8000000000000001 

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

For the bitlocker part I mostly used the manage-bde command, so for example to turn off bitlocker I used manage-bde -off c:

When I turn it back on I used :

manage-bde -on c: -s
Get-BitLockerVolume | Add-BitLockerKeyProtector -RecoveryPasswordProtector
Get-BitLockerVolume | Add-BitLockerKeyProtector -TpmProtector

This seemed to work well and alleviated alot of manual work, the only downside is you have to wait for full decryption before you can apply the update.

In my case id did not work.

My recovery partition is Partition 1

(My OS is in Spanish)