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-19T05:33:30+00:00

    Hi,

    I would advise resizing your recovery partition to just under 900 MByte at first try, then if necessary 1.25 GByte. If you have an Intel 805xx processor-based system you probably will not succeed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-02-19T15:59:21+00:00

    Why just not check the processor first, then resize the partition if the processor is > Intel 805xx? As to resizing partitions on the storage device, it's not something I would recommend to anybody without dire reason, and this update doesn't appear dire. Windows isn't Linux, especially if you have Bit Locker enabled. Chien Sage has the best reply so far, IMHO.

    To update, I just installed an SSD and Windows 10 Pro on the very machine in question. It has an i5-7200U, which is Product Code 80677. With a fresh vanilla install, using the latest downloaded Windows Install Media Creator app, I get the error as it automatically updates. Still. On a fresh install, Windows controls partition creation, not the user.

    BTW, what does it mean "an Independent Advisor"? I've been working with Windows since 3.1 came on floppies, been there, done that in pretty much any imaginable way with Windows, and not that long ago was operating a nice Dell blade server with Windows 2019 Data Center, so can I be an Independent Advisor? Does it pay, and if so how much?

    Was this answer helpful?

    3 people found this answer helpful.
    0 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
  4. Anonymous
    2024-02-20T01:51:12+00:00

    YOU ARE CORRECT !THIS ON MICROSOFT !

    Its time for them to get to work !

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-02-21T04:20:06+00:00

    they will ditch it and come out with win 12

    they never get an operating system to work right

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments