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
Is there a workaround for KB5034441 install failure that doesn't require partition modification?
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: Newest
-
Anonymous
2024-03-23T01:31:18+00:00 -
Anonymous
2024-03-22T03:25:18+00:00 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...
-
Anonymous
2024-03-22T02:27:27+00:00 I have same issue on an old Dell 690 that still works fine but the fix did not fix this. MS must be up to old tricks trying to disable old computers as a lot of previous updates made me reset windows. Its so they can sell more windows licenses=more profits=higher stock price. I may need to look at Linux again or some other more lucrative OS as this monopoly continues. Cant wait for Windows 11 w AI and more CIA/FBI spy **** NOT.
-
Anonymous
2024-03-21T12:45:21+00:00 Don’t know what’s going on with Windows but from the beginning of this year I’ve had a higher success rate of installing a Trojan than any of there dodgy untested updates.. There latest security updates on Windows 10 now has fully bricked my high end gaming pc to bios so thankyou for ruining my pride and joy windows.
-
Anonymous
2024-03-17T12:09:39+00:00 Agreed