KB4474419 will not install

I succeed with the update.

Go in BIOS, set the windows disk as first boot device.

Let the windows update reboot the computer as it likes.

When the windows update succeed, reboot to BIOS to set the "GRUB" (boot loader) disk back as the first boot device.

You get your multi-boot back to normal.

Well, if you are in my case, have one disk dedicated for Linux, and one disk dedicated for windows.

I had the same issue with Ubuntu being the Primary boot menu (grub as Active Partition; being the Primary Boot Drive in the BIOS.  My system is dual boot with Grub bootloader on one hard drive and Win7 MBR bootloader on the other drive. After switching the Primary boot device in the BIOS to my win 7 bootable drive, installing the update manually using KB4474419 MSU, letting the machine reboot using the Windows 7 boot drive he update went though no problem. It should also be noted that I have no 100MB Reserve Drive and instead windows is installed with the reserve drive Drive C.  All steps about 100MB reserve drive problems were not needed in order to install the update. I then switched back to the bookable MultiBoot Grub Partition is bootable though Grub.

My only thought or why this worked is Windows is looking to update code in MBR, boot sector or some code relating to how Windows is loaded after the POST of the BIOS  because all I did to get the update to work was change the boot drive in the BIOS.

I am still waiting for the April 2019 security update to be available on my system to see if the update goes though OK using Grub as my bootloader.

Hi, Fix worked in my case. Thanks !

I followed those steps (from link submitted before) :

1. Temporarily assign a drive letter to the System Reserved partition from the "Disk Management".

2) Open an elevated command prompt and run fsutil usn deletejournal /N /D X: where "X" is the assigned drive letter of the "system reserved" partition.

3) Remove the drive letter to the "system reserved" partition (which should remain without assigned drive letter).

4. Launch the KB4474419 update

In my case, my system reserved partition is 350 MB large and was totally full.

Clearing the logs only cleared 40 MB (310/350). It worked anyway.

I have installed this system and several others myself using Windows installer. I perfectly remember that when you create partitions using this installer, it asks if you want to create a Reserved partition or not.

So I confirm that you can install Win 7 without any reserved partition using only the official tool (I've done this at least twice).

On earlier versions of the installer, the partition was 100 MB large only.

Sometimes I use Gparted to clear the disk before install. I had issues when trying to create Windows partition in Gparted before installing. The installer didn't accept the partition if I remember correctly.

Anyway, looks like you can create this partition without re-installing Windows.

Here

I tried your fix with the drive letter and fsutil just to have tried the only solution which is not smashing MBR.

I have the 100MB system reserved partition which was installed by Win7 Ultimate.

No other tweaks (you wrote about gparted ;-)  ).

The reserved partition has 71.6MB free from 99.9MB.

The above fix did NOT work on my dual boot system.

So I am still excluding KB4474419 from updates.

The problems with the April 2019 updates are showing, that MS has some problems here anyway.

Which means: waiting till MS fixes this mess.

Today's monthly roll up security update (KB4493472) is producing the same result for me.  The update doesn't configure properly upon restart and so fails to install. I presume this is because the roll up includes last month's problematic Sha-2 security update (KB4474419). Great. So am I to assume that none of the new security patches in this month's roll up took? This is just getting worse. I am ready to disconnect Windows 7 from the WAN and consider it as secure is it is going to get. I planned to do that in January anyway.

I have dual boot Windows 7 32bit and Xubuntu 64bit on an older Lenovo laptop with a core2duo

The update would happen and on reboot it would get to 32% and then fail and revert to prevous settings.

Then I followed one suggestion I found in this forum. On reboot enter the cmos and pick the drive I want to boot from. This bypasses the Linux bootloader for that session and voilà succes. The  next boot went as normal through the bootloader. Everything is as it is supposed to be. I'm OK till next January. 

I also have 32bit win7 running in a virtual machine under ubuntu on another computer. That update happened without problems.

I f you really need win7 that might be a way to do it.

I have an idea. It helped me.

I have two systems on PC - Windows 7 Pro and Linux. The run is made using the GRUB-loader. Update KB4474419 had a crack setup at boot time via the GRUB-loader. I switched the download directly to the Windows drive, downloaded and autonomously installed update KB4474419, rebooted the PC and got the installation confirmation. Then returned to download the GRUB-loader.