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.
If that would be the case, I would advise Microsoft: "Go for it". My solution to that nonsense in not to buy a new Windows compatible computer, LOL, it's to migrate the machine to Linux. BTW, that applies to Apple products too prior to M architecture. I run Kali Linux on a 2007 white Macbook. Again, if that is the case all I can tell vendors like that is: "Hey guys, I'm not your F*****g co-dependent to your addiction!". Hopefully that is not the case with this KB...
These dated February 15, and as of today, March 22, 2024. Microsoft still has not fixed it. I believe they're just put the squeeze on us to download Version 11
Going to start using Ubuntu as soon as end of support is reached
If you go to Carey Holzman's channel on YouTube he just did a video on this issue and it works. https://www.youtube.com/watch?v=Gq\_WV2OZEks
Thank you -- I've been messing with Windows Updates for a day now as a way to deal with slow boot time. The video you link to is great with lots of background info about this update and how to resolve it.
If you do have a computer with TPM, then you can run this Powershell script to extend your WinRE partition by 250MB (if needed), then retry the update: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
In my case, I don't have TPM on my old Dell All-In-One so I just hid the update, as @1proggy suggested:
Note that I also installed and ran a pretty good Windows 'repair tool' that can reset Windows Update (and other) issues: https://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html
On the fun pi__ing contest, I was first introduced to computers on a Sperry Univac 9000 series in the early 1970s. It was all uphill from there. :-)
