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-02-10T02:28:30+00:00

    There is no workaround and there is nothing that we can or should do. This is Microsoft's situation to deal with and their problem to fix.

    I am truly saddened when I see people doing damage to their systems to try to fix a problem that only Microsoft can fix. Who knows what trouble will result when Microsoft finally does release a corrected version of this update, and it tries to install on a computer that has been altered in ways that Microsoft doesn't support.

    Sit back and do nothing. This one is on Microsoft.

    Was this answer helpful?

    300+ people found this answer helpful.
    0 comments
  2. Jonathan Deives 81,350 Reputation points Independent Advisor
    2024-02-10T02:50:46+00:00

    My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today.

    Many people reporting problems with update, you need to wait for the developers to resolve the problems with this update, the best alternative is to pause the update for 7 days.

    Was this answer helpful?

    60+ people found this answer helpful.
    0 comments
  3. Anonymous
    2024-02-12T19:18:16+00:00

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  4. Anonymous
    2024-02-15T15:31:35+00:00

    Had one of our employees get an error. My laptop had not yet run the update. When I did a Check for Updates on my machine, it found it and installed it seamlessly/successfully. Figures.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-02-15T17:31:54+00:00

    Have this issue as well. Exchange had to roll back this morning because the install failed. Also see in my console that almost every single desktop/laptop on campus has failed this update this week.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments