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

Right there with you... Been at the IT game since bubble cards and card readers on mainframe/mini systems were in use.

I don't have a lot of patience for the kinds of garbage that Microsoft, and many other large software/hardware, companies produce and then expect their paying customers to clean up for them. More so when that customer is a home user.

Now, I think there is a balance that needs to be struck such that those that prefer to allow Microsoft, et al, completely "rule the roost" can do so, and Microsoft, et al, then have a responsibility to do the job right and when they don't get it fixed ASAP with at least a public "mea culpa" so everyone knows that there is an issue and they are busting their collective **** to get it fixed--and withdraw whatever offending "item" is creating the problem.

Or better yet, in this case, properly prepare the update for the various likely scenarios. For instance, this scenario could have been avoided with a simple "pre-flight" check of the size of the RE partition and if insufficient perform the steps outlined in KB5028997 automatically as necessary.

Then for advanced users, provide a more accessible version of their OS--like allowing Professional editions to be purchased and supported even if you aren't a business (you know, like they used to).

ALL issues with updates should still be addressed as they are for the "novice" end user, the end user that "just wants to get on" the system without having to think about how any of it works. This should be the default for putting out updates, or anything else that can affect the entire system in this manner.

Another option for extending the RE partition is to use a 3rd party disk utility that allows you to "rearrange"/resize"/"create"/"delete" partitions, such as EaseUS Partition Manager.

It should be possible to see the RE partition, delete it, move the Windows installation partition to the start of the disk--careful not to overwrite the protected partitions--like the boot and the manufacturer's "clean install" to purchased state (if it exists)--and then create a partition that can then be configured as the RE partition.

Though I'd probably use the creation steps that Microsoft has outlined in KB5028997 now that the placement will put it at the end of the occupied section(s) of the drive. This placement still isn't the best scenario, because, if you find you have the room at the end of the drive and need to expand the Windows partition later you have to go through all of these steps again.

As of this point I've done three physical systems and one VM using the steps in KB5028997 successfully--but also very carefully/deliberately--and then successfully completed this **** update.

Don't know if ANY of this helps anyone, but I thought I'd "throw" it out there as a possible solution for moving/re-arranging/extending the RE partition.

IMHO, instead of making this something the end user has to be responsible for, Microsoft should be putting this into the update as a test and as necessary warning that the RE partition needs to be resized, ask the end user if they are okay with the change and if okayed doing the repartition, the restart and then the installation of the update. Don't leave the end user having to determine their mess and have to correct it.

I ran diskpart and shrunk the the c: partition, followed the instructions for creating the new recovery partition. It worked fine for me, but I've been a Windows user for over 30 years with training in dos and older Windows versions on IBM and other major brand pcs and laptops. The field of pc makers and models is too diverse these days for the average home user to attempt this without having some idea of how partitions are setup on their system.

Hi all,

I haven't seen anything new from MSFT on this subject. I've continued some experiments on my own to learn a bit more about what's happening. The main obstacle to installing the patch is whether the system drive's "recovery partition" is large enough (768MB) for the installer to successfully complete putting the patch into a system. For one thing I've been looking at what it takes to create the "right" size Recovery partition at the time of installation. There might be later problems when a user attempts to re-install Windows 10 (often on Tech Support's advice). Is the re-install tool going to resize the recovery partition to the original size?

Starting with a newly "cleaned" (done by diskpart) drive (only drive in this system), I observe that the Windows 10 installer (from a Microsoft supplied Windows 10 image file) creates a 500MB recovery partition as the first partition on the drive. The installer creates 3 more partitions immediately after the first with no space between the partitions. Microsoft's manual patch to the fix is to create a 768 MB partition after all the other partitions since the first partition has no room to have its size increased in place. Afterwards there's a 500 MB empty partition in the first position on the disk. It also seems this partition should have a partition allocated for it because the patch installer tries to use the first Recovery partition it finds.

In one experiment I manually created a 250MB NTFS partition as the first and then let the installer create its usual partitions including a 500MB recovery partition as the second partition. After the install I followed MSFT's manual instructions up to removing the installer's own too small recovery partition along with my own 250 MB partition. I used MSFT's partition allocation script next and this produced the target partition size (768) in the disk's first position. The online patch successfully completes with this configuration.
I can't say more about the success of this effort because I discovered I was working with a broken SSD, and I've had to replace the drive. Not a Windows problem, a Linux installation using this drive also met with failure.

You can readily see what's on the system (C:) drive using diskpart or Disk Management. These will show you the drive's partitions including their sizes and order of placement. If you have a ~500MB Recovery partition and the urge to install the patch, then following MSFT's manual instructions will fix the problem.

While this patch doesn't seem to notice whether BitLocker is installed, you might be right about whether this patch is relevant to the Home edition. That the patch makes repeated efforts to install itself is likely another indication of MSFT doing inadequate testing before releasing the patch.

Good luck to us all.

art

2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) - Still not downloaded.

Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.403.2784.0) - Current Channel (Broad) – Installed again on 1/28/2024.

KB5034441 has still not been downloaded. Does anyone know WHY KB2267602 keeps downloading with Different Versions?