Dual boot Windows 10 and Ubuntu 15.10 Linux on HP Envy 13 D008NA

My eldest daughter has flown the nest and gone to university. For her first term, she took her trusty 7 year old Acer Aspire netbook with her. With an unofficial memory expansion and a conversion to Ubuntu, it’s seen her through both her GCSE’s and A-Levels, and is still going surprisingly well for its age. However, it’s really well past the time for it to be retired, and my daughter deserves to have something a little significantly more stylish and capable. She didn’t want an Apple, and wanted to keep Ubuntu as her primary OS. She also felt that keeping Windows available (as it would certainly be preloaded on anything we bought) made sense in case she needed it for anything specific.

So after a fair bit of investigation I bought her an HP Envy 13 model D008NA. This is a beautiful metal-bodied Ultrabook with the latest Intel Skylake Core i5 processor, 8GB of RAM and a 256GB SSD, preloaded with Windows 10 Home 64bit. A trial of the latest Ubuntu linux (15.10) from a “live USB” works well, with only the built-in fingerprint reader seeming to be unsupported, so getting it running Linux and Windows 10 in a dual-boot configuration certainly looks possible, though there are a few roadblocks to overcome:

  • Microsoft no longer supply a Windows Certificate of Authenticity with OEM (preloaded) computers, so there is no visible indication of the Product Key for the preloaded Windows 10
  • HP don’t supply install media (only the ability to recover to the “factory state”)
  • The HP recovery process uses hidden Windows partitions on the laptop SSD
  • This is designed and shipped as a UEFI-only system

But we like a challenge! There are two approaches to this problem; either shrink down the existing pre-installed Windows 10, and install Linux next to it, or start from scratch, wipe the SSD, and install new copies of both operating systems. It turns out that HP (in common with most suppliers of consumer IT) ship their preloaded Windows 10 with quite a lot of bundled “trial” software that we don’t want. So my ideal endpoint is a fresh install of bare Windows 10 Home 64 bit, with a fresh install of Ubuntu Linux 15.10 64 bit, in such a way that both coexist happily, and are easy to keep up to date (especially as Ubuntu 16.04LTS isn’t far away now). So, that means finding Windows 10 install media and the product key. It also means finding a way to recover the laptop back to factory state (in case everything goes badly wrong) that doesn’t depend on the internal SSD, as I’ll be overwriting that. And then there are the usual problems of getting Windows to coexist with another operating system, complicated by the need to do everything within a UEFI context. For me that means having Grub be the system Boot Manager, which will then start either Linux or Windows (actually, it will chain to the Windows Boot Manager, which will do nothing but seamlessly start the single instance of Windows).

Getting hold of the Windows install media turns out to be trivial. Microsoft now make them freely available for download. Thankfully I can also get the full version, rather than the European-legislation compliant version that needs post-install updates to provide full multimedia functionality. Turning that ISO into a bootable USB key was harder than expected, but eventually I found this tool called Rufus. Since this is a UEFI-based system, it’s essential to get the options right, and because of a “glitch” in the Rufus tool’s GUI, you also need to get them right in the right order! The trick for me was to specify the USB device, then select the ISO, then specify the partition scheme (which needs to be GPT only), then the filesystem (NTFS). That (and only that!) combination produces a USB memory key that can be booted by the HP.

The product key was a concern, but after a lot of reading, it seems that the way this now works is that the manufacturers burn the Product Key for the preloaded Windows into the NVRAM of the motherboard at manufacture time (for interest the standard defined by Microsoft is available here). The good news is that NeoSmart Technologies provide a free tool to read that information out. So now I have the Product Key to activate Windows 10 Home 64bit, although if I understand the process correctly, I shouldn’t need it, as Windows should be able to detect and use the license key that is embedded in the hardware without any intervention on my part. See posts 10 and 11 of this thread for some really useful background to how Windows licensing and activation really works.

Next problem was how to get factory recovery working without access to the SSD. As it happens, we have warranty cover that would get us out of that hole if the worst came to the very worst. But I’d rather not have to call on HP (and the delays that would entail) if I need to just reimage the laptop. Fortunately, a little Googling revealed this HP Support Page that explains the options available. It turns out that it is possible to create a set of external recovery media, using a preloaded application, that is buried somewhere in the Windows 10 menu system (or possibly behind one of those strange, rotating blocks that Windows 8/8.1/10 seem so keen on). Anyway, 20 minutes with a 32GB USB memory stick, and we have a bootable recovery solution that ought to be able to reimage the whole laptop back to “factory fresh”. Result.

So now it’s time to take a firm grip of the keyboard, and start changing things. In particular, I need to check that I can restore the laptop back to its factory state. If that doesn’t work, then now is the time to invoke the HP warranty process! Fortunately, booting from the recovery USB key works perfectly, and restores the laptop back to it’s Factory fresh state in about 40 minutes.

With that reassurance, I booted into the Live Ubuntu 15.10 environment, and using gparted I wiped the SSD. I then repartitioned it (using the GPT scheme) as:

  1. 250MB, FAT32, “EFIBoot”, flags=esp/boot
  2. 80GB, unallocated (eventually for Windows 10)
  3. 4GB, Linux-swap, “Swap”
  4. 18GB, ext4, “Root”
  5. 136GB, ext4, “Home”

When an OS is installed in a UEFI system it adds an entry to the EFI Boot Manager’s list of installed OS’s, telling the EFI Boot Manager where it’s EFI file is, and getting a unique reference number. I wanted to remove the entry for the pre-installed Windows 10 from the UEFI system (its stored in NVRAM, not on the SSD) to minimise the opportunity for later confusion. To do that, I installed efibootmgr by running the command sudo apt-get install efibootmgr, and then ran it with sudo efibootmgr. I then deleted the entry for “Windows Boot Manager”. On my system that was entry 0000, so I did that by running the command sudo efibootmgr -b 0000 -B. I was EXTREMELY careful not to remove any other entries, as I could easily prevent the system from booting by deleting the wrong entries.

And then I installed Ubuntu 15.10 onto the SSD, using the Swap, Root and Home partitions. Confusingly, the installer asks where the bootloader should be installed, but of course, as this is UEFI, the EFI boot code MUST be installed into the EFI partition (which is marked by the ESP/Boot flags). In practice, the Ubuntu installer knows this, and ignores whatever you tell it when installing in UEFI mode, but the dialogue is a little confusing.

Having tested that the installed Ubuntu system works, the next step is to install Windows 10. My first attempt to install Windows 10 failed, as the SecureBoot setting in the BIOS prevented the bootable Windows 10 installer from starting up. So I temporarily switched that off, booted the Windows 10 USB installer, and pointed it at the unallocated space that I left on the SSD. Windows then partitions that space into two partitions; a small one reserved for its own private use called the MSR, and the rest for the main Windows environment, ie the “C” drive. Unfortunately Windows insists on rebooting several times during the install process, and at this stage in the process it’s highly likely that those reboots will cause Ubuntu to start up, not continue the install of Windows. My approach was to “catch” each reboot by pressing ESC then F9, and then manually guide the reboot back to Windows again by navigating the UEFI firmware back to the Windows EFI bootmanager, which is at /efi/microsoft/boot/bootmgfw.efi in the EFI partition. As expected, Windows 10 never asked for the product key, and self-activated as soon as it connected to the Internet – which was remarkably easy.

Once Windows was actually installed, I followed advice I found on the Internet, and turned off the Windows “Fast Startup” feature while I did the final configuration of Grub. This is a Microsoft feature that caches system-state across restarts (similar to hibernating) so I’m not sure how this could interfere with reconfiguring Grub, but I figured better to be safe than sorry. I did this by:

  1. Open Control Panel (Win+X->Control Panel from the desktop in Windows 8+)
  2. Navigate to Power Options
  3. Click “Choose what the power button does”
  4. Click “Change settings that are currently unavailable”
  5. Uncheck the box that says “Turn on fast startup (Recommended)” at the bottom.

You should be able to re-enable Fast Startup after reconfiguring GRUB, but I’ve not bothered, as I’ve not noticed any significant change in boot performance with it turned off on this machine (boot times are incredibly fast anyway). At this point I shutdown Windows, and rebooted into Ubuntu. There I reconfigured Grub, changing the file /etc/default/grub to make Grub remember the last OS I booted, and it make it the default for the next boot, with a 15 second timeout while there is a visible OS Selection menu on the screen:

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
# GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

I then ran the command sudo update-grub to make those changes live, and to allow Grub to locate the Microsoft Boot Manager, and add it to it’s menu entries. This means that now when the system boots, Grub will get default control when the SSD is selected as the boot device. It then gives you the option to choose between Ubuntu or Windows 10, and will default to booting whichever was chosen last time. The advantage of this is that when Windows 10 runs its automatic updates sequences it expects to be able to reboot itself multiple times, and this Grub configuration will accommodate that requirement without someone needing to sit in front of the machine and babysit Windows through its updates.

Finally, I booted back into Windows, and downloaded the HP Support Assistant, which is supposed to manage updates for all the drivers on the laptop automatically. My experience was that it only downloaded and installed about 4 or 5 of the 15 or so required drivers, so in the end I manually downloaded and installed all the HP drivers for this machine. I’m hoping (but not hopeful) that now the right drivers are all in place, the HP Support Assistant may manage them all properly from now on.

Now I just have to transfer my daughters data over to the Linux partition, and install any required applications; an easy job.

Advertisements

21 thoughts on “Dual boot Windows 10 and Ubuntu 15.10 Linux on HP Envy 13 D008NA

  1. Hi I have a same laptop(Korean version of envy 13, skylake i5, 8g ram, 256g ssd) but preinstalled OS. I really hope to install windows10 64bit and Ubuntu same time on it but i got a problem with that. The problem is, when I type efibootmgr, it sais “efi variables are not supported on this system”. how can I solve this?

    • The version of Linux you are using needs to be 64bit, and I would recommend the latest version (ie, 15.10) too. Check to see if you have an EFI firmware available. There should be an entry called “efi” if you do “ls /sys/firmware”. If you do not have an EFI firmware available, then I would suspect that your Linux is not being booted in EFI mode.

      If you are booting a Linux that you have installed yourself, then check it’s 64bit, and installed on a GPT partitioned disk with a valid ESP partition. Otherwise you’ll be booting in MBR mode, and will not be using EFI, and will not have access to the EFI variables.

      If you boot the Ubuntu 15.10 64bit live CD, then install efibootmgr in that test environment, you should be able to use efibootmgr to see the boot entries, or “efivar -l” to display all the variables.

      • Oh. Mine was ubuntu15.10 with gnome and by reinstalling ubuntu 15.10 normal version, finally problem has solved. But dualbooting really works fine and i never understood what ‘entry’ means, so I decided not to touch that with efibootmgr.(can it be a future problem? But i am newb and afraid to delete something..) anyway, it works well. Thank you.
        p.s. It was “GRUB_DEFAULT=saved” not “GRUB_DEFAULT=save”

  2. Hi, I have already got this laptop and I also want a Linux dual boot (my case I choose elementary OS based on Ubuntu). My question is “how to enable the fingerprint scanner for auto log in in Linux?”. I am really interested in the use of the fingerprint scanner in Linux as well as in Windows… Thanks!

  3. Pingback: Best Linux Laptop: What are the top options 2016 - Pick Notebook

  4. Pingback: Best Ubuntu Laptop: 9 Top picks for 2016 - Pick Notebook

  5. Hi Richard, I’m finding your article very helpful. I am trying to install the new Ubuntu 16.04.01 onto hp envy 13.3 D061sa (no idea what the difference between sa and na models is… but that’s another issue)

    An i’m using a Kingston pen drive to test out the live bootable version of ubuntu however my issue is I can’t get it to initiate when I restart the computer I followed your instructions with Rufus to the T and have also disabled “secure boot” and turned off “fast start” any ideas?

    Thanks Jazz.

    • Do you mean that you can’t get Ubuntu to start from the USB drive, or you cannot get the Microsoft Windows installer to start from the USB drive? To prepare a Ubuntu Live USB drive you DO NOT need Rufus – simply use the methods that Ubuntu recommend, and it should work perfectly. See https://help.ubuntu.com/community/Installation/FromUSBStick for lots of details. The one thing I’d add is that sometimes you need to freshly format the USB key before you start for it to all work smoothly.

      In addition, the Microsoft Media Creation tool seems to work really much better now. So if you have an existing Windows system (the tool only works on Windows of course!), you can use that to create your Windows 10 installation USB drive, and avoid needing to use Rufus at all. Simply go to the Microsoft Windows 10 ISO download page, and it should offer you the option to download the tool, which will download everything it needs to build the USB drive for you.

      Hope that helps.

      • Thanks for the response Richard I will try to boot Ubuntu from the USB using the link that you have provided.

        • Hi, sometimes the fast boot of Windows 10 is an issue for dual boot or boot from a pen drive either. Check if you have the fast boot option activated in the control panel of windows. regards.

  6. Richard,

    Thanks for sharing this experience. I have learnt a couple of things from your piece. I am wondering if you will be able to point me to the right way to get Elementary OS 0.4 Loki (based on Ubuntu 16.04) to boot successfully from a USB thumb drive, given your experience.

    I have Envy 13-d022tu, which is a i7, Skylake machine. Naturally, it came with Win10. My eventual setup will hopefully be similar to what you have done but I will take it one step at a time by just doing a dual boot with Elementary OS, hopefully installed in a 16 or 32 Gb thumb drive. The ideal setup for me would be Elementary OS on SD Card but I have not been successful in booting from SD card on other notebooks I have tried in the past and I have come to understand it is very difficult if not impossible unless the BIOS support booting from SD card. In this case with the Envy 13, it does not.

    As a first step, I was only trying to boot from USB and run Elementary OS from the CD image. I managed to get the notebook to boot from USB by changing the boot order in the BIOS but Elementary OS will not boot completely. It hangs after displaying the Elementary logo. I have tried using the same USB drive in a Toshiba notebook and it booted successfully.

    I suspect it is the BIOS setting but having gone through all the settings, I don’t see any which may be a problem on my Envy 13.

    Any ideas or pointers would be greatly appreciated.

    • I’ve never used Elementary OS. It’s running the 4.4 kernel, so it’s got support for the latest Skylake processors, and your USB key works on other machines, so I’d guess it’s a problem with a missing driver for specific bit of hardware. I’d start by trying to see what kernel messages are being output.
      Assuming they are still using Plymouth to provide the graphical boot, then you can press escape as soon as the screen switches to graphics mode, and it should “toggle” from the Logo to a scrolling display of messages that you’d normally see from dmesg. That should let you see what it was trying to do when it hangs, and give you a clue about what you need to do to fix it.
      Hope that points you in the right direction. Good luck!

      • Richard,

        Thanks for the pointer. I figured out my problem. It was due to me not paying sufficient attention to ensure that Win10 fast startup was not disabled. Once I switched from Graphics mode, it was quite obvious from the messages displayed. I did encounter another problem after that with the USB hub which I had attached to my Envy13. I have a Orico USB hub (with SD card reader), that worked ok in Win10 but seems to cause a problem when I try to boot Elementary OS from it. Fortunately, I had the presence of mind to just try sticking the USB Stick into one of the 3 USB ports on the Envy 13 and bingo!

        My next step will be to install Elementary OS in a dual boot on the SSD. WIn10 and associated programs have already taken up almost 100 GB of the 256 GB on the SSD but I figure I can partition it and free up enough space for the Elementary OS and still leave enough space for any working files. I p/as no shrink the C: partition which Win10 is currently on and then just create the necessary partitions for Elementary OS. I figure in my case, this may be the least disruptive course of action.

        Over the years, I have tried Ubuntu, Linux Mint and now am more inclined to use Elementary since trying it 2 versions ago. I kinda of abandon Ubuntu in its original form after trying it on a sub-notebook some 6 years ago, having been largely disappointed by its performance. Linux Mint was ok for me on the desktop but for notebooks, I much prefer Elementary OS for its clean and very appealing user interface.

        I will be exploring your blog for other interesting articles on Linux in general and other stuff you are writing about. Thanks again!

  7. Is it okay if I resize the partition and then install ubuntu in it. I really don’t want to format my laptop since I have some important data that will require re downloading and don’t have time to download it.
    Thanks 🙂

    • Hi Wodin
      Sorry for the long delay in replying – I seem to be going through one of those “busy” periods!

      You ought to be fine shrinking down the Windows partition and installing Ubuntu in the resulting free space. I’m pretty sure that the standard Ubuntu installer knows how to do all that for you. HOWEVER, if you have critical data on the laptop then I’d strongly suggest a full backup first, just in case anything should go unexpectedly wrong.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s