Maybe perusing Event Viewer would help. That has been a last resort (because it's hard to use) method for me to dig into all kinds of strange windows issues over the years.
Is there a workaround for KB5034441 install failure that doesn't require partition modification?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
127 answers
Sort by: Newest
-
Anonymous
2024-03-14T00:25:15+00:00 -
Anonymous
2024-03-14T00:22:09+00:00 That depends on your BIOS. Usually it is in the BIOS security settings. You have to enable the TPM to be accessible by the OS. Just that, nothing else. I would recommend consulting with the BIOS documentation.
-
Anonymous
2024-03-13T20:52:44+00:00 I have 5 of the exact same spec computers, bought at the same time. 1 of 5 is running into this error installing the update. The Windows and Recovery partitions are all set to the same size on all machines. It installed fine on 4 of the 5.
The error does not seem to be entirely related to the recovery partition size. As a test, I also deleted all Windows Update files and reinstalled the update. It failed during install with the same error code.
Which OS and is it possible the one that's not installing properly has TPM disabled in the BIOS?
Windows 10. TPM is enabled in BIOS and Windows reports it's ready for use.
-
Anonymous
2024-03-13T20:28:22+00:00 I have 5 of the exact same spec computers, bought at the same time. 1 of 5 is running into this error installing the update. The Windows and Recovery partitions are all set to the same size on all machines. It installed fine on 4 of the 5.
The error does not seem to be entirely related to the recovery partition size. As a test, I also deleted all Windows Update files and reinstalled the update. It failed during install with the same error code.
Which OS and is it possible the one that's not installing properly has TPM disabled in the BIOS?
-
Anonymous
2024-03-13T20:21:09+00:00 I have 5 of the exact same spec computers, bought at the same time. 1 of 5 is running into this error installing the update. The Windows and Recovery partitions are all set to the same size on all machines. It installed fine on 4 of the 5.
The error does not seem to be entirely related to the recovery partition size. As a test, I also deleted all Windows Update files and reinstalled the update. It failed during install with the same error code.