Would just like to say thank you very much for the F3 notification. I was struggling getting CLOVER to boot from the USB with windows installation media, when i pressed F3 i got an extra option called "boot from EXTERNAL USB" or something, and then the boot started from the OS.
I have the motherboard MSI 990FXA-GD80 which is AM3+ and have bios 13.6 The bios can see the NVMe M.2 drive fine, but refuse to boot from it. I was even able to install the OS but got a bluescreen.
The PCIe M.2 card i use is ICY BOX PCIe card with M.2 M-Key socket for one M.2 NVMe SSD product ID: IB-PCI214M2-HSL Drive i have added is Kingston A2000 500GB NVMe M.2 SSD / M.2 2280, PCIe 3.0 x4, NVMe, 3D NAND, up to 2200/2000MB/s, 350TBW
Going from 30-60MB/s transfer rates to 1600 READ and 1400 WRITE is such a big difference in responsiveness of the OS.
Would just like to thank the author for this article, although it should be updated as there is no 64-bit named nvme file to copy in Clover. Just a simple named file without 64.
PRIOR to using CLOVER, my NVMe mostly stated an error during Win10 installation specifying i could not install anything on it AND boot.
So i use CLOVER running from internal drive with 200MB, as SATA, and then it loads Win10 as OS.
This imo is a much better solution and far less complicated than risking bricking a bios in an attempt to make a custom BIOS.
Thnx for this. Saved me from buying a new computer when i only wanted this as extra.
I just noticed something… After i booted to Clover, then installed Windows successfully, i got a new entry in the Bios called "UEFI: WINDOWS BOOT MANAGER" and clover is no longer primary boot device.
So seems being able to boot with Clover, to initialize NVMe driver installation created a new UEFI entry in BIOS?
Hi all, I just wanted to report that I was able to get this successfully working on a HP Z400.
Casing: HP Z400 Power: Corsair RM750x 750 Watt Mainboard: Foxconn Intel X58 Chipset Processor: Intel Xeon X5690 12M Cache, 3.46 GHz, 6.40 GT/s Memory: 48GB DDR3 1600MHz RAM 2Rx2 PC3L-12800E ECC Unregistered (6 x 8GB) Graphics: Gigabyte AORUS Radeon RX 580 8GB NIC: Broadcom NetXtreme Gigabit Ethernet Controller: Akasa AK-PCCM2P-05 PCIe x16 to M.2 Storage 1: 1TB KINGSTON SA2000M8 M.2 Storage 2: 500GB Samsung 860 Evo 2.5 inch SATA III DVD: HP DVD-ROM TS-H353C
The whole thing was pretty painless. I did ran into an issue with Windows not installing from the USB stick using the Clover bootloader. However, when I booted from a DUET_EDK2020_REFIND USB stick, the Windows installation went fine. Once Windows was up and running, I tried the Clover USB stick again and it successfully booted to Windows. Finally, I moved the Clover bootloader to a SATA SSD and the system is now automatically booting to Windows without the Clover GUI. You can’t even tell anymore that there is an additional bootloader between the BIOS and Windows. Very, very, nice! Thing of beauty!
Hi Shonk your EFI files work great i’m booting from them o problem would like to ask you if there is way of either shotening down the 5 second automatic boot or getting rid of it. Thanks for all your work.
Good day. Thank you for this forum. I bought an NVMe disk and I didn’t know I would have a big problem. Finally, I managed to create a USB BOOT, through which I was able to install WIN 10. It works without problems. Translation created through GOOGLE Translator.
Hallo guys, im new to this forum. First off i appreciate your commitment to this topic. I’m impressed how helpfull some people are, and i think that should not be taken for granted.
@sibliss I followed your post for the clover installation but i ran into a problem. I installed my PCIe SSD, set it to gpt, formated it, downloaded BDU and installed clover on a thumbdrive. I followed your instructions to copy the NvmExpressDxe to both the bios and uefi directories and created the folders drivers32uefi and drivers64uefi with the driver in it. Then i set up my bios like in the original post and and changed the storage eprom to uefi. I don’t am able to disable CSM in the settings.
Now my problem: I boot into clover, but i don’t am able to boot the windowsinstallation drive. The option is displayed as “Boot Microsoft EFI cdboot from ESD-USB”. I select it but this ends every time in and error, stating: "Error: Time out returned from cdboot.efi" As i am really inexperienced in this regard i tried to edit the config.plist file. Specifically the key #DefaultLoader from “boot.efi” to “\efi\microsoft\boot\cdboot.efi” (I read another blog about this topic and they made something similar) but that also didn’t work. I tested the installmedia without clover too and could boot into it without a problem.
Why can’t i boot into the installmedia with clover and what could i do to fix it? This really stumbled me because many other poeple don’t have a problem with this step apparently.
My System: GA-Z87-HD3 with AMI UEFI BIOS, Intel i7-4770k, WD Black SN750 500GB, Lycom DT-120 M.2 Adapter, Kingston DDR3 RAM 8GB
I have no definitive answer why some install usb’s work and some do not i recommend just trying another usb untill you find one that works and people seem to have the most luck when they create it with teh Microsoft media creation tool.
Hi, i’m trying to boot my HPe ProLiant ML310e Gen8 V2 off of an M2. NVMe Drive. I am successful in the attempt of making a Clover BootLoader via BDU but i get a screen that says “6 _” when i boot from the USB Stick.
Hello, I just want to share my experience here, if you want to use WD_BLACK SN850, first update firmware of the NVMe. then it will go smoothly. without the update, NVMe will never appear in Clover/DUET menu.
@skyfire I too got this on my screen from one of my machines and from my research i suspect it’s something to do with boot 6 vs boot 7 i suspect it’s actually meant to say boot 6 but the rest is chopped of the screen for some reason. i was lucky that on mine it went away after a minute or so. and as such i haven’t really looked more into it. my guess is it’s failing back to boot 6 and for some reason hanging in the process but i have no further info and have been unable to find any about this. we may have to go to the creators of clover about that one.
i was really looking forward to getting it to work. there really isn’t much to debug on the bootscreen but that "6 _" that stays there. did you keep all 3 boot files on the usb stick (boot, boot6, and boot7) and waited god knows how long? i read in an FAQ that its the worst kind of hardware incompatibility. but if you’re able to make it work, then i suspect there’s more to it than just hardware incompatibility.
I just wanted to post a BIG THANKS to @Nyctophilia , @Fernando , and @Sybliss. What an effort to keep this thread alive and helpful.
After looong trying, and two fatal Win10 corruptions, I got this working too! The “Clover way”. I will still have to study all plist file settings to speed this up, but the NVMe SSD nicely boots now too. On an “old” (2013) Dell, yes. Like new. Thus environmentally conscious I am, indeed
The boot delay, currently, is still dramatic, as compared to my earlier SATA SSD boots. But I have freed that one up, and can use the larger NVMe SSD for speed-requiring things post booting.
Interesting (to me) is: For whatever reason, I now have it going like so with Clover: - Dell logo for a long time - then Intel booting something - then after a long time Clover menu comes up, with 6 (six!) “options” for booting (but it looks like most are the same, as per name underneath) - and then, when I’ve clicked (or now on auto) the right one of those buttons, then I yet get another menu, on blue background, with two large squares, asking me whether I want to boot my Win10 install on Volume 1, or on Volume 4?
I figured out the Volume 1 will boot the NVMe SSD, and Volume 4 the prior SATA SSD Win10 install. Funny thing is, Clover seems to have set this all up automatically, without my knowledge nor intent. It must have seen that I have two Win10 installations (at the time), and so decided to offer another (second) menu afterwards. LOL Well, I don’t know Win10 enough to say.
Now a SUB stick is sticking out where my legs are unfortunately, but yes, I have read some users’ posts here how they managed to install Clover bootloader onto the SSD as well. I might give that a try as well at some later point.
I’m having an odd issue where the speed of my NVMe drive is MUCH faster when tested as a secondary drive when booted from the existing SATA/Win10 install vs now booting from the NVMe/Clover combo… AS SSD score of 2300 vs 850. Anyone have an idea?
When I tried to boot from UEFI flash stick with Clover, I got a message: "The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [N] to run the next boot device, or enter directly to BIOS Setup if there are no other devices installed. Go to BIOS Setup > Advanced> Boot and change the current boot device into other secured boot devices" Any suggestions? Motherboard Asus P8H77 - V with the latest BIOS from Asus 19.05
@tinky thankyou and welcome to the forums, the second blue menu is actually the windows 10 bootloader and it’s auto detected the other windows installation you can actually remove the other option following this guide https://www.tenforums.com/tutorials/1487…up-windows.html
you can remove or hide the other clover boot options via the config.plist file.
the other logo’'s before the clover boot i’m assuming are bios logo’s you may wish to tweak some bios settings and see if you cant get it to pull up clover a little quicker.
@sibliss Great additional tips, that I didn’t even expect/ask, thank you Yeah, so before, with SATA SSD boot, it booted like it was always waiting for me: a felt 2 sec. Never timed though. Now, with Clover, before plist studying/optimizing, Win10 on the NVMe SSD is up after a felt 3 min or more. Never timed though (I just do other things after pressing the Dell button, lol).
Before I get down with plist, I am working on getting Win10 realize that the "Ethernet" (which Win10 labels wrongly, it’s actually Vodafone Mobile "Broadband" via antenna) IS plugged in. It requires me to pull out the USB and stick it back in. Every boot. No big deal. Online there are many, many references to the same problem (not with Dell, so seems universal with Win10). I reckon sth like the Startup sequence needs change that it looks a little later at the USB sockets. When I find out, I’ll post the solution here on Win-Raid.
