Bcdedit /set {bootmgr} path efiubuntugrubx64.efi

As a long-time user of Ubuntu, I freshly purchased an Acer Revo One which came pre-installed with Windows 8 on a 60GB SSD. This time I made a decision to keep the license. I took advantage of the totally free upgrade to MS Windows 10 (I made a decision to execute a clean installation from a USB disc so I could manage the partitions on the SSD - I left enough space for a root partition). This installation worked fine.

You watching: Bcdedit /set {bootmgr} path efiubuntugrubx64.efi

Next, I set up a HDD and also proceeded with an Ubuntu 16.04 installation using a live USB.

I partitioned the disks as follows (I acquired this from GParted after booting from the Ubuntu live USB):

*

*

Basically I want:

both OSs to boot from the SSDUbuntu to usage the HDD for a nominal /house, swap partition and also /tmpa shared partition to which both Windows and also Ubuntu have the right to write to

I have actually no idea why /dev/sdb3 and /dev/sdb4 have acquired "msftdata" flags.

Secure Boot is enabled (I"ve read miscellaneous write-ups - some say have actually it disabled as soon as installing Ubuntu, some say you do not need to execute that). Fast Boot is disabled.

Ubuntu installs as meant however, upon reboot (having removed the live USB disk) the machine boots only right into Windows.

I have actually checked the BIOS and tbelow is no alternative to boot into anypoint other than the Windows Boot Manager (or the live USB disk when installed).

efibootmgr reports:

BootCurrent:0002 Timeout: 2 secs BootOrder: 0000,0002,0001 Boot0000* Windows Boot Manager Boot0001 ubuntu Boot0002* UEFI: SanDiskI noticed that tright here is no astedanger next to Boot0001 implying that is not "active". I have actually tried setting that active and I have likewise tried transforming the boot order so Boot0001 is first. I"ve even tried transforming BootNext off to 0001. None of these work-related. I did alert that changes to activate Boot0001 are reset on the next boot - so my changes are not being maintained.

See more: How To Eject Usb From Android, Android Pie: How To Safely Remove Usb Otg Drive

I read a number of posts which make number of recommendations:

Some say install Windows first, others say the reverse.Install Grub aobtain.Repair the EFI bootloader entries either manually (by mounting the EFI partition and also copying/renaming entries) or making use of Boot-Repair.

I can"t seem to affix a dump of the EFI partition, however here"s a fragment:

./EFI./EFI/Microsoft./EFI/Microsoft/Boot./EFI/Microsoft/Boot/bg-BG./EFI/Microsoft/Boot/bg-BG/bootmgfw.efi.mui./EFI/Microsoft/Boot/bg-BG/bootmgr.efi.mui./EFI/Microsoft/Boot/bootmgr.efi./EFI/Microsoft/Boot/memtest.efi./EFI/Microsoft/Boot/boot.stl./EFI/OEM/Boot..../EFI/Microsoft/Boot/en-GB./EFI/Microsoft/Boot/en-GB/bootmgfw.efi.mui./EFI/Microsoft/Boot/en-GB/bootmgr.efi.mui..../EFI/OEM./EFI/OEM/Boot./EFI/OEM/Boot/boot.stl./EFI/OEM/Boot/bootmgfw.efi./EFI/OEM/Boot/bootmgr.efi./EFI/OEM/Boot/memtest.efi./EFI/OEM/Boot/BOOTSTAT.DAT./EFI/OEM/Boot/BCD./EFI/OEM/Boot/BCD.LOG./EFI/OEM/Boot/BCD.LOG1./EFI/OEM/Boot/BCD.LOG2..../EFI/OEM/Boot/en-GB./EFI/OEM/Boot/en-GB/bootmgfw.efi.mui./EFI/OEM/Boot/en-GB/bootmgr.efi.mui..../EFI/ubuntu./EFI/ubuntu/fw./EFI/ubuntu/fwupx64.efi./EFI/ubuntu/grubx64.efi./EFI/ubuntu/grub.cfg./EFI/ubuntu/shimx64.efi./EFI/ubuntu/MokManager.efi./OEM./OEM/AcerOA30.xml./OEM/Factory./OEM/Factory/AMIDEWINx64.exe./OEM/Factory/AMIFLDRV64.sys./OEM/Factory/CHK.bat./OEM/Factory/CHK_DK.bat./OEM/Factory/Delay-Diags.exe...I recognize I"m close to cracking this nut, so which of the over suggestions is most likely to work? I"d fairly not acquire right into the situation wright here Windows no longer boots and having actually to start aobtain. It takes a lengthy time reinstall every little thing.

Success of a type.

My BIOS was out of date, so I updated that.

I likewise offered Boot-Repair from a USB boot disk to repair the EFI boot partition (I"m not certain it was broken at all).

I then tried
fords idea - running bcdmodify within w$ - Success! Grub is displayed via a plethora of options - Ubuntu being the default.

See more: Sharp Tv Input Selection Not Available, Tv Will Not Change Inputs

This is all pertained to nought as soon as I rebooted right into Windows which, upon shutdvery own, made a decision to use an update which quit Ubuntu from booting. (deep sigh).

All I acquire is a few lines saying I try

sysctl rebootor

sysctl defaultsneither of which did a lot.

Did the Windows upday unperform the Windows bcdmodify and/or Linux Boot-Repair? If so, how do I prevent Windows updays from wreaking havoc on a everyday basis?