Windows 10 22H2 KB5034441 error still not fixed with Patch Tuesday

No the error with KB5034441 is not fixed, just ignore it or use the trick in my video on how to hide it

[daveschmarder-]

I never expect much from Microsoft. I'm never disappointed.

[thsenseeq]

Thank you for clarifying that this update is not cumulative, so it won't mess up other updates that come along. That is reassuring! In fact, I received two new updates on update Tuesday and they installed just fine; of course I tried to update 4441 but it failed again. Having researched the problem with 4441, I read that, in some cases, its failure might have NOTHING to do with the recovery partition size, but in fact relates to the update stupidly assuming your recovery partition MUST be on Disk 0! For those of us with SSD's (I have an NVMe SSD) for their recovery partition they are nearly always NOT found on Disk 0 (mine is Disk 2) so the update won't find it and fails! If all this is true, then changing the partition size wouldn't make ANY difference -- the update still wouldn't find it since it's looking on the wrong disk. And for those who have their recovery partitions on Disk 0 (likely HDD's), I discourage users who are not expert from messing with partition sizes. This could be a recipe for making bricks if done incorrectly. Although the MS fix has not come yet, let's be patient and wait for it. Maybe best not to mess with things if they ain't severely broke. I can deal with this update failing to load until they either fix it or remove it.

[Athonite]

As an advanced user going back to the DOS /Win3.1 days, I will say that I am perfectly capable of working with partitions. But I never do so unless absolutely necessary, and would never recommend it to a novice. There's a reason Partition Magic got the nickname "Partition Tragic" in the old days :)

[Cobnapint]

It's the wall of silence from MS that is so annoying. Why don't they just say hey guys, don't worry about that update failure, we're on it.
Instead, they're providing instructions on their support page on how to resize your partition.
Screw that MS. Screw that.

[Krooked]

This was the first error message I've gotten since I built my PC about 3 years ago. Had me so worried..
Thank you for this video and the explanation! 🙏

[Cheap_Fried_Rice]

can you add the link in the description on how to hide it please

[jojjmub]

why the hell would i buy win 11 or 12, when they can't fix

[stephenlawlor]

I'm been waiting for this video. Well I was curious if by now, we could finally get rid of it. Well anyway, you can at least hide it!! So Thanks For That Update!

[RomoloLuciani]

thank you very much for the information

[erre.]

The only news from MS is that they updated the KB5034441 article to point to a new [very long] powershell script made for resizing the winre partition: "Or, to use a sample script to increase the size of the WinRE recovery partition, see Extend the Windows RE Partition."

[ethimself]

I got this error code - 0x80070643 - Trying again after some fixes, seems stuck at 5% and iptional is 0% so far. If stuck, just restart etc?
Just checked and the regular up date is working

[dvsalto]

Would like to know exactly how much extra space on the recovery partition is needed to accommodate this *4441 update? I recently cloned my HDD onto an SSD and left over 1 gig of space on the recovery drive partition...

[andrewenglish]

So how do I bypass bitlocker? :) I have a drive that windows updated the Intel SATA driver and blewup my Windows that I cannot start the drive and I don't have the key to unlock it. :(

[SwankyK]

This may have also been the same update that broke the photos app on Intel Core 2 duo and quad platform CPUs. And about the same time caused an issue with updating some laptops. The "solution" I found...(I'm using the term solution loosely here) was a clean install of Win 10. and then entering sysprep mode. (Ctrl+Shit+F3) and update the system in full that way. That seemed to resolve the issue. Obviously, a DATA backup would be required. But beyond that, that's all I've got to say for now.

[Kista]

It's been over a month and still no fix by Microsoft. I've been working on another PC that is a replacement for work that I've been setting up, everything was fine with the updates but then I cloned the HDD to swap in the SSD but now even more updates have been released and one was causing an issue upon reboot that it reverted the changes back however it wasn't this specific update but had the same underlying issue of the recovery partition basically being too small. I don't know if cloning to the SSD somehow messed up the partitioning of the drive but since I still hadn't finished setting it up I decided to just reinstall Windows 10 from scratch and now it's fine.

I wanted to update, my earlier comment was 3 months ago and it's now June so it's been 6 months and there still isn't a fix by Microsoft. I don't think they are going to provide an update for it, 10 is practically dead anyways and also if you upgrade from 10 to 11 the issue is still there, you have to install Windows 11 from scratch to not have this issue. There are fixes online but it involves modifying partition sizes and most users are not going to be comfortable with all that.

[nommindymple]

It's got to be more than just a lack of space in the Recovery partition. Mine has 530MB free and the update won't install. The Feedback item for this has plenty of people with similar situations.

[johnd]

II have a WinRE partition and this update is not installing, its it a vulnerabiltiy security risk for me? Is it more safe to disable bitlocker or keep it enabled and just wait for a fix from Microsoft??

[choppergirl]

My Windows 10 Reliability Index is still hovering around 2 out of 10
See my Community Tab. Microsoft has had geez 40 years now and still can't finish one single operating system.
Just stop rolling out new revamps and whole different operating systems, just pick one, and finish it. Preferably one we actually liked, like Windows 7.
Nobody wants Windows 11, just finish Windows 10 already and get all the bugs out. I mean still, the friggin File Explorer will hang all the time to a white solid window, what's up with that. They have to be noticing that.

[wildbill]

I haven't tried it on either computer I updated last month, where it failed, but I have another computer, which I didn't update month, but decided to update this month and it worked on that one. The 2 computers it failed on last month I haven't tried yet this month.

Update: I did updates on one of those other PCs today and it failed to install this patch again.

[lesliedavison]

Don’t use my windows 10 laptop frequently so no updates since before Christmas. Should I and how do I prevent this update from installing? If it does fail to install correctly will it harm my PC? I’m a very average user, just want it to work. My laptop does not meet criteria for Windows 11.