So Tiny Tim, what do you want for Christmas?
I want KB5034441 to install!
Oh Tim, you’re such a rascal.
(Next up, two KBs walk into a bar.)
Is there a workaround for KB5034441 install failure that doesn't require partition modification?
![](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)
Anonymous
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-04-10T16:58:51+00:00 -
Anonymous
2024-04-06T15:40:13+00:00 you can buy a external chip for TPM 2.0
-
Anonymous
2024-04-06T13:29:50+00:00 And how long will it take for microsoft to fix this issue?
Its been now 4 months, and no fix has arrived yet. How long does microsoft keep this fix delayed, and meanwhile numerous people try their own "fixes" and end up bricking their pc's...
Would think that security updates would need urgent and immediate fix, but guess microsoft thinks otherwise.
Your recommendation to pause updates for 7 days helps NOTHING and nobody, when its already been 4 months of no fix to this...
Shouldnt microsoft apply a "patch" to windows, allowing users to pause their updates for 6 months for example (instead of only 7 days), if it really takes months for microsoft to fix the problem they caused.
-
Anonymous
2024-03-25T20:28:32+00:00 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. :-)
-
Anonymous
2024-03-25T19:59:25+00:00 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!