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-04-02T14:59:18+00:00

    Thank you for signposting a much simpler route to solving this infuriating and long-standing problem. I am a bit of a technological dinosaur, and the thought of navigating seamlessly through Command Prompt filled me with dread. So, as you suggested, I downloaded 'MiniTool Partition Wizard Free 12.8' and was overjoyed to find that its 'Extend Partition' option gave me the opportunity to transfer space directly from the main Data Partition to the Recovery Partition. Alas, the 'Slider' that enables you to specify the transfer amount seems to have a minimum transfer of 1.2GB (rather than the required 250MB). So, instead, I used the 'Move/Resize Partition' function, which allows you to specify the precise number of MBs to shrink the Data Partition. This then creates an Unallocated Partition of 250MB. I then returned to the 'Extend Partition' function which helpfully defaulted to the option of transferring the 250MB in the Unallocated Partition directly into the Recovery Partition (and then automatically deletes the emptied Unallocated Partition). A re-boot was required after the initial (shrink) 'Resize' of the Data Partition, but otherwise everything was implemented within seconds. And, hey presto, the offending KB5034441 did, at long last, install successfully. So the 'MiniTool Partition Wizard' worked wonders for me...though the real, universal solution is obviously an automatic 'fix' from Microsoft itself.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2024-02-22T22:44:55+00:00

    You can hide the non-installing update with the PSWindowsUpdate PowerShell module. It will probably get superceeded anyway once Microsoft has a fix.

    #you might need one or more of the following:
#Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
#Install-Module PSWindowsUpdate -Force
Import-Module PSWindowsUpdate
Hide-WindowsUpdate -KBArticleID "KB5034441"

    Or direct download and run the Microsoft Update item Hide/Unhide software tool: https://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-05-12T01:59:55+00:00

    So grateful, for your insight on this stupid problem!

    This approach worked for me on several aged HP machines, which I understand are near end of life, but not quite ready for disposal.

    Shame on Microsoft for making this so difficult to accomplish. They diminish the concept of keeping up with updates, when they do not provide a path to achieve same.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-02-22T17:57:21+00:00

    it's February 22 2024 and there is still no fix for this KB5034441!! I keep getting the same error message, is it that hard to figure out over there???

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-02-19T01:53:54+00:00

    To pile on, my recovery partition is greater than 250MB (see below), everything else is as it should be I think?

    Any suggestions?

    DISKPART> detail partition
Partition 3
Type : 27
Hidden: No
Active: No
Offset in Bytes: 511565627392
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 NTFS Partition 517 MB Healthy Hidden

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments