ReAd the UPDATE: Tuesday 2/27/2024. Go into BIOS and Enable TPM.
Is there a workaround for KB5034441 install failure that doesn't require partition modification?
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: Most helpful
-
Anonymous
2024-05-29T17:22:09+00:00 -
Anonymous
2024-05-24T05:26:30+00:00 Ideally why would you even enlarge the recovery partition? Why not just create a new partition at the end of the disk and just re-point the recovery partition pointer to that after proper formatting and data copying?
No need for deletions, no need for reagentc commands aside from /info.
But why would you use Paragon (MiniTool/AOMEI/EaseUs) to shrink drive C if you have disk management available? No reboot, and certainly no 20 minutes required.
You never need a tool to shrink drive C as there is always disk management and diskpart.
You never need to delete a partition unless you resize relying on Windows facilities.
You never need to resize with BitLocker disabled.
-
Anonymous
2024-05-20T22:35:43+00:00 My recovery partition is currently 584Mb and apparently has 100% free!
See this reply by Ramesh Srinivasan: "Disk Management doesn't show the free space in the Recovery partition. It always shows 100% free. It's misleading."
Can't install 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)
-
Anonymous
2024-05-20T12:34:26+00:00 Windows 10.
Seems KB5034441 is/has been failing to install with error code 0x80070643 for quite some time.
My recovery partition is currently 584Mb and apparently has 100% free!
It looks like WinRE is also enabled.
Will check TPM is on in BIOS.
Suggestions welcome.
-
Anonymous
2024-05-08T19:14:10+00:00 If I bring up Disk Management it indicates that partition #4 is 718 mb and is 100% free.
You'll love this one: Disk Management has no judgment of the free space of a protected partition. It has no judgment of the file system either. No judgment of free space and file system of Recovery or EFI System Partitions, for starters.