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
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: Most helpful
-
Anonymous
2024-03-23T04:09:08+00:00 -
Anonymous
2024-03-14T22:57:55+00:00 It sounds as if you're mistaking what I suggested with what the previous commenter "DouglasNCampbell" suggested "Option 5.1". I never suggested "Option 5.1" or using any "Diskpart" commands etc. I simply "included his comment in my reply." I suggested a simpler way of resizing the "RP" which completely avoids ALL of that "command line" instruction because not everyone is adept at following such instructions especially as they can become somewhat convoluted. I still hold that using "Disk Management" and "Partition Wizard" as I outlined are simple and easy to follow for even novice users.
-
Anonymous
2024-03-12T11:48:58+00:00 It's like a mechanic telling me my engine needs to be rebuilt, your warranty is expired, but here's how you can fix it at home, I'll talk you through it.
This is Microsoft telling me that my computer is obsolete.
-
Anonymous
2024-03-10T17:27:10+00:00 HOW ON EARTH IS THIS STILL NOT SOLVED? MICROSOFT ARE YOU AWARE THAT ONLY PRE-BUILT PCS HAVE WIN-RE PARTITION THAT THIS UPDATE SEARCHES???? HOW ARE YOU THIS STUPID? EXACTLY THESE THINGS DRIVE PEOPLE TO APPLE !
Actually, I had the same problem with the update not installing correctly and I custom built my machine by ordering and installing all of the components & the OS. However, my machine was working just fine without the update so I wasn't sure why so many people were in a "panic" as if "It was a system-critical update that must be installed immediately but we can't install it!" I just wanted to see if I could get it installed by increasing the RP size and the way I had done it, was easy and carefree.
I didn't have to use any "command line commands" etc. Maybe more "advanced users" are better with those "terminal interface commands" but I had initially opened "Disk Management" and "shrunk" the system partition by ~250MB. This created "~250MB unallocated disk space" on C:. Well "Disk Management" would not allow "extending the Recovery Partition", it just offers "Help"....
So then I remember I had "Partition Wizard" installed, the basic version is still offered free. So I opened it and then I was able to "extend Recovery Partition" by moving the slider to "~250MB of unallocated space" and then I had a "Recovery Partition of ~780MB" because my RP was already ~530MB. I then clicked "apply", it completed the process in less than 5 seconds. I restarted my computer, re-ran the update, it installed without issue. No problems since. That was so easy and safe & no "command line commands" etc.
-
Anonymous
2024-03-05T05:34:07+00:00 My recovery partition was ~530MB and I tried the "Instructions on manually resizing the recovery partition." I think it's silly to suggest average users would need to follow those steps and hope they didn't mess something up. I was able to follow the steps but it reached a point where it simply said it couldn't shrink such partitions and I noticed other people were going deeper creating new partitions, assigning drive letters, copying contents etc. Just too much excess for me. Users can simply wait for a "fix" but I decided to see what I could do with other tools.
I opened "Computer Management" and then selected "Disk Management" and I shrunk the System drive by 250MB. Of course "Disk Management" won't allow you to extend the "Recovery" partition so I opened "Partition Wizard" which is a free utility (basic version). I opened it and then selected the "Recovery" partition and chose to "extend" it to the "250MB unallocated space", then click "Apply" and the changes were made near instantly. I then restarted my computer.
I then tried to install the "update KB5034441" again and whilst waiting I decided to open Task Manager, "Open Resource Meter" and noticed that "Dismhost...." was running and then "UpdateWinRE...." appeared and the update successfully installed. So increasing the size of the recovery partition worked fine for me.