frustrating update of KB5034441

Good day jvajva

If I follow initially to the suggestions (instructions) given by MS support I honestly expect a working fix, not such as I experienced, later on someone telling me "Columbo like catchphrase: Just one more thing" ... see me prtscr attached and tell if I did any wrong compared to the instructions given? AND NO I have not "fumbled" at any previous time on resizing the partions of my PC... I am somehow red in my face. True it is a very rare occasion, but MS got my "dough" at point blank. Great the community was finding "ways around" and helped a lot faster than MS "Capt. slow policy" hanging loose or dangling somewhere between Redmond and Pluto" ever since mid January 2024". ... in short words the error showing (in German) says ... the file "C:\1\1.ps1" can't be loaded for the reason it is not digitally signed.... :-(( I am waiting for W12 now....

I am waiting on my Micro$oft Programming Engineers Check from Micro$oft! If I have to go in and run all these different line commands etc... to get a Micro$oft patch to work, then I want to get paid for it. I do not work for free!!! Why do I have to go fix what Micro$oft F*cked up? I have been to 3 different knowledge base instructions trying to get this patch to work and each one of them gives me an error. The last one is I can not change the WinRE on an OEM item. After 3 hrs of giving myself a migraine and some colorful words coming out of my mouth. I said **** It. I don't care if this **** of an OS gets patched or not as long as it works, and the second it stops working, I will become a Linus Torvalde fan all over again. Strange how you can get many different flavors of Linux for free and it is more secure and stable than Micro$oft Windows, but yet you have to fork over big bucks for Windows, that keeps putting out patches that the user has to fix and finagle to get it to work. If Micro$ofts Programming Engineers can not put out a working patch that does not require user intervention, then the Programmers need to be FIRED!

Well put my good man.

In the backup method, I got some illegal character errors for these lines:
$sourceItemPath = Join-Path -Path $sourcePath -ChildPath $item.Name

Copy-Item -LiteralPath $sourceItemPath -Destination $destItemPath -Recurse -Force

But, even after resizing the partition several times, up to 2 GB, I still get the same error on some machines. I have noticed that it is only happening on Server 2022, 21H2, 20348.2322 when the Windows RE partition was already over 500MB. On computers with the same build and a smaller recovery partition, the install went fine many weeks ago.

Thank you for the script though, it was good to see how to do these things, and query the free space within unmounted partitions.

I still get error: "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643)", when I try to do update KB5034441. Update seems to download fine, but "Status: Installing" remains at 0% until above error appears. My Healthy (Recovery Partition) is 571MB.