frustrating update of KB5034441

Anonymous
2024-01-22T08:05:38+00:00

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 ?

Windows for home | Windows 10 | Windows update

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.

0 comments

321 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-05-14T16:30:22+00:00

    A relatively “simple” solution to the problems caused by the update KB 5034441, which worked for me (see tutorial below)

    Having used a copy of a recent Windows 10 installation, downloaded from Microsoft onto a USB, I carried out a “Repair Install Windows 10 with In-place Upgrade” which kept all of my files, apps and settings and then updated and installed KB 5034441 without the need to use Command Prompt, resize partitions, or do anything further. I am neither technically knowledgeable or that competent, so for further information please address any questions to ZEKRI Abdelhafid who’s method this is.

    Repair Install Windows 10 with an In-place Upgrade | Tutorials (tenforums.com)

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2024-05-12T06:33:37+00:00

    You provided a VERY HELPFUL highlighted excerpt in your EDIT:26/02/2024 on Page 1 of these comments. Although it worked, a missing piece of instruction found in the full script reached at the LINK you posted (as HERE, seen above) provided the remainder.

    You wrote, "This will ensure the folder which contains the script is selected. Now, we need to run the script, which increases the size of WinRE. For that, run the following command:

    .\1.ps1"

    The following line should not have followed, yet:

    "After that, press Y to confirm running the script."

    The text included too early is shown above as struck-through, above, and missing text is as follows:

    "When you are asked for the backup directory (this is used to ensure that your device remains bootable if anything goes wrong), enter

    C:\2"

    Now is when this text applies:

    "After that, press Y to confirm running the script.

    "Press Enter."

    As I said, the script worked, but the backup ended up in a newly created folder named 'y', Hopefully it will never be needed.

    Thanks for your good work, and for helping us out of repeated update failures!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-05-09T11:40:56+00:00

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-05-02T14:15:59+00:00

    Volume 1 J System Rese NTFS Partition 350 MB Healthy (Primary Partition)
    Volume 2 C NTFS Partition 114 GB Healthy System (System Boot, Active, Crash Dump, Primary Partition)

    Try the following: Delete System Reserved and run reagentc /enable again. Right now reagentc.exe does not know which BCD to address as there are several.

    Was this answer helpful?

    0 comments