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

Hi Judy, Hi Marv6,

I saw the failure on two different systems here (different hardware). It appeared the fix failed as soon as it "discovered" that the recovery partition was too small. No aftereffects to report. My patch to Microsoft’s fix also appears safe so far.

As far as I know, none of Microsoft's usual debugging techniques or automatic system fixes attempt to diagnose disk partition issues like this one. Mostly users only get to create new partitions, especially system managed partitions like this one, as part of an install or as part of "cleaning" a disk to remove existing partitions. diskpart is one of these tools as is "Disk Management". Even now I expect that any current, unfixed Windows 10 installer will still create a recovery partition that's too small to install this patch.

Here's what my partitions look like on one of my Windows 10 boot drives. The first unallocated partition (530MB) was the original recovery partition. The new, current recovery partition is now last because that's where I could create a 780MB partition that would fit. Enlarging the original partition in place would mean moving the other partitions out of the way.

Art

Judy, did the failed install KB5034441 cause any problems on your computer? Thinking about updating to at least get the other two updates in my laptop. thanks, Marvin

Let me know if you get any answers please.

Same here.

Microsoft's recommended manual instructions on how to make the recovery partition worked for me on 3 Win64 desktops. Two other systems failed. The difference is that the install works when the recovery partition is the last on the drive. The failures occurred when the recovery partition was first on the drive and there was no space between the first and second partitions. The newly freed space got allocated after all the other partitions. My work-around was to prevent the first partition from being used here by making this a NTFS partition followed by freeing more space from the Windows partition. This yielded a large enough contiguous block after the rest of the partitions for the patch to install.
I suppose a cleaner way to do this would be to use a partition manager that can relocate the recovery partition and move the other partitions over that space. At the moment I've got two system drives each with an unused 500M partition on it.

art