On 2016-06-24 13:05, James Knott wrote:
On 06/24/2016 12:06 AM, Felix Miata wrote:
Billie Walsh composed on 2016-06-23 16:47 (UTC-0500):
I just did some Windows 7 updates on my dual booted Eepc and there was no issue.
The vast majority of Windows updates do not require Windows' boot partition be active. Occasionally one does.
W10 certainly has issues with dual boot Linux. As one who's made it a habit to avoid MS as much as possible, I've never had occasion to update Windows on my own computers. In fact, in my entire life, I've only had 2 computers that even had Windows installed (unless you include the Windows 3.1 "WinOS2" in OS/2). However, this computer came with W7 and the update would not run until the install DVD "repaired" the MBR. I also had another instance of W7 in a virtual machine, on my desktop system, and that required the DVD, as the regular update wouldn't run. On the other hand I also updated a friend's computer, but as she only had Windows 7, the update ran OK.
Read the links I provided. I dual boot my laptop with Linux and W10, and I can update that W10 system just fine (so far). Basically (for traditional MBR setup, not GPT): - Install Linux so that Grub is in the Linux partition, never on the MBR. - The partition that boots is the one marked "active" bootable. Set as default to boot the partition that holds Grub, and this one can boot Windows as a choice. - Alternatively, you can define as bootable partition number one, and Windows will boot directly without trace of grub. In this mode, you can run updates on Windows. To revert to Linux, you have to revert the boot mark with a live linux disk or *good* partition software in Windows. - Finally, so that you don't need to change the boot mark on almost every W10 update, replace the boot code with another one hacked to always boot a certain partition, the one that has grub installed, ignoring the boot mark, which is on partition 1 (that has Windows). See this post by Neil Rickert and his blog: https://lists.opensuse.org/opensuse/2016-04/msg01023.html +++................. In any case, here is the quick and dirty solution: echo -e -n '\004' > x ### should create x as a 1 byte binary 4 cat /usr/share/syslinux/altmbr.bin x > altmbr.4 ##### That creates the file "altmbr.4" which is based on the syslinux "altmbr.bin" generic boot code. It will always boot partition 4, regardless of the active flag. So now install that in the MBR, and set the active flag for partition 1 (to keep windows happy). And you will still boot with the grub menu. .................++- -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)