KB4474419 will not install

Anonymous
2019-03-14T00:02:37+00:00

KB4474419 will not install - error code 80004005

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

77 answers

Sort by: Oldest
  1. Anonymous
    2019-03-29T00:02:47+00:00

    I got the issue solved, but it was a long way. Here is what I did:

    Using the Windows Disk Management tool:

    • Shrink some partition on the disk to leave some free space. I left 512 Megabytes.
    • Create a primary partition whose label is "System Reserved", formatted with NTFS, marked active, and assign a drive letter to it.

    Using the Explorer, copy the file "bootmgr" from the partition holding Windows into the System Reserved partition. You might need to display system and hidden files.

    Using the Windows Disk Management tool, remove the drive letter assignment from the System Reserved partition.

    Using the Windows 7 installation media, boot into recovery mode, and start the MSDOS console. In that console:

    • Run "bootrec /fixmbr". Sorry, this will override your MBR...
    • Run "bootrec /fixboot".
    • Run "bootrec /rebuildbcd".

    Then reboot. Then install the update again. I used the "windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9" file to install the update immediately. Good luck.

    Comments:

    • Your MBR is now the Windows 7 MBR. You will have to restore dual/multiple boot boot loader if you need to...
    • Your System Reserved partition loads Windows 7. "bootrec /rebuildbcd" configures that.
    • Use "bootmgr" from your Windows partition instead of the one on the Windows 7 installation media, as it is likely to be more up-to-date.
    • 512 Megabytes should be enough, but you might be fine with less than that.

    References:

    [1] https://www.partitionwizard.com/partitionmagic/accidentally-deleted-system-reserved-partition.html#fix-2

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-03-29T00:43:10+00:00

    Okay good luck with waiting !  ;)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-03-29T19:06:48+00:00

    I am happy you had success, but this looks like a convoluted  work-around that has the potential to brick your installation. I am with  PMaffMS on this. Microsoft needs to provide a proper fix. One shouldn't have to jump through hoops to install a required update, unless of course the goal is to get users frustrated enough to not wait until January to switch to 10, assuming they ever will.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-03-29T19:18:55+00:00

    I should add that I am a dual-booter and I am aware of the method that some have used successfully to get the update to work. I know well how to use the Windows 7 disk to repair the MBR on the windows installation (wiping out the GRUB boot manger in the process) and then reinstall GRUB after applying the 4474419 update. But I have no intention of doing it, at least not before July. That is how long Microsoft has to correct this. I am a patient person.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-03-29T20:35:13+00:00

    It looks like many have tried different methods, but nothing works. The update clearly has bugs and needs to be fixed by Microsoft.

    That is also my opinion. There are dual boot and single boot systems and both fail so I will for sure not change anything with the

    boot drives.

    This is clearly a Microsoft bug and they have to fix it.

    So when can we expect Microsoft to fix this?

    Please name a time frame or date.

    My machine is always rebooting 2 times before I can access Win 7 Ult and this is absolutely senseless (I am using Windows only

    for gaming because this is the last and only reason to use Windows at all).

    PMaffMS

    To stop the looping caused by the doubling of configuration attempts and sucessive boot ups, go to the options page in wu where the file is housed, right click it and select "hide". You can always unhide it later. This will end sucessive bootups.

    I agree, after looking at all the back and forth about to handle this problem, it should not be expected that the average user should have to figure out how to make all these technical executions such as resizing paritions, et al.

    I started this thread and I'm letting it go till July. If M$ doesn't fix it by them, M$ is going out my 3rd story window.

    Mike

    Was this answer helpful?

    0 comments No comments