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.
Nicholas Sullivan1,
After running reagent/info, my Windows RE Location is harddisk #1 and partition #4.
If I bring up Disk Management it indicates that partition #4 is 718 mb and is 100% free.
Does that mean that the Windows RE Location is a sub-partition of partition #4? If so, too bad they didn’t just use the whole partition.
Thank you for your time,
DefinitelyNotFunny
PS: Hey Microsoft, what did KB5034441 say when it swam into a wall? Dam.
Yup, three options - program it yourself, upgrade to Windows 11, or live with it.
I may try to live with it (CVE-2024-20666 - Security Update Guide - Microsoft - BitLocker Security Feature Bypass Vulnerability …A successful attacker could bypass the BitLocker Device Encryption feature on the system storage device. An attacker with physical access to the target could exploit this vulnerability to gain access to encrypted data.)
Either way you cut it Microsoft did not provide a “user friendly” solution.
PS: Hey Microsoft, did you hear about KB5034441 stealing a calendar? It got 12 months.
Only Windows 10 22H2 and older have the KB5034441 install failure. Download and install the newest version from the Microsoft server has the fix built into the reinstall version. The fix is different for different versions of W10 (Pro, Home, Enterprise...)
Sorry, I don't have the version number with me.
Windows 11 doesn't have the problem because, it uses a completely different method of organizing recovery data.
Thank you for the information and all the hard work. Unlike similar instructions, these are clear enough that I might give them a try, though it is a little scary messing with things at this level.
One question, will upgrading from Windows 10 to Windows 11 resolve this issue?
If not, I'll have to think about it. My understanding of the security vulnerability is that someone must first "physically" take control of your PC. I might be able to live with that. Then I have to figure out how to stop further KB5034441 attempted updates.
Wow, talking about the lessor of three evils.
PS: Hey Microsoft, why did KB5034441 cross the road? To get to the other side!
Yep, I found this on the Microsoft support website and now the file works.
