@tinky
Are you booting clover from usb ? In your circumstance i highly recommend booting clover from your sata drive instead. This should avoid any conflict with usb booting. The internet dongle issue sounds alot like a windows 10 driver problem with that dongle. And if so is probably not really clover related.
@sibliss
My plan is, later, to boot ALL from NVMe SSD, like a few others here wrote (at least I understood it that way).
Otherwise, yes, boot Clover from my SATA SSD instead of the USB stick at my knees, is a great idea too (as long as the Clover boot partition will not occupy the whole SSD, just needs to be set up right).
If you meant that the WiFi USB issue results from booting Clover from a another USB, then that’s sth I haven’t even thought of. Great idea. I gonna find out.
The internet dongle has the right driver though (is as fresh as the dongle) and it is being recognized just fine when booting my other Win10 install still on the SATA SSD.
So now I suspect that your idea of a conflict when also booting Clover from a USB is Spot-On!
Please don’t worry about me, I normally figure things out (even if it takes me three attempts like with Clover), hence why I chose tinky as username, lol.
You clearly have figured things out long before me, I am impressed! 
I am of that age who still learned programming a processor deep down (was 6502, I believe I remember) in the early 80ies, and my teacher gave me full marks on auto because he said he “can’t keep up with you” (he was primarly teaching math, back then teachers for “Informatics” were self-trained). Ah, the eighties was a time! First seeing the internet. How different. But today we’re being stopped and annoyed with all sorts of permanent popups and auto videos, phew! Luckily, and thankfully, Win-Raid has none of that disturbing stuff. Yet.
@tinky
Ah yes I’ve been in the computer profession since the 90’s myself. So am somewhat familiar with the processors you speak of replaced many in the 90’s.
On a side note it is not possible to boot clover from the nvme as the nvme driver to allow the nvme to boot in the first place is part of clover.
the clover partition is only 200mb and can be placed at the start of your sata ssd and keep using your sata drive as normal.
One small note is you should back up the sata drive before you use the bdu to create the clover partition on the sata drive as the bdu will wipe the whole drive … however after clover partition is created it is perfectly safe to partition the rest of the drive and use it like normal. This is how I am currently using clover boot on my personal computer.
If you read the comments back a few pages I do mention how to hide boot entries and even how to install clover to a sata drive via the bdu options.
Good luck and happy modding.
@sibliss
Huh sorry I only now realized there is actually a BIG Thank you button. I used it now 
"it is not possible to boot clover from the nvme as the nvme driver to allow the nvme to boot in the first place is part of clover." - Of course, how foolish I forgot that!
Yes I remember that. I will re-read it when I am about to wipe my SSD for BDU like you say.
And I’ll be back here beforehand with actual current boot time. I haven’t timed it still because I really rarely turn the computer off. Old habit. But I am curious myself to compare the two later. Then I’ve got sth to contribute 
here is a side by side… yes it is on a gen3 x1 bus but miles ahead of a SATA SSD "my 500gb 860 evo scored 1100"
@Black6spdZ
Did you end up figuring out your speed issue
not yet, can’t understand at all what would make such a difference… how new is the nvme uefi driver in the clover loader? I also have an issue where my laptop bluescreens when waking from sleep
@Black6spdZ
most people do not have this problem myself included, i am using a fairly new nvme myself and the driver seems fine so with that in mind i don’t think it’s a clover driver issue, I’m leaning more towards smbios
remember clover is a hardware emulator.
I’ll refer to this wiki page regarding emulation https://sourceforge.net/p/cloverefiboot/wiki/SMBIOS/
so if i made a semi educated guess i’d say there’s an issue with the emulation of the drive maybe ?
sorry i’m not much help on this i am no clover expert but i do what i can.
any way to bypass this Mac emulation? I may not be the only one here, has anyone else ever benchmarked their NVMe drives as a secondary drive before doing a clover boot/OS installation?
@Black6spdZ
There are options in the config.plist i just unfortunately do not know my way around the config.plist quite well enough to know exactly what we are looking for and which tags to edit.
Hi guys. Can someone please help because I cant even get clover to boot from USB no meter what method I try (BDU, Rufus, AIO, YouTube etc.). In tests it goes in boot loop on “booting from hard disk” and in real boot it goes to black screen and turns of my second screen. I didn’t touch config.plist but in wiki it states to let it auto config before trying to set it up. I have Win10 on pretty old BIOS only Asus M4A79XTD EVO, AMD Phenom II 6X 1070T, 16GB DDR3 Kingston, 2TB HDD upgraded with Radeon RX570 8GB, and 120GB SSD as C: drive that i was hoping to replace with 500GB NVMe Kingston A2000 over adapter. Adapter can also take M.2 Sata and I have one of 250GB as external if that helps.
hello @BlackAdder
and welcome to the forums.
I have actually used clover with much success on an m4a series motherboard and almost identical system specs to yours.
In order to best help you resolve your issues please first ensure you have done a few things on your system.
1. in your existing win 10 install ensure you can access the nvme drive as a spare storage drive this proves that the adapter card works as intended.
2. try a few different usb sticks and run the BDU from your windows 10 installation to create a few clover usb’s
3. remember to move the nvme driver file on the clover usb to activate it.
4. note that clover will only use/show on one of your screens.
5. insert clover usb and boot the computer do not remove the usb.
6. enter your bios and set your bios to boot from usb.
7. allow the computer to boot to clover from the usb. report here any errors
please refer to both OP #1 and my updated pined post see blue text in post 1 for details on how to do this.
Thx for welcome and quick and detailed replay. I already tried all of it before (and after) but didn’t remember the stupidest thing of all and that is old USBs (I’ve been mostly using external drives). Still no luck. 3 stick same behavior. I’ll get/borrow some newer ones and try again and report but in the mean time any advice about setting clover on 500MB Z: partition on HDD without having to format my entire HDD (D: and E: partition) as BDU would like to. That is the original plan, I wanted to get familiar with and learn Clover before any real work but I cant get damn thing even to boot into itself. And should I just migrate my C: drive or is fresh install better?
i’ve narrowed down the culprit… it must be the nvmexpress driver. i ditched clover and just use a basic efi shell and autorun to load the nvme driver then map new drive to shell and launch windows… same slow benchmarks however. I’ve tried 3 different nvme efi drivers that all perform just as bad. there is alot of performance being left on the table here probably for most using clover to boot from an nvme drive
Bump
So peculiar case. Got newer USB stick (unlike older ones bios reads it as generic mass storage) and managed to create and enter Clover using USBSetup program from this tutorial: [Guide] NVMe-boot for systems with legacy BIOS and UEFI board (DUET-REFIND) (2020 version is Clover), after that i managed to do the same on older stick and get clover to boot from new USB using BDU or this method. But next day after i returned to win and set up NVMe drivers in Clover i couldn’t enter Clover any more. Both new and old USB behave the same with Clover (with or without NVMe drivers) going to black screen and not showing anything using BDU method and using other method Clover locks on load for a while the shows boot load error: couldn’t load efi dvd/cd and couldn’t load efi menu after it goes into Clover menu without keyboard or mouse so pretty much useless. I’ve been using MiniTool Partition wizard to format sticks along with BDU and USBSetup. Maybe that has some to do with it? NVMe drive works normally under the windows.
The reason you had the same results with 3 different driver’s is because this is not a driver issue else i would have expect varied results. also if it were a driver issue everyone would have the same problems and we don’t. I’m still leaning towards bios or hardware as i doubt this is emulation related. i would suggest trying your nvme adapter card in a different motherboard slot or even try a different card as we had learned repeatedly on this forum thread not all nvme adapter cards are created equal.
pcie 2 vs 3 number of pci lanes power handling etc these are all factors on adapter cards that can effect the way the nvme drive behaves.
Note for the record i have a samsung 970 evo and it actually exceeds it’s rated speeds and it’s an os drive booted with clover.
The same card in same slot benchmarks MUCH faster as a slave in same PC booted from a sata drive… How is this explained? When I mentioned driver I am talking about the low-level efi nvme driver, not windows.
Hi everyone.
I have followed this guide and successfully bootet from my NVMe already (on an Asus M4A785TD-V Evo). But it takes like 15 seconds until i even get to boot Win10. At this point i might aswell install the OS on my significantly slower 64GB SATA II SSD and use the NVMe only for programs and storage. Any help would be highly appreciated.
"timeout" was already set to 0 and I also tried giving my board time to initialize everything by waiting in the manual boot selection for a bit. "Log"/"Debug" already set to "false".
After BIOS I get a blinking " _ " for a couple of seconds, then a " 6 " and then a constant " _ " with a different font/size before booting into windows.
I read that BiosBlockIO may speed things up but I couldn’t find out which files needed to be replaced and where to download the new ones.
Here’s an extract of my preboot log of what i understand are the responsible steps (couldn’t get a debug log to work):
The reason you had the same results with 3 different driver’s is because this is not a driver issue else i would have expect varied results. also if it were a driver issue everyone would have the same problems and we don’t. I’m still leaning towards bios or hardware as i doubt this is emulation related. i would suggest trying your nvme adapter card in a different motherboard slot or even try a different card as we had learned repeatedly on this forum thread not all nvme adapter cards are created equal.
pcie 2 vs 3 number of pci lanes power handling etc these are all factors on adapter cards that can effect the way the nvme drive behaves.
Note for the record i have a samsung 970 evo and it actually exceeds it’s rated speeds and it’s an os drive booted with clover.
Did you see my side by side benchmark in the prior post? That was the same drive "inland pro 512gb Phison E12S SSD". Only difference was faster score was obtained when I booted off the existing SATA drive.