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-05-04T14:49:57+00:00

    There is an easier fix, listed in the thread above, of just enabling control of the TPM for the OS. But that doesn't appear to work with everybody. I disagree with a world class action lawsuit. Have you tried to sue one of the big ones? Been there done that and am waiting for a ruling on a case against FB.

    What Microsoft has done with this is paint themselves into a corner. As an example, though I have several computers, only one has Windows 10 Pro, and that is an older i3 based laptop. I'm also one of the OG's, having cut my teeth on DOS and Windows 3.1. I've learned the hard lessons over the years to not keep all my eggs in the Microsoft basket.

    The day Windows 10 ceases to update, is the day that Laptop becomes an Ubuntu Pro machine. Microsoft has already told me, via the update app, that the machine is not compatible with Windows 11. What does Microsoft think, that I'm going to throw away a perfectly functioning laptop and buy another one just to install the latest Windows? One that I recently swapped the HDD with an SSD to speed up. I have to laugh at that mentality. There are at least 10 Linux OS flavors that I can think of off the top of my head that will fit that laptop like a fine Gucci glove, LOL.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-05-05T15:21:31+00:00

    Thank you for the information and all the hard work. Unlike similar instructions, these are clear enough that I might give them a try, though it is a little scary messing with things at this level.

    One question, will upgrading from Windows 10 to Windows 11 resolve this issue?

    If not, I'll have to think about it. My understanding of the security vulnerability is that someone must first "physically" take control of your PC. I might be able to live with that. Then I have to figure out how to stop further KB5034441 attempted updates.

    Wow, talking about the lessor of three evils.

    PS: Hey Microsoft, why did KB5034441 cross the road? To get to the other side!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-05-06T06:31:27+00:00

    Only Windows 10 22H2 and older have the KB5034441 install failure. Download and install the newest version from the Microsoft server has the fix built into the reinstall version. The fix is different for different versions of W10 (Pro, Home, Enterprise...)

    Sorry, I don't have the version number with me.

    Windows 11 doesn't have the problem because, it uses a completely different method of organizing recovery data.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-05-06T15:40:21+00:00

    Only Windows 10 22H2 and older have the KB5034441 install failure. Download and install the newest version from the Microsoft server has the fix built into the reinstall version. The fix is different for different versions of W10 (Pro, Home, Enterprise...)

    Sorry, I don't have the version number with me.

    Windows 11 doesn't have the problem because, it uses a completely different method of organizing recovery data.

    In other words, you're saying upgrade to Windows 11, because 22H2 is the final version of Windows 10. That's fine if you have a computer that can do TPM 2.0; I don't, and I'm not ready to give up the one I have.

    Why do I feel like I'm stuck in a squeeze play between Microsoft and the PC manufacturers?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-05-06T17:50:30+00:00

    Only Windows 10 22H2 and older have the KB5034441 install failure.

    22H2 is the final version of Windows 10. So "22H2 and older" means ALL Windows 10 versions.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments