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: Most helpful
Most helpful Newest Oldest
  1. 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

  2. Anonymous
    2024-04-20T15:52:30+00:00

    So, can anyone confirm that upgrading to Windows 11 resolves this issue?

    Thanks

    PS: Why did KB5034441 fall down the well? Because it couldn't see that well!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-14T19:43:12+00:00

    The issue happened after a windows update. We have managed to reinstall windows 10 after backing up docs and photos. The computer did say it was a memory issues.

    Thank God we could access through dos.

    We used the info from Al Reaud.

    All this and now computer is back to normal.

    Not going to do the latest update that is for sure.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-04-14T12:43:20+00:00

    I was able to fix it manually with zero issues, on mutliple machines.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-04-11T13:25:47+00:00

    yet another user with this issue. Is MS completely silent on how to fix this still?

    Was this answer helpful?

    0 comments