Grateful...
Hopefully there's no partition resizing and MBR tomfoolery out of this at all cost, especially since it is happening to people who do not have a dual boot system. Anyways, Win7 Ultimate x64 is on the third partition of the drive its on for me, so even that would not help at all.
Does anyone have any idea when Microsoft will fix their total screwup regarding the installation of KB4474419?
After an extensive survey of forums on the net it is clear that the fault lies with Microsoft. I have a dual boot computer which I use for research and development. It is not a trivial setup and system reinstallation and configuration is at least a month's work. I am not about to play around with the boot manager or partitions.
It baffles me why MS's update should concern itself with my boot manager or partitions.
I find this an ugly end to a long and happy relationship with MS, and a display of unprofessional behavior. As a long term professional user of MS products, I and I believe others, place our trust in MS that their update process will not harm our computers or otherwise make them unusable. We use these devices to make our living.
This trust is now broken and I think it about time MS admitted their fault and fixed the problem.
So I do not have Windows 7 Ultimate but I'm on Windows 7 Home Premium dual booting with Linux. I finally managed to get the updates to install properly after looking at these forums for a week. All I had to do was to go into Windows 7 and under Disk Management right click the partition that has Windows installed on and click Mark Partition as Active. Updates went through even booting Windows in GRUB.
I'll wait and see what the moderator has to say about the CBS.zip, but if that does it...I guess I could try, it's not active by default? Also, I have Minitools Partition Wizard Technician Edition 11.3 or such, I rather do anything partition related there, I'm guessing I could be doing this.
Thanks for the tip,
but I'll wait for now, it's not an emergency until August..
Did not work for me. I marked the partition as active and Grub still worked so booting windows is not broken, however the update still fails.
I really did think Microsoft employed professional engineers. Seems I was mistaken. Amateurs all around. To break customer's computers with a faulty update is completely unacceptable. We make our living with these computers.
the CBS.zip didn't tell you anything?
I've installed the april updates fine, but I'll be going back to Linux Mint or Ubuntu MATE permanently if I can't get it to work before the August deadline. Which means a lot of data moving, formatting...thankfully I got a VPS where I can dump everything and download everything back, so in theory, I could give win7 its own partition and see what happens, but I won't be doing so until all avenues haven't been looked at. There's other things I have seen where people say they have succeeded in installing it, but that would mean that if it fails, reinstall would be mandatory. There's no way to make a backup right now, the C:\ partition is 530gb large, I got 3 1TB externals and they're 3/4 full, all stuff that goes back to the early '00s since I got cable modem way back in 1999 maybe even. If that means I'd have to buy another external drive...I'd have to get a pci to e-sata, usb 3.0 isn't fast enough.
The idea works for me and I simply provide further clarification.
I run Clover to dual boot (legacy boot) MacOS X (hackintosh) and Windows 7 on the same disk with MBR partitions. Initially marking Windows partition as Active caused me problem because the system failed to boot and I had to run Gparted to remove the 'active flag'. Then I remembered when I set up Clover to boot Windows, I needed to choose the System Reserved partition in order to work. So next I marked System Reserved partition (Windows) as Active and the system booted directly to Windows bypassing Clover. The update KB4474419 went through successfully and subsequently KB4493472 as well. Finally, I removed the active flag from the System Reserved partition and everything is back to normal with Clover menu coming up where I can choose to select Windows or MacOS. I didn't bother to change the MacOS partition back to Active as it doesn't seem to matter.
So in my case, it is a simple change without the risk of corrupting the boot loader already installed. Hope others may find it useful.
I wish to thank monkeyfarts and his post #23 for help in solving the issue on my PC.
Finally after lots of attempts since last March I succeeded to install KB4474419 on a Win 7 Pro x64 PC in dual boot with a Debian distro.
Me too with 'Failure configuring Windows updates. Reverting changes.' alert and 0x80004005 - E_FAIL Unspecified error
I found that moving the Active flag to the Win partition is the correct and, let me say, elegant solution (before this change the flag was on a Linux partition, because Linux was installed after Windows on my drive and so the flag went there).
There were no need for me to alter Grub configuration or boot device order in UEFI, or to change the boot loader back to the Win one.
I also stopped 3rd party firewall software during the update but the Active flag made the difference.
This change doesn't affect Win or Debian boot, and there are no collateral effects as I can see.
Hope this helps.
Quote