Updating to Windows 10 on a Dual-Boot System

I didn’t want to wait for the Windows 10 update to be pushed to my development machine so I opted to use the Media Creation Tool to update Windows manually. At least I tried to do so.

My first problem was receiving the very useful error: “Something happened”. Having downloaded the media creation tool, I ran the program and selected update this machine, only to produce the noted error. Microsoft’s programmers might as well have indicated that “nothing happened” because, essentially, nothing did.

I tried again to run the media creation tool thinking that, this time, I would download the ISO file and create a bootable USB drive. I couldn’t even do this without a something-happened error! However, this time it gave me a 0x800… error code that I could at least run through Google.

The fixes suggested on the web included running the media creation tool as an administrator which didn’t work, and running it under an administrator’s account – which did! I don’t know why MS in its wisdom couldn’t do better than “something happened” in this scenario but, when running as an administrator, the update to Windows 10 went smoothly. Well, at least as smoothly as possible, given the multiple reboots required to make the process continue to completion.

Initially, I was congratulating myself since, not only was my machine now running Windows 10, but the grub menu remained intact and I could also boot into Linux Mint.

However, such success was short lived. I quickly discovered that my dedicated data partition (DataDisk in Linux and Drive D: in Windows) wasn’t being mounted automatically when booting into Mint. Or, at least, it wasn’t being mounted at the expected mount point.

Running the blkid command revealed that DataDisk had changed from /dev/sda6 to /dev/sda7 as a result of the Windows 10 update. This was quickly rectified by editing the etc/fstab file to use the new partition designator.

A check on the pre- and post-update partition layout showed that the update to Windows 10 had added a 450 MB partition (that was unused) between Partition 5 (the Windows C: drive) and (the now) Partition 7 (the Windows D: drive – and the Linux DataDisk!)

So, two “tricks” to perhaps bear in mind if updating to Windows 10 on a dual-boot Windows/Linux system – run the update under an admin account, and watch those disk partitions.


Installing Windows 10 using the media creation tool

Forget the blue screen of death, Windows 10 has the silliest error message yet

FIX: Something Happened – Windows 10 Installation Has Failed

What is this Recovery Partition for on a fresh installation of Windows 10?

This entry was posted in Installation, Mint, Windows and tagged . Bookmark the permalink.

2 Responses to Updating to Windows 10 on a Dual-Boot System

  1. My advice is forget about Windows 8 and Windows 10. They are horrible and not the Original Windows of Bill Gates. When Bill Gates was asked about Windows 8 he just shook his head.

    • Alan German says:


      Since LinuxNorth is really about Linux and not about Windows, this isn’t the best (or right) forum to give advice about using specific versions of Windows. The main point of my post was to indicate that the partition numbering scheme in Linux changes when (and if) Windows 10 is installed. Some people need to use Windows for particular reasons. Some of them – including me! – spend much more time in Linux. But, whichever OS is being used, it’s just an OS. It’s not worth getting bent out of shape about. If you don’t like – or hate – Windows, there are several hundred Linux distros to choose from!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s