Windows 10 anniversary update alters partitions and disables Linux
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It appears to me that the folks in Redmond are a little ODC. Over the weekend I updated Window 10 on my Asus laptop which multi-boots Windows 10 along with three different versions of Salix; Salix64 14.1, Salix64 14.2 and Salix32 14.2. The laptop has a single gpt formatted disk using uefi CMS mode to boot. I also use rEFInd as my boot manager. Over the years, I have deleted and added many different versions of Slackware and Salix creating a somewhat jumble harddisk, meaning that the physical order of the partitions did not jive with the partition name(i.e sda6, sda7, sda8 etc).
Forewarned by this thread, I initiated the Windows 10 update. The update went smooth, at least from a Windows perspective. The update comprised of three separate steps, Coping Files, Loading Drives, and Configuring System. After each step the system rebooted and I was somewhat surprise to find that it did not muck with the EFI boot order. Each time it rebooted into rEFInd, which was the default efi image to boot. After the first step, Copying the Files, was completed, i tried to boot into the three Salix installations and was not able to boot two of the for what appeared to be a problem with loading the root files systems.
I was able to boot into the third Salix installation, Salix32 14.2, and once in I could see that three of my partition were re-named. My /home partitions for the Salix 14.1 installation changed for sda7 to sda6. The rootfs for this same installation changed from sda8 to sda7 and the rootfs for the Salix 14.2 installation changed from sda6 to sda8. This renaming aligns with the physical layout of the partitions. I eventually had to edit the fstab and elilo.conf files with the appropriate changes in rootfs partition names and was then able to boot into the systems without problem or loss of data.
The update did not touch my first three partitions, sda1 (ESP) sda2 (not really sure what this is, but it's small) and sda3 which is the main partition (C drive) for Win 10. The sda4 partition, which is Win 10 System recovery partition was apparently deleted and a new partition was created in its place since the UUID of sda 4 changed.
The sda9 partition which has the rootfs for the Salix32 14.2, was unchanged and therefore I was able to boot into this system with out making any changes. The last partition, sda13 (sda10, 11 and 12 had bee deleted by me prior to the Wind 10 update) which is the Win 10 Restore partition name was changed from sda13 to sda10. Here's a diff of the output of lsblk -f before and after the Win 10 upgrade:
Although the update did not destroy any data nor did it appear to make any new partitions or use up any more of the disk space, it would have been nice if the update would have at least informed me of these changes. I did find it somewhat ironic that during the first boot up to the newly updated Win 10 there was a banner screen that said:
I'm going to have to rethink my sharing a data partition on the same drive with Windows 10.
Lesson learned / thread solved?
You can't really expect much more from MS (or any proprietary OS vendor) in the way of supporting/caring about "dual booting". They ensure their own OS works and that's about it - it's safe to say that that's what 99.9% + of their customer base want.
"Dual booters" are assumed to be hobbyist/geek users who can just chroot into their broken system fix it up and get up and running again. In your case you could boot up, log in as root and fix it, so no harm done?
Despite all of this, with x86 hardware (designed for windows) it's easy enough, for those inclined to do so, to install other operating systems and "dual boot" or even "multi boot". Can the same be said for Apple hardware and Android based OEM devices?
Last edited by cynwulf; 08-10-2016 at 07:13 AM.
Reason: typo
Thank you very much laprjns for taking so many risks.
Now we understand what Windoze is doing behind the curtain, as usual.
I think that the banner
Quote:
All your files are exactly where you left them
is a joke by Microsoft. They obviously know what they programmed, so they know that if you are dual booting, you gonna have some work to do; so they are playing with your nerves.
I have 15 partitions on my laptop hard disk and the IDs are not in any particular order. So, I think I'm just going to remove Windows 10. Seriously.
Excuse me for my language: **** ***** **** ****** Microsoft!!!
My Windows 10 VM under qemu-kvm was a different story. It was like pulling teeth to get that upgrade to complete, but at least it couldn't affect anything but itself.
Hello,
I'm struggling to update my VM, what did you have to do?
I'm struggling to update my VM, what did you have to do?
First try locked up when Windows tried to shut down for reboot. Had to force power-off in the VM. On a hunch that the virtio disk drivers might be an issue, I switched those to IDE. (I have a separate drive just for swap -- no point in backing up that image.)
On the second try, Windows insisted on downloading the whole update again, but this time it got through the shutdown steps and got stuck in a loop during early reboot with no keyboard or mouse response. It eventually responded to a shutdown signal sent from the VM toolbar.
Upon rebooting, it completed the installation and presented the greeter screen, but with no response to the keyboard. With the mouse, I was able to activate the on-screen keyboard and log in successfully. Rebooting from there (via the mouse), Windows 10 finally came up normally. I was then able to shut down and put the disk drives back in virtio mode.
I just got the Anniversary Update. Win10 resides on a SSD which, besides the Windows partitions, have a set of root (/), /home and swap partitions. I manage booting with Grub2. All were left untouched and I am posting this from Slack as we speak. Thankfully all went smoothly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.