-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, First I explain how I have setup booting of this laptop. BIOS, not UEFI. Traditional partitioning. MBR: generic. partioning (numbers as in fdisk): 1 -> Win boot 2 -> Windows 10 3 -> old HP recovery 4 -> extended, marked bootable. Contains Grub loader. 5 -> swap 6 -> Linux /boot 7 -> root (/) (openSUSE 13.1) So, the BIOS loads the MBR program, this searches for the first bootable partition, sees it is #4, loads the first sector there, which is grub code, which takes control and boots either Linux or Windows as I choose. Now, the nuisance. When Windows (I boot it about once a month) tries to do certain updates (not others) it says that the update failed to be applied for some obscure reason (no, they are unable to figure it out in their help sites). I figured long ago that this is because it does not see partition #1 as bootable. Ie, that Windows is not in control of the boot process. When this happens, the remedial procedure is: Boot Linux, mark partition #1 bootable, unmark #4, boot machine, now without grub in the way. Windows downloads again the updates, reboots, applies them. Boot from external USB stick with Linux, and change mark back to partition #4 to reactivate grub. Boot machine now normally. With Windows 7 this procedure I needed to apply only once in years, for the service pack. But with Windows 10 this is happening more often: there has been a SP already, and another normal update that required this procedure. Twice in almost a month. This is becoming a nuisance. So I wonder if there is another method, where it is Windows which thinks it is in control and presents a menu asking what to boot. I have done this previously with Windows 7 and 2008, using a program for the purpose that configures Windows own boot system. But I have been told it doesn't work with Windows 10. I have not tried it yet, I have to find out first the name of such program, which I have forgotten... BSD or BSC, perhaps :-? Ah! It is BCDedit... No, easyBCD! The article in the Wikipedia is not clear if W10 is supported. I'll have to try, I figure. After I do a real backup. What do you think? Anybody tried this with W10? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlcX4+IACgkQja8UbcUWM1zE6AD9ElWK0CO2qPouACl/nNhNaILy OkiEz/X3KuK8jLo5nzgA/15RYV9Its6LVT+BpxwEHY7UxmdakQK4jxMWAUgKEPRn =QT48 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org