@nivi3 :
I have moved your request into this thread, because here are the Clover method experts. Maybe @Nyctophilia can help you regarding the Clover boot screen.
Here are some advices regarding the performance of your NVMe SSD:
1. Try to insert it into another PCIe slot.
2. Look into the start post of >this< thread and follow my advices.
Good luck!
I need help. I already have the OS and everything copied to my NVME SSD using macrium reflect. Will this be a problem? I have downloaded clover on a USB but I dont see the file paths that are on page one of the guide. I did find the NVMEexpressdxe.efi file in clover/drivers/off though. But this doesnt seem to be the 64 version.
Can I get an updated file path?
I want to make sure im copying and putting the right things were they go
The file to be edited is;rootfolder->EFI–>CLOVER–>config.plist
1. In your BIOS make sure you can boot into your USB Where the clover is.
2. Boot into clover and go through the boot options, one by one, until you see your NVME where Windows is loaded. If you don’t boot into clover then you have to make sure your clover files are correct.
3. If you can Windows from your nvme then you are okay, if you can’t, try re-installing Windows.
@ndruiz
Assuming you used the BDU as directed in the OP …It is safe to simply omit the 64 from the file path as clover itself actually doesn’t care if it’s 32 bit or 64 bit since it makes no difference to handing off the boot to another drive/os like we do in this situation, I have also found it is perfectly safe to copy the NVMEexpressdxe.efi driver file from EFI/clover/drivers/off dirrectory to both EFI/clover/drivers/BIOS and EFI/clover/drivers/UEFI directories with no issue file size is negligible at best and my system is 64 bit os.
As for cloning a an already installed OS build… It is possible and infact i did it myself but it is not an easy process (much easier to just do a clean install) no doubt the cloned OS will not boot properly initially if i recall it took me about two days of trial and error with various terminal commands to make mine work and i’m a Microsoft certified tech… that said if you still want to go this way the best advice i can give especially if coming from an older windows 10 upgraded from a previous os is to make sure the OS partition is GPT not MBR windows 10 has a built in tool to convert to gpt without data loss https://docs.microsoft.com/en-us/windows…ment/mbr-to-gpt
EDIT:( try Microsoft’s sysprep first before the below blog method )
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep–generalize–a-windows-installation
I also found steps 2, 2a, 3 and 8 particularly useful (regarding getting the OS to boot) from this page PLEASE NOTE that i have no invested interest in or relationship with this blog and you do this at your own risk. I simply found it was useful https://mrlithium.blogspot.com/2015/12/how-to-boot-nvme-ssd-from-legacy-bios.html HOWEVER i highly recommend using the supported Microsoft sysprep method ( do a web search for how to use it ) before attempting the way suggested on mrlithium’s blog. sysprep is ALOT easier and quicker when it works unfortunately my system failed to sysprep so i had to do it this harder way.
So i put the NVMEexpressdxe.efi file into the UEFI directory. Everything worked. I saw my SSD too. But when I boot up my SSD there is just a blank screen. Is this because I have already cloned my main drive and there is already an OS and files on my nvme SSD? How do I fix this.
Thanks for everything and for the quick replies.
@ndruiz
glad to hear clover booted for you, the blank black screen is expected and happened to me too… and is likely one of two issues. but first i should mention this is the part that took me several full days to figure out and there is no exact science to it just alot of trial and error. i should also mention it helps to have a very good knowledge of your drives and partition layouts which can be viewed via diskpart in a terminal window
first issue is that clover will see several partitions on the ssd and even identify several of them as windows you need to be sure to boot the correct partition via clover remember to ensure you are running uefi gpt not legacy mbr on your ssd as you are booting via uefi i cannot recall exactly which partition you need to boot from but with mine it was the variant labled with efi…
second i’ll assume like me you didn’t change the registry keys mentioned in that page before you cloned it this means the windows bootloader on your ssd is trying to boot the wrong hard drive id and partition id. i corrected this by booting to my old hard drive and changing the registry keys then cloning the drive again alternatively you could from a separate windows install on the same computer but on a different drive and "remote" mount and edit the registry hive from that install…
once those registry keys are changed even if it worked it still wont boot though but you should atleast now hopefully get the display output from the windows bootloader typically the spinning circles before it bluescreens and may reboot (note you may not even actually see the bluescreen before it reboots) if you get to this point then great because you are two thirds of the way there. DO NOT PROCEED until you have reached this point
once you have got to this point you now need to fix the windows boot issues from a windows Recovery Environment terminal prompt, I found it was best/easiest to just boot from a windows install usb and enter the repair/recovery environment that way. from the terminal you will need to run several and various recovery commands as required until it boots the commands you will need will vary but will probably include an offline sfc /scannow and an offline dism /restorehealth both these offline commands are different to the normal ones so take your time research them and understand them.
may also be worth trying bootrec and bcd edit commands but again do so at your own peril i will not take any responsibility if you mess up the os image even more with these commands.
i hope this atleast points you in the right direction and good luck, as i stated in my previous reply cloning the os with clover involved is a process best only undertaken by advanced windows users for this these reasons.
Hi,
I have mounted Clover on an SD card, and I have installed Windows 10 (on my M.2 SSD disk) and everything works correctly. Reading in the forum I have seen that there are users who have then installed Clover to an internal hard drive (SATA), but I can’t get it to work this way.
I have tried to create a small partition of 200 or 100 MB (in FAT32) in my internal HDD, and copying here the files that I have on my SD card (Clover installation), and I have also tried to create the partition with the BD utility, but to restart (having selected the internal disk as boot into the BIOS) does not load the Clover menu, and it gives me the message that “operating system not found”, but with the SD card it works correctly.
Do I need to modify something of the config.plist? I have seen some user who claims to have modified it (but it is not specific what lines), and others who only copy the contents of their USB stick in the internal hard drive.
I hope you can help me with this.
Regards.
Sorry, I didn’t fully understand everything you said. I am a newbie. Lets go through this one step at a time. How would one make sure clover is seeing the right partition. All i see is “NVME” windows which is what i named my drive. Thank you 
@oskarssj5
I did install clover to an internal hard drive aswell the best way is to use the BDU then simply copy the config.plist (and any themes) to the new clover install on the disk as far as i know you should not need to edit anything in the config.plist if you are using it on the same computer… (atleast i didn’t have to when i did it) that said here are some points to note about using clover on an internal disk and bootloaders in general … the BDU will seek to erase the entire drive this is a must and cannot be avoided(its about partition tables and other technical stuff), the 200mb fat32 partition created by the BDU must be at the very start of the drive not after other partitions(if you allow BDU to wipe the drive it should do this automatically). clover i think uses MBR type partition table and thus the partition must be marked active ( can be done via diskpart) before it will boot and again the BDU should do this automatically.
Finally don’t forget to enable fixed disks and select clover boot record under the options in BDU.
Beyond that though i’m sorry i can’t think of any reasons it did not work for you, perhaps some of the other clover wizards here can think of something i’ve missed.
@ndruiz
so it seems we have got to the bottom of your issue it seems your clone is only a partial clone and thus won’t work … windows 10 like many recent windows versions requires atleast the system(boot) and windows(os) partitions to boot. you need to boot to the system partition i think if you properly cloned the whole disk and not just part of it than you should see actually up to 5 partitions on the disk. in your situation i would if you can make a new proper clone of the disk or simply do a clean install.
i am going to decline to discuss how to make a viable windows clone because cloning although possible is well beyond the scope of this forum thread, i would suggest to perhaps make a new thread about cloning windows.
@sibliss
Thank you for your advice, but I already tried with the BDU utility and copied the config.plist of my SD card (with which it works), I also even tried to copy all the contents of the SD card to the internal disk …
However, I can only boot from the SD card :_( , but I would like to be able to free the card and take advantage of the internal disk.
When I want to manually select the boot device in the boot menu, only the SD card appears to be able to select a device (if I have it on). It is as if it did not detect the boot partition of the internal disk (it is formatted with the BDU utility and marked as active).
Does anyone think of what can happen?
Thanks in advance.
@oskarssj5 Did you checked option of using Hard Drives as target drive for installation on BDU ?
If you combine BDU with pre-downloaded Clover, and launch that on XP/7/10 mini, you should be able to format and install Clover on what ever you need.
Keep in mind, Clover installation formats target drive (and all of it’s partitions), so better copy data you want saved somewhere. Also, I recommend avoiding using Clover on the same drive as OS.
Hi @agentx007
Yes, I installed clover on an internal SATA hard drive (formatted / installed with the BDU utility and the option "Enable fixed disks" checked). I have the operating system installed on the NVMe M.2 disk.
Is it formatted in GPT with "EFI" hidden partion ?
Quick question
I want to boot off NNVMe drive off a Supermicro LP Server running Windows 2019.
First, has anyone attempted this?
Second, is it my understanding that the boot order goes UEFI (which the MB has) then you must always have a USB drive in the system for clover, and then it passes loading over to the NVMe drive?
Anyone see any issues with attempting this? Just do not want to waste a lot of time or money if this type of setup is not workable. I do not want to mess up the server with the BIOS edit
Thanks
Tim
I am using a Supermicro XDTL-3F server board for my Hackintosh which I also use for booting into Windows. UEFI or Legacy BIOS is of no relevance. Yes, the Clover option to boot from NVMe will work without any firmware modifications on your system.
You don’t have to use a USB stick, I am using a small SATA SSD for my Clover install - you can use any bootable media, USB, SSD, Hard Drive even a CD/DVD. Using the SSD is a lot faster than USB 2, which you are likely to have given the lack of NVMe boot support in your BIOS. You just have to make sure that your BIOS see’s the Clover device as the primary boot option so Clover boots first. The Clover device then stays in place as it needs to be called each time you boot so the boot process can continue with your NVMe drive. You can modify Clovers config.plist to always boot the same device and with no/little delay so its just boots, albeit with a slight delay given you are running Clover during the boot.
Just to re-cap the theory of whats happening. Windows and macOS have their own NVMe drivers that see the drive. But older BIOS (Legacy and UEFI) dont know about SSD’s living on the PCIe bus - they thinks thats just for Graphics Cards and the like - hence you can’t boot from an NVMe drive.
What you are doing is getting your BIOS to boot from a drive it can see, typically via USB or SATA. This boots into Clover which is rather like a small operating system. Clover has its own driver that sees the NVMe drive and then lists it, along with anything else bootable it can find on USB, DVD, SATA, SAS etc you then choose to boot from one of those devices. and Clover loads and starts your operating system just like a BIOS would.
One tip, make sure you stick the NVMe PCIe card into the right slot. I have two free slots, both look the same (PCIe x8 connectors) but one is PCIe 2.0 x4 and the other is PCIe 1.0 x4 … one is virtually three times as fast as the other (500 MB/s PCIe 1.0 compared with 1500 MB/s PCIe 2.0 - for my SSD).
So i recloned my drive using macrium reflect. Windows 10 sees it as a bootable local disk. But clover still only sees my NVME once. Is this a problem with macrium reflect or is there something I need to do to the drive after cloning it. Thanks
Hi all,
I have an Optiplex 7010 with a 1tb NVME drive in an adapter. I have tried many different configs of clover, including the updated one in this forum. The issue is that clover refuses to recognize the NVME ssd. I’m running version A29, I7-3770, 8GB RAM.
Any help is extremely appreciated!!!
@Jah-On
the main 2 reasons obviously aside from a bad adapter card that clover will fail to recognize the nvme drive is if;
1. the nvme dxe driver hasn’t been inserted correctly.
2. the drives partition configuration doesn’t register within clover.
please check the dxe driver file is in the correct locations as mentioned in my other post (i would put it in both locations to be safe) and ensure your using gpt on the nvme instead of mbr remember clover won’t detect the nvme drive if it has not been initialized and formatted yet (i just formatted mine to ntfs then let the windows installer wipe it and change it as usuall during the windows install) beyond this be certain of your adapter card not all cards are bootable and check the bios for any erroneous PCI settings that may interfere with it.
good luck,
I saw in Clover option: load option roms. Can there add any bios roms like raid or ahci ?