On 2016-04-21 22:57, Dennis Gallien wrote:
On Thu, Apr 21 08:09:11 PM Carlos E. R. wrote:
Well...
I will try Neil's method first, and see what happens in a month or two. The problem updates are not all, and it is unknown in advance when a W10 update will cause this problem, so even if this method appears to work at first it will be no proof. Only if I see a service pack update will I know if it works. If it doesn't, I will then revert and use easyBCD instead.
I will try this tonight. Thanks!
Carlos, easyBCD will not help you. When you run the program, and as explained on the vendor's site, with W10 MS made some change which forbids a non-Windows OS from even being added to the bcd database. Consequently, the tools that update the W10 boot database can no longer even access those records or create any new (non-W$) ones.
ARGH :-( Yes, this is, I think, what I read somewhere, saying that W10 was not supported by easyBCD.
The vendor offers a couple solutions. One is to install grub to the mbr pointing your linux boot partition and then chainload from there to W10. Apparently you are already doing this, but that doesn't solve your upgrade problem.
No, this is not the method I use. I have grub in partition 4. I do not use this method because it causes problems on some Windowss upgrades. Having MBR generic, and grub in a partition, you can change the boot mark to the windows partition to make it temporarily happy during certain upgrades, and is easy to undo.
The other suggestion is to use another tool the vendor offers called Recovery Essentials. The vendor claims it can enable the system to use either the EFI or the traditional boot method, presumably switching back and forth between the two. Personally I would not use this without knowing first exactly how it works; the bcd is very complex and the MS bcd tool is a nightmare to use. It is not difficult to make a multi-boot bcd system unbootable.
In the past I had the same issue as you describe. Because easyBCD no longer works with non-W$ multi-boot, I used essentially the same workaround as you are now. My next step was to search for a different software tool, but a machine upgrade eliminated the need.
The method Neil posted looks promising. I have already made the changes, but I still have to reboot to test. And then wait for a service pack. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)