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

Anonymous
2024-02-10T02:17:25+00:00

We know about the failure of KB5034441, and the recent recommendations to modify a partition as a workaround. As an old school practitioner (since 3.1 came on floppies), and having crashed many a hard disk, modifying a partition seems rather extreme for an update workaround, unsafe, and IMHO highly NOT recommended. My questions are:

Is there another workaround or fix to KB5034441 not installing?
How important is this update seeing how update Tuesday is in just a few days?

Edition: Windows 10 Enterprise
Version: 22H2
Installed on: ‎8/‎19/‎2020
OS build: 19045.3930
Experience: Windows Feature Experience Pack 1000.19053.1000.0

Elevated PS Script Command> Get-WindowsUpdate -Install -acceptall -IgnoreReboot

1 hostname Accepted KB5034441 23MB 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)
2 hostname Downloaded KB5034441 23MB 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)
3 hostname Failed KB5034441 23MB 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) (Error: 0x80070643)

UPDATE: Tuesday 2/27/2024
The 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.

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

127 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-04-22T01:33:08+00:00

    What do they mean by approaching EOL?

    Windows 10 EOL is on October 14, 2025. Which is not a week time, it is more than 1 year from today.

    We can follow the suite and say Windows 11 is approaching EOL too. What's the point?

    May be we need to grasp MS recommendation for upgrading as to any non-MS OS upgrade?

    Was this answer helpful?

    4 people found 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-03T16:55:06+00:00

    Since microsoft officially stated they wont be fixing this and noticing multiple websites had different instructions or incomplete commands i put this together. Tested on GPT systems not tested on MBR yet. Please verify DISK# and Partition#, my examples are common setup but yours may be different. Tried to note in steps "whichever number is listed" means yours may be different then what is in example command.

    1. Check WinRE status,  enter   reagentc /info
      1. Note Windows RE Location,  specifically the PARTITION#
    2. Disable WinRE, enter   reagentc /disable
    3. Run diskpart,  enter   diskpart
    4. Enter   list disk
    5. Select OS disk, most likely the only one or the largest one, enter select disk 0 or whichever number is listed for OS Disk
    6. Enter    list part
    7. Select primary partition #, normally the largest size also,  enter  select part 3 or whichever number is listed on your list part
    8. Enter    shrink desired=500 minimum=500 (did 500 instead of the MS recommended 250, incase future issues)
    9. Enter    list part again note recovery partition #
    10. Enter   select part 4   or whichever number is listed as recovery partition
    11. Enter   delete partition override
    12. Enter    create partition primary
    13. Enter    format quick fs=ntfs label=”Windows RE tools”
    14. Enter   detail part
      1. Verify *"Type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7"*This will be GPT option in next step
      2. If anything else is listed it will be MBR option in next step
    15. If GPT option from above step:
      1. Enter    set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
      2. Enter    gpt attributes=0x8000000000000001
    16. If MBR option from step 15:
      1. Enter     set id=”27”
    17. Enter    exit
    18. Re-enable WinRE,   enter   reagentc /enable
    19. Enter  run reagentc /info
      1. Verify status is ENABLED
      2. Verify WINDOWS RE LOCATION shows partition4 or whichever was listed from step 10
    20. Restart and run windows updates again

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-05-04T02:36:59+00:00

    Yep, I found this on the Microsoft support website and now the file works.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-05-04T06:55:32+00:00

    Wow that is a lot of work... Microsoft Technical Support gave me an official definitive answer. A 1 step solution:

    Step 1) Reinstall windows 10 with the latest version, the script with the fix is embedded in the update.

    Microsoft will not post the script for the end user to download, and Microsoft will not update the update to include the script.

    Of course this takes considerable preparation time i.e. full backup and hours to download, install, setup and reinstall apps and data. Seems to me like cause for a world wide class action.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments