Security Update KB5034441 for Windows 10 Ver. 22H2 will not install.

2/10/2024 - INTERESTING. WHEN I CHECK MY SECURITY UPDATES IT SAYS I AM CURRENT; HOWEVER, WHEN I CHECK INSTALLED UPDATES I CAN'T FIND KB5034441 ANYWHERE. ALSO WHEN I CHECK MICROSOFT LIBRARY/DIRECTORY, I CAN'T FIND KB5034441 AVAILABILITY ANYWHERE FOR WINDOWS 10. I'M ASSUMING THEY HAVE EITHER TAKEN THE UPDATE DOWN OR ARE WORKING ON A FIX AS I WAS TOLD IN MY ONLINE CHAT OF 2/4/2024 WHEN THEY TOLD ME THEY WERE AWARE OF THE PROBLEM AND A TECHNICIAN WOULD HAVE A FIX BY 2/13/2024???

you are probably familiar with the old adage that goes back to early computing days: "To err is human, but it takes a computer to really f**k things up".

art

I'm glad you are so hopeful MS will soon fix it. I think over a months time, with no help. Is way too long to wait. I already went thru similar **** like this. With Windows 7, caused by that pestering Update to Windows 8 popup all the time. Which when people set their computers back to factory settings? That Windows 8 Popup caused massive trouble. It installed correctly, but left you manually installing over 100 updates yourself. In other words, They never did fix that problem, ever!

In one experiment here, I installed a fresh copy of Windows 10/Pro on a completely "cleaned" SSD. The source for my install image file was a Microsoft download. The installer package placed the Recovery partition as the first partition on an NVME SSD.

Also going back to Windows 2k era or there abouts, Windows installers write partitions not just on the drive you might be installing to, they write partitions to any other drive found in the system. Mainly because I want each of my system installations to be independent and self-sufficient, before I start an install I'll remove all other drives from the desktop.

With UEFI the partition allocation, stuff also gets looked at the by a system's BIOS so it can look for recovery partitions and possible boot partitions. But if another drive has another system's recovery partition written to it, losing that drive can make it impossible to boot that system. I prefer using the UEFI list of bootable systems over say Linux grub loader or Windows boot options. If I'm not careful, Windows 10 and 11 seem to make their own partitions the only boot choices.

The following Microsoft document does a decent job of explaining partitions and how to manage them.

Windows Setup: Installing using the MBR or GPT partition style

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11

One reason for wanting to have 3 distinct systems installed is to be able to test new systems like Windows 11 and Windows 10 before this. From my point of view it took more than 5 years for Windows 10 to become usable for my purposes. Windows 11 has not yet reached this point. I need to be able to use something else when a new Windows 11 changes/deletes some capability that I rely on.

art

Installed on my hp laptop win10 22H2 latest build SSD drive. Still fails to install on my hp pavillion desktop win10 22H2 latest build hard drive which is not compatible with win11.

This update wont affected the operation and running of one's computer.

It's not worth trying to muck around with trying to resize one's recovery partion so the update installs.

Its more on a nuisance and annoyance when you notice the fail to install error of this update all the time.

Given time i think MS will resolve this.