[opensuse] Updating to Windows 7 on dual boot openSUSE 13.1
I'm trying to update (I refuse to say upgrade) the Windows 7 on my ThinkPad to W10. Apparently Grub interferes with the normal update method. I have created a DVD from an ISO I obtained from MS. I can boot from the DVD and install from it, assuming it doesn't also choke on Grub. Has anyone tried this? If so, did it clobber the existing Linux system? Also, I'm not using UEFI on that computer, though it is available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
23.06.2016 20:42, James Knott пишет:
I'm trying to update (I refuse to say upgrade) the Windows 7 on my ThinkPad to W10. Apparently Grub interferes with the normal update method.
Apparently in some cases Windows verifies that system is configured to boot Windows, which means that a) MBR has known Windows code and b) active partition is Windows boot partition. You may need to revert either (or both). Fixing active partition is easy. If you have to replace MBR code with Windows code, you obviously need to reinstall it. Note that it is not necessary GRUB - current openSUSE versions install Syslinux when you tell it to install generic MBR code; I do not know whether Windows tolerates it.
I have created a DVD from an ISO I obtained from MS. I can boot from the DVD and install from it, assuming it doesn't also choke on Grub. Has anyone tried this? If so, did it clobber the existing Linux system? Also, I'm not using UEFI on that computer, though it is available.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-23 19:55, Andrei Borzenkov wrote:
23.06.2016 20:42, James Knott пишет:
I'm trying to update (I refuse to say upgrade) the Windows 7 on my ThinkPad to W10. Apparently Grub interferes with the normal update method.
Apparently in some cases Windows verifies that system is configured to boot Windows, which means that a) MBR has known Windows code and b) active partition is Windows boot partition. You may need to revert either (or both). Fixing active partition is easy. If you have to replace MBR code with Windows code, you obviously need to reinstall it.
Correct.
Note that it is not necessary GRUB - current openSUSE versions install Syslinux when you tell it to install generic MBR code; I do not know whether Windows tolerates it.
Yes, it does. Check this thread: https://lists.opensuse.org/opensuse/2016-04/msg00975.html In particular: https://lists.opensuse.org/opensuse/2016-04/msg01023.html -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2016-06-23 22:34 (UTC+0200):
Andrei Borzenkov wrote:
James Knott composed:
I'm trying to update (I refuse to say upgrade) the Windows 7 on my ThinkPad to W10. Apparently Grub interferes with the normal update method.
Apparently in some cases Windows verifies that system is configured to boot Windows, which means that a) MBR has known Windows code and b) active partition is Windows boot partition. You may need to revert either (or both). Fixing active partition is easy. If you have to replace MBR code with Windows code, you obviously need to reinstall it.
Correct.
Note that it is not necessary GRUB - current openSUSE versions install Syslinux when you tell it to install generic MBR code; I do not know whether Windows tolerates it.
Yes, it does.
Check this thread:
In particular:
When one has astutely[1] installed generic MBR code in the first place, one only needs switch the boot flag to the Windows primary, boot and update Windows, then switch the boot flag back where it was, to the primary partition on which one has the Linux bootloader installed. [1] https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_u... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 05:28 PM, Felix Miata wrote:
When one has astutely[1] installed generic MBR code in the first place, one only needs switch the boot flag to the Windows primary, boot and update Windows, then switch the boot flag back where it was, to the primary partition on which one has the Linux bootloader installed.
[1] https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_u...
Actually, I was able to get the install going. The disc has a diagnostic function, which repairs problems it finds. So, it "repaired" the MBR and is now installing. I had previously saved the MBR, so I'll just replace it when the install finishes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-23 23:35, James Knott wrote:
On 06/23/2016 05:28 PM, Felix Miata wrote:
When one has astutely[1] installed generic MBR code in the first place, one only needs switch the boot flag to the Windows primary, boot and update Windows, then switch the boot flag back where it was, to the primary partition on which one has the Linux bootloader installed.
[1] https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_u...
Actually, I was able to get the install going. The disc has a diagnostic function, which repairs problems it finds. So, it "repaired" the MBR and is now installing. I had previously saved the MBR, so I'll just replace it when the install finishes.
You will have to do this often, every time Windows 10 fails to update itself. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/24/2016 06:24 AM, Carlos E. R. wrote:
Actually, I was able to get the install going. The disc has a
diagnostic function, which repairs problems it finds. So, it "repaired" the MBR and is now installing. I had previously saved the MBR, so I'll just replace it when the install finishes. You will have to do this often, every time Windows 10 fails to update itself.
Don't you just "love" MS. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/23/2016 03:34 PM, Carlos E. R. wrote:
On 2016-06-23 19:55, Andrei Borzenkov wrote:
23.06.2016 20:42, James Knott пишет:
I'm trying to update (I refuse to say upgrade) the Windows 7 on my ThinkPad to W10. Apparently Grub interferes with the normal update method. Apparently in some cases Windows verifies that system is configured to boot Windows, which means that a) MBR has known Windows code and b) active partition is Windows boot partition. You may need to revert either (or both). Fixing active partition is easy. If you have to replace MBR code with Windows code, you obviously need to reinstall it. Correct.
Note that it is not necessary GRUB - current openSUSE versions install Syslinux when you tell it to install generic MBR code; I do not know whether Windows tolerates it. Yes, it does.
Check this thread:
https://lists.opensuse.org/opensuse/2016-04/msg00975.html
In particular:
I just did some Windows 7 updates on my dual booted Eepc and there was no issue. -- Fast is fine, but accuracy is final. You must learn to be slow in a hurry. -Wyatt Earp- _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-24 06:06, 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.
Yep. Service packs, for instance, fail. Also the upgrade to W-10. And then, several upgrades in W10 fail as well, they are similar to service packs. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/24/2016 06:26 AM, Carlos E. R. wrote:
Yep. Service packs, for instance, fail. Also the upgrade to W-10.
Updates on W7 worked, but not the update to W10. BTW, calling anything from MS an "upgrade" is to be overly optimistic. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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)
On 06/23/2016 11:06 PM, 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.
Maybe I've just been very fortunate. Since 2000 when I bought my first boxed version of SUSE I've never had a Windows update mess with the boot partition. Upgrades, yes. Going from one version of Windows to the next has always messed with the boot partition. Not saying it can't happen on an update, it just never has for me. For the most part I have stopped dual booting as much as possible. Only my main laptop and my E are dual booted. I have matching desktops, one Linux and one Windows. Easier to switch back and forth when necessary and much simpler than a VM. Plus, I can do both at the same time if I need to. My Dell Duo is Windows only, I share it with my best half and she won't do Linux. And, it being part laptop and part tablet I am hesitant to try a Linux install. It probably would work fine but................... -- Fast is fine, but accuracy is final. You must learn to be slow in a hurry. -Wyatt Earp- _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-24 17:06, Billie Walsh wrote:
Not saying it can't happen on an update, it just never has for me.
On W7 it only happens with service pack updates. That is, once. But W10 has had at least 2 such updates (each takes several hours to complete, with very fast network). And a few "normal" updates failed unless W10 thought it had control of booting. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (5)
-
Andrei Borzenkov
-
Billie Walsh
-
Carlos E. R.
-
Felix Miata
-
James Knott