81chevette
August 8th, 2017, 11:28 PM
My computer has two OS drives plus a data drive. One drive houses Windows 10. The other drive is partitioned for my current Ubuntu version--currently Wily--plus another flavor for me to play with. I've determined, after much pain and heartache, that problems I have properly updating Windows 10 are related to GRUB2's redirect of the Windows bootloader. So I came up with a simple solution. I'd leave GRUB2 alone on my Linux drive, and then when Windows was struggling with an update I'd change my boot order in BIOS. (Actually BIOS; my mobo is too old to UEFI)
Well, much to my horror, I discovered GRUB does something that I don't entirely understand. My Windows drive has a redirect to GRUB2. One that even a "refresh" (where Windows allegedly reinstalls itself without installation media) didn't remove. So if I change my boot order I still end up booting with GRUB2, and if I unplug my Linux drive, I can't boot.
So I have two questions. One, how do I fix this? I want the ability, when I feel like it, to boot to Windows without GRUB2 touching it. Two, how do I KEEP it fixed? How do I keep a future update-grub from replacing the redirect? I do want to use GRUB2 most of the time, I just want to have a workaround available for when Windows Update gets stupid on me.
Well, much to my horror, I discovered GRUB does something that I don't entirely understand. My Windows drive has a redirect to GRUB2. One that even a "refresh" (where Windows allegedly reinstalls itself without installation media) didn't remove. So if I change my boot order I still end up booting with GRUB2, and if I unplug my Linux drive, I can't boot.
So I have two questions. One, how do I fix this? I want the ability, when I feel like it, to boot to Windows without GRUB2 touching it. Two, how do I KEEP it fixed? How do I keep a future update-grub from replacing the redirect? I do want to use GRUB2 most of the time, I just want to have a workaround available for when Windows Update gets stupid on me.