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 No comments

127 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-17T23:30:08+00:00

    The web-posted KB5034441 fixes work on Intel 806xx product code and newer 807xx Intel 64-bit processor based systems, but do not work on older Intel 805xx processor (like Xeon E3113, Core 2, Core 2 Quad, Core 2 Extreme, dual core Xeon, Pentium D, Celeron D, etc.) based systems. At present MS has released no fix for these older Intel 64-bit processor based systems.

    To date, I have successfully created/resized the WinRE partitions and installed KB5034441 after increasing the WinRE partition size in more than 20 Intel 806xx processor I-5 and I-7 laptops/desktops/workstations after resizing and/or creating the WinRE partition correctly with zero failures. However every Intel 805xx based processor system fails the KB5034441 update/installation. I have tried increasing the WinRE drive in steps to over 10GByte size to no avail, re-installing Windows 10/PRO latest/last update/troubleshooting/etc. and many other work a-rounds, including manually installing the code into the WinRE partition (successful equivalence of the KB5034441 but the KB5034441 update still fails even though it is effectively already installed! Sometimes I just laugh!!!)

    For tables of the Intel 805xx, 806xx, and 807xx processors check at the bottom of the wikipedia article: List of Intel processors

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-04-12T20:17:57+00:00

    Date April 12 2024.

    I Spoke with Microsoft Support (more than five (5) Tech support members: "We have no plans for correcting this update error. Windows 10 is approaching EOL and that does not support W11 is near EOL. MS recommends upgrade."

    I told the MS support staff members that, I support systems that utilize W10 software and related hardware that, control, or maintain infrastructure systems that, cost $millioins of dollars to retrofit and down time that is unacceptable for safety or profitability. And since "Safety & Security" is of the essence, and the update notes state this update is not optional because it closes a security breach then, the update must be completed.

    When I asked the Support Techs to escalate this case they disconnected the call.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-19T22:03:40+00:00

    Your partition is likely too small, or not recognized correctly, or a host of other recently discovered bugs in the KB5034441. On Microsoft/programmers failed release of this POS I believe we are in agreement.

    Excuse me, you misunderstood my intent. No amount of resizing/software/programming enables the Intel 805xx based processor systems that I have attempted to install the KB5034441 Windows Recovery Environment update on, even when I manually program the same upgrade (without Microsoft's buggy patch) into the Recovery partition on these (Intel 805xx) systems. All of my PC-systems have the Windows Recovery Environment correctly installed, regardless of KB5034441. Repeat, I program computers--for my entire career--not just fiddle around with PC/hardware/software installations.

    BTW, I first began programming using punch cards in 1969 for the IBM System/360 mainframe. I began my PC career later, at the same time/place, virtually as Gary Kildall. Lets suspend any pointless pi__ing contest(s) concerning computer/programming/hardware experience and solve problems.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. 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 No comments
  5. Anonymous
    2024-02-15T20:16:24+00:00

    Can’t believe you only found this issue today!! It’ started on JANUARY 10

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments