But then you can only boot Windows from grub menu.Īlways say no until proven that you only can boot Windows entry from UEFI menu.īuggy-kernel detected. With the file rename booting Windows from UEFI actually boots grub/shim as that is the only way with those systems. That is only for those systems where vendors have modified UEFI to only boot Windows. And then you are adding another boot manager with EasyBCD.ĭo not run the Boot-Repair rename. UEFI is a boot manager which lists boot options, grub is both a boot manager and a boot loader for Ubuntu. You do not have to use either Windows or grub to choose to boot, but can choose from UEFI menu or your one time boot key. UEFI then lists all bootable systems and you just set one as default. With UEFI every system is equal and installs its boot files into separate folders in the efi partition. I understand with BIOS why some may want Windows boot loader, as with BIOS you can only have one system in MBR and that one is in control Running boot-repair doesn't help since I run into the issue with the two grub screens and having to go to the BIOS to start Elementary's grub.
I would like to use the Windows bootloader to start Windows and Elementary, but I am running into the issues above.
Attempting to open either Elementary options results in the initial problem showing up again (this screen: ).Īt the moment, I am currently on Windows and hoping that I didn't break anything important. There are three entries - the default Windows 8.1, the Elementary OS entry I created, and the Elementary option that appeared after using boot-repair. I overwrote the MBR, which brought back the Windows Boot Manager (looks like this now: ). I moved a newly-created Elementary boot entry (it linked to some EFI file) to the bottom of the list and set Windows as the default OS. I booted to Windows and started EasyBCD again. Rebooting resulted in the same situation: having to exit from the initial grub screen, go to the BIOS to select the Elementary partition, and then go to the "actual" grub. I booted to Elementary OS and ran boot-repair again (report: ). However, when I exited to the BIOS and selected the Elementary OS partition, I was able to access Grub, which gave options for Elementary OS (the installed version) and Windows. Report: After restart, I saw the same screen again. When I returned to the Live USB, I disabled the Secure Boot option in boot-repair and repeated the process (and said yes to renaming Windows files). After reboot, I was confronted by the same screen again and still could not open Elementary OS. I retried boot-repair while saying no to renaming Windows files instead. Here is the report generated afterwards: įortunately, I was able to get to the BIOS settings after entering exit, and I was able to boot back to the Live USB. I was unable to open Elementary OS from here. After that process finished and I rebooted my computer however, I was confronted by this screen: I then booted back to my Elementary Live USB and ran boot-repair (as described at ) using the default settings (and I said yes to renaming Windows files). When restarting and attempting to open it however, I got the following message: I opened EasyBCD and added the Elementary partition to the Windows bootloader.
#REMOVE DUPLICATE WINDOWS BOOTLOADER WINDOWS 8#
To my surprise, my computer booted to Windows 8 after installation. Installation completed successfully and I rebooted the computer. Using the Elementary Live USB, I created a 4 GB swap drive and a ~60 GB root drive for installation other than that default options were used. I then disabled Fast Boot and Secure Boot (since the Elementary Live USB wouldn't load otherwise).
I followed the following instructions to the best of my abilities:įollowing the first thread, I shrunk my main partition in Windows 8 to make space for Elementary.
#REMOVE DUPLICATE WINDOWS BOOTLOADER WINDOWS 8.1#
I wanted to have the Windows 8.1 bootloader instead of Grub for personal reasons. Today I attempted to set up a dual-boot of Windows 8.1 and Elementary OS (based on Ubuntu), both 64-bit and using UEFI.
0 kommentar(er)
