This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
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.
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.
I found the same thing and asked. A reply I got back is below. My take is Windows soft of creates a partition within a partition and that sub-partition isn't big enough.
Volume Z
Replied on May 8, 2024
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.
PS: Hey Microsoft, what did KB5034441 say to its fingers? I’m counting on you!
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)
You have to extended the recovery partition.
I used Paragon Software Free Edition.
After install it will ask for recovery solution, just cancel and go right into the partition resizing.
Adjust space of main partition which provides room for the recovery.
It will ask you to reboot.
It will pop up a Paragon boot screen while it makes the adjustment. Mine took around 20 minutes.
Booted back into Windows as normal
Ran the KB update.
Installed as expected.
So let me get this right, because the arithmetic is confusing me. You resize the partition from 500MB to 1GB. That takes 1200 seconds? That is a operating speed of just over 447KB/sec. Which makes no sense on a modern Windows machine with even an Intel i3 and an HDD.
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? And on an SSD that would be the proper thing to do and just trim out the old retired one. However, because of the complexity of the OS, only Microsoft developers know where the pointers needing change reside.
So Microsoft putting this on users and not fixing it with a second KB sets a pretty low quality bar, IMHO. Especially if it requires "outside of the repository" software installs to fix, or kludgy fixes with several steps and high probability of failure for those lacking knowledge. Having an uninstallable update increases the attack surface of the OS because of the unknown future ramifications of it not installing. At least until whenever in 2025 that Windows 10 crosses the Rainbow Bridge. Then it won't matter unless you keep using it ;-)
