Is there a workaround for KB5034441 install failure that doesn't require partition modification?

My recovery was 500mb and I had to increase it by 250mb.

I followed the instructions on: https://www.msn.com/en-gb/money/technology/how-to-fix-the-kb5034441-update-fail-to-install-on-windows-10/ar-BB1hYieK

Using "Option 5.1"

This isn't for the faint at heart. Even with my "knowledge and skill" I was holding my breathe. It WAS successful and the update WAS able to install after I performed those steps BUT do at YOUR OWN RISK! If you have hesitations I suggest not doing it.

Hope this helps!

I won't tell anyone not to follow those guidelines being they're from "Microsoft" but "hiding the update" seems silly other than you just don't have any notification of it, otherwise users could just ignore the update anyway. As for that long drawn-out process for resizing the "RP", again let me just propose using Windows Disk Management and downloading/installing the basic version of "Partition Wizard" which is free & can be uninstalled after using.... Even though "Partition Wizard" can be used solely, to reduce confusion this is how I did it.

Open Window's "Computer Management" then select "Disk Management."

Select the "System" drive typically C:, right click on it and select "shrink."

In the highlighted box "Enter the amount of space to shrink in MB" enter a number like 250.

Click "Shrink."

It will complete the process and display the newly "Unallocated...." space of ~250MB.

Close "Computer Management." (How simple was that....)

(After downloading/installing "Partition Wizard basic free version")

Open it and find the "Recovery Partition" listed. Right click on it and select "Extend".

You will be prompted to "Take free space from...." and it should actually preselect the "Unallocated" space you created in "Disk Management" just confirm it's the correct one.

There is a slider you must use to adjust how much of the "Unallocated" space you want to use so just MOVE IT TO THE RIGHT to select the full unallocated space of "250MB" in this case.

Once you move the slider all the way to the right, click "OK."

THEN click the "Apply" button in the lower left of the window to apply the changes, OTHERWISE your changes will NOT have taken effect. If you try to close the program before clicking "Apply", it will warn you. (There's even an "Undo" button next to it.)

It will complete the process quickly, then you can close the program and restart the computer.

You can now try reinstalling the update.

That IMO is far simpler & safer, it worked perfectly for me and avoided all of the, "not for the faint of heart - command line interface" nonsense.

Simpler, yes, but option 5.1 in the link, often particularly in MBR format primary drive Windows 10 installations, the instructions are incomplete as Diskpart does not correctly keep the Recovery partition ID or assign it correctly via the shorthand reagentc /enable command. It does not create the directory tree Recovery\WindowsRE and then copy winre.wim to it. Thus I/most have developed, for the indicated Win 10 PRO MBR format primary drive installations an expanded creation/assign/succeed Diskpart Windows Recovery implementation instruction set. [indicated reagentc /setreimage /path [path] where [path] needs to be created/setup manually after unhiding the recovery partition, etc.].

That said, If you have a GUI format primary drive [optional in Windows 10, required in Windows 11], simple partition assignment, an inadequate Recovery partition size in Windows 10/11, the indicated simple steps in 5.1 often work. https://www.tenforums.com/backup-restore/204223-recreate-recovery-partition-reagentc-exe-operation-failed-2-a.html https://www.diskpart.com/articles/unhide-recovery-partition-5740.html

Several more references:

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/reagentc-command-line-options?view=windows-11

https://www.elevenforum.com/t/recovery-partition-reagentc-setreimage-path-to-a-recovery-partition-not-having-an-assigned-volume-letter.8158/

https://answers.microsoft.com/en-us/windows/forum/all/windows-update-kb5034441-error-0x80070643/3bcad8a3-385b-4cf8-8458-509a162cea64?page=23

https://en.wikibooks.org/wiki/Windows_10%2B_Recovery_Environment_(RE)_Notes

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/deploy-windows-re?view=windows-11

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/customize-windows-re?view=windows-11 https://www.windowslatest.com/2024/02/14/windows-10-kb5034441-is-still-broken-with-0x80070643-error/

It sounds as if you're mistaking what I suggested with what the previous commenter "DouglasNCampbell" suggested "Option 5.1". I never suggested "Option 5.1" or using any "Diskpart" commands etc. I simply "included his comment in my reply." I suggested a simpler way of resizing the "RP" which completely avoids ALL of that "command line" instruction because not everyone is adept at following such instructions especially as they can become somewhat convoluted. I still hold that using "Disk Management" and "Partition Wizard" as I outlined are simple and easy to follow for even novice users.

I included the entire dialogue, as both methods usually do not succeed in Windows 10 MBR boot/primary drive partition applications, and occasionally Windows 11 as well, and thus should have their limitation(s) recognized like I just did.

With all do respect, you said "Simpler, yes, but option 5.1 in the link...." and proceeded to critique "Option 5.1" which had nothing to do with what I suggested. I never suggested "Option 5.1 was simpler." So you're mixing two different opinions by addressing two different people's differing suggestions simultaneously in the same sentence. That creates confusion.

You then went on to say, "That said, If you have a GUI format primary drive [optional in Windows 10, required in Windows 11], simple partition assignment, an inadequate Recovery partition size in Windows 10/11, the indicated simple steps in 5.1 often work."

Again I never even mentioned "Option 5.1 being simpler." Can people even see what I wrote in the text or is this website obscuring it?!

The GUI interface within the Windows OS as per "Computer Management/Disk Management" app has nothing to do with "a command line interface" where you type in "commands" which is what you do in "Option 5.1." The "GUI" of these apps/software consist of "mouse clicks", not "typing text" other than selecting/entering a numerical value.

Given "GPT - GUID Partition Table" has been out since the 1990's I'd assume ~30 yrs later more machines would be using that standard so not to say you aren't correct about those "limitations", I suppose I'd have to see proof otherwise that either/both methods, "don't usually succeed on Windows 10 MBR partitions" because I don't have any machines utilizing "MBR & W10" to test them for confirmation.

With all do respect, you said "Simpler, yes, but option 5.1 in the link...." and proceeded to critique "Option 5.1" which had nothing to do with what I suggested. I never suggested "Option 5.1 was simpler." So you're mixing two different opinions by addressing two different people's differing suggestions simultaneously in the same sentence. That creates confusion.

You then went on to say, "That said, If you have a GUI format primary drive [optional in Windows 10, required in Windows 11], simple partition assignment, an inadequate Recovery partition size in Windows 10/11, the indicated simple steps in 5.1 often work."

Again I never even mentioned "Option 5.1 being simpler." Can people even see what I wrote in the text or is this website obscuring it?!

The GUI interface within the Windows OS as per "Computer Management/Disk Management" app has nothing to do with "a command line interface" where you type in "commands" which is what you do in "Option 5.1." The "GUI" of these apps/software consist of "mouse clicks", not "typing text" other than selecting/entering a numerical value.

Given "GPT - GUID Partition Table" has been out since the 1990's I'd assume ~30 yrs later more machines would be using that standard so not to say you aren't correct about those "limitations", I suppose I'd have to see proof otherwise that either/both methods, "don't usually succeed on Windows 10 MBR partitions" because I don't have any machines utilizing "MBR & W10" to test them for confirmation.

First off, Al Reud's message thread initiating question: "Is there a workaround for KB5034441 install failure that doesn't require partition modification?" is marked answered:

"UPDATE: Tuesday 2/27/2024The issue was resolved by enabling the TPM is BIOS to allow the operating system to access the TPM. Nothing was done to modify partitions from the default install size. Currently I have a 50MB NTFS System partition, a 465GB Primary partition, and a 546MB Recovery partition.
Looking in the Update history, KB5034441 installed correctly. Kudos to 1proggy, below, for coming up with the answer for my system."

Second, as you stated that your remedy was easier and in your view, superior to your quoted method indicated in Step 5.1 you rely on the content or lack thereof in Step 5.1 to prove/disprove, i.e. make your contention that your method is easier. Thus we need to investigate the method in 5.1 before reckoning the worthiness of your contention--of course. Note that Microsoft began supporting GPT in the 2000s, check your math. I am not claiming that GPT is not superior to MBR, or even more popular presently, only that there are still a plethora of the MBR systems still in everyday use and that they are the particular target of the Recovery partition creation and maintenance failures, and the KB5034441 failures. Thus, your prescribed solution applies to a narrow range of the most modern PCs that and is thus very narrow in scope. Finally, your offhand assumption [without verifiable supporting statistical evidence] that there are more GPT {short for GUID Partition Table) PC systems in use today than MBR PC systems overall in the world you do not support with evidence:

https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide

ttps://www.pcworld.com/article/2094755/windows-10-doesnt-give-windows-11-a-chance.html https://www.pcworld.com/article/394791/windows-11-upgrades-for-windows-10-pcs-wont-happen-until-2022.html

https://operavps.com/blog/mbr-vs-gpt/

https://www.spiceworks.com/tech/hardware/articles/mbr-vs-gpt-the-best-choice-for-your-computer/

https://www.diskgenius.com/how-to/mbr-vs-gpt.php

https://www.quora.com/What-is-the-difference-between-MBR-and-GPT-Can-you-have-both-MBR-and-GPT-on-the-same-hard-drive

.