This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Microsoft has released a frustrating update of KB5034441 which can not be installed by a common user in any means. it needs to expand the virtual memory in a very technical and the professional way. can anybody help how to install it in any easy way ? or how to permanently by pass this frustrating update? i am using windows 10 pro ver 22h2 infact the worst one of the entire win 10 history because :
ms security is down since last 8 months & there chat helpline and all over the forum has failed to resolve it. microsoft told me that they are not even aware of this. windows security was going auto down, any how i ve purchased a extremely expensive software to fix that.. now ms launched another prb which i ve been asking for a fix. they ve charged me for win 10 pro and after couple of years failed their security in the windows..anyhow.. about KB5034441 any fix ?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I haven't read every response, so maybe this has been already answered: What is the risk of not doing this (difficult) update?
Can anyone quantify?
It seems that if it was "critical" MS would have a "plug & play" solution by now.
We are up to 25 pages now. And MS has not made visible effort at fixing it.
So what is the risk?
-Bob
Good morning
It seems that Microsoft does not know the easiest solution for the KB5034441 update failure.
Indeed, since the release of cumulative update KB5035845 (OS Builds 19044.4170 and 19045.4170) on March 12, 2024:
if you perform a system repair by upgrading without loss of data, programs and settings using the Windows 10 22 H2 ISO available on this page:
https://www.microsoft.com/fr-fr/software-download/windows10 …
see :
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
Once the In place upgrade is complete and Windows Update is completely updated automatically (moving to the latest build, currently 19045.4291 for Windows 10 22H2, or later build in the future), the KB503441 update will eventually install automatically.
Note that the WINRE partition was automatically enlarged….
Important :
When launching the upgrade, in the "Get updates, drivers, and optional features" window, make sure to check the box: "Download updates, drivers, and optional features ( recommended)".
(This box is normally checked by default).
Remarks :
1- No need to ask questions because this solution definitely works.
I had done more than a dozen similar tests (system repair by upgrade) before the release of cumulative update KB5035845 (OS Builds 19044.4170 and 19045.4170) and it did not work.
whereas now, with this KB5035845 or with the latest cumulative update KB5036892 (OS Builds 19044.4291 and 19045.4291), I also did several tests and it works, but I remind once again that repairing the system by updating level without losses (Repair Install of Windows 10 with an In-place Upgrade) remains essential.
2- Even if you have performed a clean instal of Windows 10 22H2, repairing the system by an In-place Upgrade remains essential so that the KB5034441 update can be installed automatically.
I'm sorry for the automatic translation from French because I don't understand English.
Thanks!
The script is the automation of the instructions here KB5028997: Instructions to manually resize your partition to install the WinRE update - Microsoft Support
Used co-pilot to create the Powershell command for it.
| # Resize the OS partition by 250 MB <br><br><br><br> # Note: You'll need to manually shrink the partition before running this script <br><br><br><br> <br><br><br><br> # Check WinRE status <br><br><br><br> $winreInfo = reagentc /info <br><br><br><br> $winreLocation = $winreInfo | Select-String "Windows RE location" | ForEach-Object { $_.ToString().Split(": ")[1] } <br><br><br><br> <br><br><br><br> # Disable WinRE <br><br><br><br> reagentc /disable <br><br><br><br> <br><br><br><br> # Prepare the disk for a new recovery partition <br><br><br><br> diskpart <br><br><br><br> list disk <br><br><br><br> # Select the OS disk (replace <OS disk index> with the actual index) <br><br><br><br> sel disk <OS disk index> <br><br><br><br> list part <br><br><br><br> # Select the OS partition (replace <OS partition index> with the actual index) <br><br><br><br> sel part <OS partition index> <br><br><br><br> shrink desired=250 minimum=250 <br><br><br><br> # Select the WinRE partition (replace <WinRE partition index> with the actual index) <br><br><br><br> sel part <WinRE partition index> <br><br><br><br> delete partition override <br><br><br><br> <br><br><br><br> # Create a new recovery partition <br><br><br><br> # Check if the disk is GPT or MBR <br><br><br><br> list disk <br><br><br><br> # If GPT, create the partition <br><br><br><br> create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac <br><br><br><br> gpt attributes=0x8000000000000001 <br><br><br><br> # If MBR, create the partition <br><br><br><br> create partition primary id=27 <br><br><br><br> <br><br><br><br> # Format the partition <br><br><br><br> format quick fs=ntfs label="Windows RE tools" <br><br><br><br> <br><br><br><br> # Confirm the WinRE partition is created <br><br><br><br> list vol <br><br><br><br> <br><br><br><br> # Exit from diskpart <br><br><br><br> exit <br><br><br><br> <br><br><br><br> # Re-enable WinRE <br><br><br><br> reagentc /enable <br><br><br><br> <br><br><br><br> # Confirm WinRE location <br><br><br><br> reagentc /info |
|---|
+1 The script is no longer available. Now what?
