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.
I had intended no disrespect and was honestly curious about what an "Independent Advisor" is, do you get paid, etc. I'm rarely on MS products till late 2023 when I needed access to Word 365 and AI for use in a legal case against a well known social media entity.
You're going back to the era of minicomputers and mainframes, my friend! Windows was definitely not the OS. My introduction to computers was a community college in a Rocky Mountain state. They had a DEC PDP-11/780. It was the bomb!
Well, thank you for opening this thread -- it turned out the Windows Update issue was likely causing my boot time to lag because fixing that (hiding the update and running that repair program) seems to have resolved it.
It was mostly DEC VAX but did work on PDP-11s in the 1990s - even had to do some editing/moving of bits on a disk when there were bad data sectors. Now it's mostly Windows or Linux servers. I remember paying $610 for a 20MB hard drive upgrade for my IBM PC in 1983. We've come a long way, huh. :-)
My lame BIOS does not permit me to modify or enable TPM.
Hello everyone,
i also have been dealing with this issue for many extensive hours but could not resolve it and even contacted many times Microsoft expert about but no resolution, the best option availible to wait for microsoft about to resolve it.
Thank you for signposting a much simpler route to solving this infuriating and long-standing problem. I am a bit of a technological dinosaur, and the thought of navigating seamlessly through Command Prompt filled me with dread. So, as you suggested, I downloaded 'MiniTool Partition Wizard Free 12.8' and was overjoyed to find that its 'Extend Partition' option gave me the opportunity to transfer space directly from the main Data Partition to the Recovery Partition. Alas, the 'Slider' that enables you to specify the transfer amount seems to have a minimum transfer of 1.2GB (rather than the required 250MB). So, instead, I used the 'Move/Resize Partition' function, which allows you to specify the precise number of MBs to shrink the Data Partition. This then creates an Unallocated Partition of 250MB. I then returned to the 'Extend Partition' function which helpfully defaulted to the option of transferring the 250MB in the Unallocated Partition directly into the Recovery Partition (and then automatically deletes the emptied Unallocated Partition). A re-boot was required after the initial (shrink) 'Resize' of the Data Partition, but otherwise everything was implemented within seconds. And, hey presto, the offending KB5034441 did, at long last, install successfully. So the 'MiniTool Partition Wizard' worked wonders for me...though the real, universal solution is obviously an automatic 'fix' from Microsoft itself.
