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. Anonymous
    2024-08-14T01:41:43+00:00

    Al Reaud wrote (2024-02-09):

    ...

    The issue was resolved by enabling the TPM in BIOS to allow the operating system to access the TPM. ...

    Kudos to 1proggy, below, for coming up with the answer for my system.

    I just ran into the same failure with KB5042320, again with an idiotically useless error code, on a VMware virtual machine running

    Windoze 10 and a 1GB RE partition (overkill while I was futilely trying to get KB5034441 to work), but without TPM.

    As with KB5034441, some update-related process would run for 50 seconds, then DISM would run for 50 seconds, then failure.

    It's exasperating that those morons at Microsoft are apparently incapable of providing a real error message.

    Fortunately I don't have to use Windoze for anything real (my "old school practitioning" goes back to 4.1 BSD, with 250MB disk drives

    the size of a small washing machine :)

    As before, I used wushowhide.diagcab to hide the update.

    It make sense that these WinRE updates require TPM, even though Windoze 10 doesn't, because they seem to be involved with BitLocker.

    VMware supports a virtual TPM, but that requires encrypted filesystems (boo), and an encrypted vmx (configuration) file, which was a deal-killer for me.

    And yes, indeed -- kudos to 1proggy .

    P.S.: It isn't an "issue", it's a problem. "Issue" is just a Microsoft weasel-word.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-07-05T15:07:25+00:00

    Interesting....

    Windows 10 KB5034441: PC's without a WinRE recovery partition do NOT need this Update ?

    https://www.youtube.com/watch?v=mDLjr53HSHE&list

    Was this answer helpful?

    0 comments