This worked for me.
sudo grub-install
after that I was able to go into the bios and select manjaro as the default efi boot device.
Why? Because it doesn’t work on Linux?
It is not supported at all on Linux - but if enabled - at least to my knowledge it will create problems - but I have not been able to verify - so kind of - better safe than sorry.
1 Like
This looks very useful, but I’m a bit stuck on the “Firmware checklist for EFI Systems” section. There are a number of directives there but no directions as to how they may be accomplished. I have a brand new Acer Spin 5 laptop. Looking in the BIOS I see that RAID is disabled, but Optane Memory is not. Searching for information about Optane Memory I find what appears to be an authoritative reference -
But this looks like a major low level intervention to me. I’m pausing at this point.
The implication of all this appears to me to be that I cannot just wipe the SDD drive and load linux, because there would be some kind of memory access problem. Has dual booting, or loading a straight Linux system really become this difficult?
Something to do with CTRL+S in BIOS. Read these comments on Acer community:
Thanks for the speedy response! I’ll jump on it very soon. Looks promising.
This is all accomplished with your systems firmware setup.
There is a lot of different systems - it is not possible to describe in details how you should navigate any given firmware.
Windows will work - as there no evidence to the contrary - even if you disable Intel Optane.
No - it is not difficult - but some major players are creating obstacles - some may say deliberately - to keep their eco system intact.
These documents are taken from topics on the now archived forum - posted by @Wollie and @c00ter
These documents is how to install / activate RST / Optane - so reversing the settings should disable it - in theory - that is
1 Like
Thank you so much for your quick response. I now have Manjaro installed, but a master key decryption lockout problem has arisen. I’m taking that to the appropriate forum. Thanks again for your detailed help.
Bitlocker?
To my knowledge Windows Bitlocker requires Secure Boot.
Manjaro do not support secure boot OOB so when disabling Secure Boot - BitLocker stops functioning.
You can read more on Secure Boot on the Archwiki using this link
Thanks so much for this guide! Long-time windows user thinking of changing to Linux here and thanks to your guide I finally made the jump.
However, after installation I had tremendous problems booting into Manjaro automatically even with @gohlip’s guide. The Manjaro boot partition was working but not showing up in the boot options in BIOS (UEFI). What solved the problem for me was flagging the boot partition with esp using gparted. Afterwards everything worked perfecty.
So, maybe it should read:
-
EFI PARTITION
Skip if using BIOS/MBR
Select the unpartitioned space → Create
a. Size → input 512
b. Filesystem → select FAT32
c. Mountpoint → select /boot/efi
d. Flags → check boot → OK
e. Flags → check esp → OK
2 Likes
Very helpful
I’m impressed with the amount of effort and detail that has gone into this
It’s been a while since I’ve had to install
I must admit to just skimming this to find what I needed and forgetting the need to choose the uefi version of the installer. 
Got there in the end though
Many thanks
2 Likes
Some parts has been added over time - but yes - it can be quite overwhelming.
1 Like
I followed the instructions but only windows kept booting.
The solution was to boot to manjaro with usb stick by entering the following grub commands:
grub> search.file /etc/manjaro-release root
grub> configfile /boot/grub/grub.cfg
then i had to install gparted to change the efi partition’s flag to “boot” and “esp” (It was “legacy_bios” which weird because i checked the “boot” flag when installing).
Then I run these commands in the terminal:
sudo pacman -S grub
sudo grub-install /dev/sda
sudo update-grub
and voilà.
1 Like
I feel this guide should be a bit more informative about the bcdedit /set {bootmgr} path command that is entered in the command prompt if the computer boots into windows 10 after the manjaro installation is done.
Setting the {bootmgr} path with that command creates another duplicate boot device and the issue is that it is named similarly as the windows partition’s boot device. You end up with two similarly named boot devices and well selecting either of them will still boot you into windows which is fine for most users.
But for those who wish to have an single windows partition boot device and no duplicates make sure that after you have installed and rebooted to manjaro OS successfully, boot back to windows and open command prompt with admin privileges. then type the following:
bcdedit /set {bootmgr} path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
Press enter after typing the above command and this will remove the duplicate boot device. Another thing is that the path that I have given above can vary, so make sure you check on another PC running the same version of windows 10 for the path.
Type bcdedit in a command prompt with admin privileges and get the path of the boot manager on the other PC.
Now this duplicate boot device cannot be erased by any software and even removing it in the PC’s BIOS also ends up restoring the duplicate device once windows boots up. Some users end up deleting the device with one of the bcdedit commands itself which screws up windows boot manager.
That set path command is modifying windows boot manager to load GRUB and when users delete this device thinking its related to manjaro, windows loses its boot manager and the PC cannot boot into windows.
So yeah I hope this reply of mine helps out someone facing this same issue of duplicate boot devices. also once the manjaro installer asks for a reboot, uncheck the reboot now box in the installer and manually restart from manjaro’s start menu. then when the PC is going to boot, hit ESC key and boot into the newly created manjaro boot device. this should complete the installation without ever going into windows and requiring you to set the {bootmgr} path.
1 Like