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: Newest
  1. Anonymous
    2024-02-26T17:00:55+00:00

    You may have just solved it 1proggy. The laptop is a Dell E5530 (2013). There is a TPM but in BIOS it is deactivated. Sadly in the interim since I started this post thread, the hard drive developed a thermal issue. An EVO 870 is on it's way and I'll update this thread if the issue gets fixed by enabling the TPM.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-26T06:31:33+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

    Another reason to manually upgrade/prepare the Recovery Partition is if you have a PC with a motherboard manufactured before the TPM (Trusted Platform Module) was created (first TPM around 2005-2007, TPM 1.2 ~ March 2011, TPM 2.0 ~2014-2015) in which case you will not be able to use BitLocker. For example, of the 20+ old and modern PCs I administer I have one quick for what it is used for, clean, Dell Inspiron 530 running Windows 10 PRO MBR format Samsung 850 SSD. The motherboard supports an Intel 805xx architecture Yorkfield Q9650 quad-core 3.00 GHz CPU code 80580, but has no BIOS/chipset TPM. Thus KB5034441 will not install as it finds no TPM available [or possible]. As all other Win 10 recovery options are available with manual update, hiding KB5034441 and updating the Recovery Partition via the MS PowerShell method above (if desired) is an option. It worked flawlessly on the Dell Inspiron 530 Win 10 PRO system and its recovery partition is up to date--without BitLocker.

    You can check for TPM in your PC/laptop BIOS in MBR format systems as well as in the Windows 10 Settings-->System-->About-->Device Manager-->Security Devices. In this Inspiron 530's case the Security Devices branch does not exist.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-25T16:53:25+00:00

    Mine was already at 508MB. I increased to 1024MB and the update succeeded.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. 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 No comments
  5. Anonymous
    2024-02-22T19:02:11+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"
    

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments