does this method also works for booting linux based OS? I intent to install proxmox on my samsung PM991 nvme. Will never use windows
Reporting success in installing another OS with Clover on my non-bootable NVMe SSD drive in my “legacy” system : Emmabuntüs ! 
I have now installed the following OSs and all are bootable with Clover :
● Windows 10
● Windows 11
● Linux Mint LMDE
● Kali Linux
● Ubuntu Server
● Emmabuntüs
See my post #817 here.
Just wanted to clarify what this is actually doing for future reference…
After some testing it seems that the issue of a black screen with a “_” then a “6” and then seems to hang there is the result of clover being unable to automatically fail over to the legacy boot mode file and thus hangs during the fail over. your fix makes clover load the legacy boot file first and therefore skip issue entirely.
I have come across an issue, I have just purchased an old dell precision T1700, I have been trying to get it working in a PCIe x16 gen 2 slot (second PCIe 16) and couldn’t get it to work, and I eventually tried it in the PCIe x16 Gen 3 slot and it worked fine, I am wanting to know is there any way I can switch it to the Gen 2 PCIe slot as I am wanting to add a GPU to the Gen 3 slot soon.
Hi, I’m having the same problem as @jonjof. I’m also unable to boot into clover (on a usb) on my hpe ml310e gen8 v2. From what I’ve read in other threads, this could possible be due to the integrated graphics of the server.
I have also tried to rename boot7 to boot (and the original boot to boot_orig) but that doesn’t make any difference. Instead of a 6 with a blinking underscore this gives a 7 with a blinking underscore.
I have tried all day long to make it work and I really want it to work using clover. Is there anyone who has any idea how this could be solved?
I just installed Clover bootloader release 5150 on my T1700 Mini Tower and it works well with the NVMe SSD in either slot #5 (pcie x16 gen3 slot) or slot #1 (pcie x16 slot wired as x4 gen2) as shown here - Dell Precision T1700 Mini-Tower Owner’s Manual - System Board Components. I assume you too have the mini-tower and not the small-form-factor. I have the CloverCD volume on a SATA SSD instead of a USB, but that shouldn’t affect its function. I’m using the Sabrent NVMe to PCI Adapter. I use integrated Graphics on an i7-4790 CPU, so I don’t need a graphics pci card.
This might be the answer to your problem - Using PCI x4 on Dell T1700. You need to enable the additional PCI slots in the BIOS. It appears that by default, only the PCI x16 Gen 3 slot is active.
Let me know if you need any specific information about my setup.
@sibliss,
Thanks for the wealth of knowledge and advice you share here. I have a working instance of Clover but I’m unable to hide extraneous boot options in the Clover GUI. I’ve followed your suggestions on several posts here as well as the instructions at the official Clover configuration Wiki. But nothing seems to work. Here is a detailed writeup on my issue.
I’m using Clover bootloader release 5150 from https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5150 to boot from a NVMe SSD on an old Dell Precision T1700 mini-tower. The BIOS on this PC does not support booting from a NVMe drive. Clover is working great, and it’s given a new lease on life to this old PC.
My only challenge with Clover is to hide all the extraneous boot options under the GUI. I’m trying to hide all but the “Boot Microsoft EFI Boot from System” option. The other boot options are called
• Boot Windows from System
• Boot Windows from Legacy HD3
• Boot Windows from Legacy HD4
• Boot Windows from Legacy HD5
• Boot Windows from Legacy HD6
I tried the following methods to hide these boot options in the Clover GUI, but none of these had any effect.
- Following the official Clover Configuration Wiki (https://sourceforge.net/p/cloverefiboot/wiki/GUI/#hide), I used the following in my config.plist file under the GUI section.
<key>Hide?</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
<string>HD(2,GPT,FDBA7F75-F32B-4D39-81E7-264664116178)</string>
<string>HD(3,GPT,7FF052D7-1004-4BC8-9841-6057CC84B5FA)</string>
<string>HD(4,GPT,2E288221-C76A-4800-9E31-C3569EBB97E0)</string>
<string>HD(5,GPT,C23CDBB2-D484-4700-AA44-B4A06F331C95)</string>
<string>HD(6,GPT,395C579F-1E0D-4ED3-9BC8-B0464CED8252)</string>
</array>
The entries are based on the volume listing when entering the Clover shell. I cross validated the GUID’s using the Windows PowerShell command
GWMI -namespace root\cimv2 -class win32_volume
- Next, I tried the following in the config.plist file based on the example at https://winraid.level1techs.com/t/guide-nvme-boot-without-modding-your-uefi-bios-clover-efi-bootloader-method/31665/652 above.
<key>Hide?</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
<string>(2,GPT,FDBA7F75-F32B-4D39-81E7-264664116178,0x3F000,0x8000)</string>
<string>(3,GPT,7FF052D7-1004-4BC8-9841-6057CC84B5FA,0x47037,0x3EB7D)</string>
<string>(4,GPT,2E288221-C76A-4800-9E31-C3569EBB97E0,0x85BC9,0xC8034)</string>
<string>(5,GPT,C23CDBB2-D484-4700-AA44-B4A06F331C95,0x14E000,0x105000)</string>
<string>(6,GPT,395C579F-1E0D-4ED3-9BC8-B0464CED8252,0x253000,0x68A6658F)</string>
</array>
- Then I tried the following based on the instructions at https://winraid.level1techs.com/t/guide-nvme-boot-without-modding-your-uefi-bios-clover-efi-bootloader-method/31665/541. I labeled all the volumes on the NVMe SSD using diskpart and the label command and used the volume labels below.
<key>Hide?</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
<string>System Reserved</string>
<string>Recovery</string>
<string>Recovery Partition</string>
</array>
- As a last resort, I tried the following. “Legacy HD3” etc. are based upon the Clover GUI boot options that are called “Boot Windows from Legacy HD3” etc. In the system BIOS, I have the legacy boot option turned off. Only UEFI boot is allowed. Nevertheless, the boot options are called “Boot Windows from Legacy HD3” etc.
<key>Hide?</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
<string>System</string>
<string>Legacy HD3</string>
<string>Legacy HD4</string>
<string>Legacy HD5</string>
<string>Legacy HD6</string>
</array>
I’m using Plist Editor Pro to edit the config.plist file. I use diskpart to assign a letter to the CloverCD volume and then copy the edited plist from Windows to the CloverCD partition under \EFI\CLOVER.
What am I doing wrong? Why isn’t any of the above approaches working?
Wish there was a Windows version of the graphical Clover Configurator which, on a mac, shows you the boot options in a GUI, and lets you graphically remove any boot options.
Got it to work. The basic problem was my ignorance of the plist file format. I believe the question mark at the end of a key in the default config.plist simply indicates that there is zero or one occurrence of the key. One must include the “Hide” key without the trailing question mark and the desired array string values for this to work. Once I included the following in config.plist (while leaving the “Hide?” key declaration intact,) it worked.
<key>Hide</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
<string>(2,GPT,FDBA7F75-F32B-4D39-81E7-264664116178,0x3F000,0x8000)</string>
<string>(3,GPT,7FF052D7-1004-4BC8-9841-6057CC84B5FA,0x47037,0x3EB7D)</string>
<string>(4,GPT,2E288221-C76A-4800-9E31-C3569EBB97E0,0x85BC9,0xC8034)</string>
<string>(5,GPT,C23CDBB2-D484-4700-AA44-B4A06F331C95,0x14E000,0x105000)</string>
<string>(6,GPT,395C579F-1E0D-4ED3-9BC8-B0464CED8252,0x253000,0x68A6658F)</string>
</array>
Another way to accomplish what I needed is to add the following to the default config.plist as suggested by @sibliss above.
<key>Scan</key>
<dict>
<key>Legacy</key>
<false/>
<key>Entries</key>
<true/>
<key>Tool</key>
<true/>
</dict>
I currently have this second method implemented as this is cleaner. The Clover GUI now shows only one boot option just as I wanted.
1 Like
Hello,
My system :
MB : Gigabyte GA-870A-UD3 V2.1
CPU : AMD Phenom II X4 955
SSD : Kingston’s NV2 PCIe 4.0 NVMe SSD 500GB
NVMe to PCIe adaptor
Can you please explain the steps to create the Clover USB key
Hi @JMSL. Just got to see your post.
You may like to follow the instructions I posted here.
By the way, which OS(s) do you intend to use with Clover ?
Hi, Morbius.
Thank you so much for the information.
I’m going to use WIN10.
I have included all the files necessary (im pretty sure), except for a windows disk, which i don’t think is allowed on this forum. NOTE: the BDU version i have was NOT given me by sibliss. Find his post in the collection of posts document I made.
hotfix and other EFIs.zip (6.7 MB)
BDU and adk.zip (6.7 MB)
Tutorial for loading Windows or Ubnutu on NVMe SSD for non-compatable Motherboard
Now, first thing’s first. This is how I did it. This is written with limited experimentation. Every system is different. If you run into an issue, then you must consult the collection of posts from the (“collection of post for Clover bootloader.docx” file included) and the forum on winraid.level1tech.com. It was one long road and full of pitfalls, but i felt posting my journey will help others, and this is the attempt to do so.
Going in blind will only hurt you. Unfortunately, you need to read up on as many posts to understand what is happening. You don’t need to read all of them but the main important ones which are in the file.
You will be using clover OS which is built with linux. You shouldn’t need to worry about that.
You do need to understand how to build a clover config file. It’s not hard. Don’t freak. It’s not that many settings you need to change. Make sure you use Notepad++.
Installing Ubuntu or other flavors of Linux is easy but I will show Windows 7 because that’s the only way to get a true genuine version of windows 10 and above. However, I just ended up using Win10 I couldn’t get Win7 to work.
This should work only using the MBR (legacy) booting. I’ve done it before using ubuntu.
Things needed.
• NVMe adapter. Will work in graphics card slot (PCI x 16) or that other PCI slot for sound cards… PCI x 4? I don’t know.
• NVMe SSD drive that’s Gpt activated ( this is done inside windows with DISKPART)
• 2 Flash drives(Note: A harddirve can be used, you just need to check the option within BDU) Note: a CD or DVD cannot be used with clover
• Linux Installation medium (this does not need to be prepared)
• The machine you are modding with a Windows OS already installed on it.
• The correct version of BDU ( I think it is BDU 2.1.2019.024 beta)
• The correct version of the Clover ISO (CloverISO-4961.tar.lzma)
• Prepared Clover boot disk
• Prepared Windows 7 OS medium… if that’s your choice ( MS NVMe Hotfixes for win7/W2k8) (Note: if installing win 10, you don’t need to prepare it as it already has NVMe drivers)
◦ Windows ADK toolkit
◦ windows disk
◦ hotfixes
◦ drivers (I’m sorry. I do not know the necessary drivers required (Phase 1, Method 1)
• NVMe driver for Clover USB (NvmExpressDxe-64.efi) Note: it will be auto-generated for you.
PHASE 1 - Preparing windows (3 possible methods!)
METHOD 1
Note: this didn’t work for me, cause this pretty complex. I heard that there is a tool that can do this for you. I don’t know the name of it. Sorry. I think it was in a post somewhere.
You need to be able to find a driver as well. I really don’t understand what this part is about at all. There’s a whole post dedicated to this on winraid.level1tech.com somewhere.
- Install the latest Windows ADK for Windows 8.1 update. Download and install the Windows ADK | Microsoft Learn
- Create local folders c:\temp\src c:\temp\mount, c:\temp\winremount, c:\temp\hotfix, and c:\temp\drivers.
- Copy the setup files from the DVD or a mounted ISO to C:\temp\src.
- Copy the hotfix (.msu or .cab files) to C:\temp\hotfix.
- Copy the driver files to c:\temp\drivers.
- Run Command Prompt as an administrative.
- Running the following Deployment Image Servicing and Management (DISM) commands will Insert the hotfixes and drivers to the boot.wim and update the sources folder. For more information about DISM, see the DISM Operating System Package Servicing Command-Line Options.
dism /Mount-Image /ImageFile:c:\temp\src\sources\boot.wim /Index:1 /MountDir:c:\temp\mount
dism /Image:C:\temp\mount /Add-Package /PackagePath:c:\temp\hotfix
dism /Image:C:\temp\mount /Add-Driver /Driver:c:\temp\drivers /Recurse
dism /Unmount-Image /MountDir:C:\temp\mount /Commit
dism /Mount-Image /ImageFile:c:\temp\src\sources\boot.wim /Index:2 /MountDir:c:\temp\mount
dism /Image:C:\temp\mount /Add-Package /PackagePath:c:\temp\hotfix
dism /Image:C:\temp\mount /Add-Driver /Driver:c:\temp\drivers /Recurse
Now, copy this directory C:\temp\mount\sources to c:\temp\src\sources.
-
Now, run this command
dism /Unmount-Image /MountDir:C:\temp\mount /commit -
Obtain the index from the Install.wim information by running the following command, and then count how many indexes to see how many indexes have to be updated.
dism /Get-WimInfo /WimFile:c:\temp\src\sources\install.wim -
Insert the hotfixes and drivers to install.wim and winre.wim by running the following commands:
dism /Mount-Image /ImageFile:c:\temp\src\sources\install.wim /Index:1 /MountDir:c:\temp\mount
dism /Image:C:\temp\mount /Add-Package /PackagePath:c:\temp\hotfix
dism /Image:C:\temp\mount /Add-Driver /Driver:c:\temp\drivers /Recurse
dism /Mount-Image /ImageFile:c:\temp\mount\windows\system32\recovery\winre.wim /Index:1 /MountDir:c:\temp\winremount
dism /Image:C:\temp\mount /Add-Package /PackagePath:c:\temp\hotfix
dism /Image:C:\temp\mount /Add-Driver /Driver:c:\temp\drivers /Recurse
dism /Unmount-Wim /MountDir:C:\temp\winremount /Commit
dism /Unmount-Wim /MountDir:C:\temp\mount /Commit
Note If there are multiple indexes in step 8, then run all these for each one changing index number one by one.
(Note: if the 4th command down (second mounting command) does not work then you may not have any more indexes needing to be updated for the winre.wim file. but you still need to continue running the first 3 commands for each index (updating install.wim) then the last one to unmount the image.)
- Run the second of the following oscdimg commands unless you are using MBR (legacy boot stlye). For more information about oscdimg, see the Oscdimg Command-Line Options.
Note: if oscdimg is not found then you need to put the oscdimg.exe file into your Systems 32 folder. you can find this at this directory if you did step 1 and installed ADK toolkit
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg
For Legacy BIOS Boot mode:
oscdimg -LTEST -m -u2 -bC:\temp\src\boot\etfsboot.com C:\temp\src C:\temp\Win7.NVME.ISO
For Legacy and UEFI BIOS multiple Boot mode:
oscdimg -LTEST -m -u2 -bootdata:2#p0,e,bC:\temp\src\boot\etfsboot.com#pEF,e,bC:\temp\src\efi\microsoft\boot\efisys.bin C:\temp\src C:\temp\Win7.NVME.ISO
12. Use Rufus to make a bootable USB.
Method 2 – Note: (FYI: This didn’t work for me, probably because my version of windows was not Genuine.)
Note: VERY IMPORTANT - If you do this method you will have to read Post #245 (MikeyLikesiT) of the collection of posts for NVMe installation on Windows 7 on winraid.level1techs.com
Doing this method will change how you do the rest of the process.
This is the condensed version
- Follow NVME/Clover thread to set up Clover USB.
- Install Win7 on SSD thru legacy BIOS.
- Upgrade Win7 to Win10, in-place within Win7. (Note: use a genuine disk. Will help.)
- Install cloner and clone Win10 SSD to NVME (clonezilla live boot cd works great)
- Log into Win10 on SSD and convert NVME from MBR to GPT.
If MBR2GPT is not located you need WinPE. Either download(i could not find) or manually access with a WinPE boot disk, which is made with copype tool which is only installed with adk and adk PE addon (Search online for details)
- Use Clover USB to boot into Clover and choose, start Windows EFI to boot into NVME.
- Use reagentc.exe commands to rebuild Recovery Partition on Win10 NVME.
- Clean up Clover boot USB files and leave the USB key in for every boot.
Note: (FYI: This didn’t work for me, probably because my version of windows was NOT Genuine.)
Method 3 – just Find and download a UEFI ready Windows 7 or 10 disk. I think windows 10 automatically comes with NVMe drivers.
Note:( this DID work for me even though it was not genuine.)
PHASE 2 - Get a working Clover key (bootable usb)
You shouldn’t have to enter the clover shell and pray you do not because that is a rabbit hole that leads to nowhere.
Steps
1. insert blank NVMe and start-up
2. boot into windows and format the NVMe
a. goto command line type diskpart
b. List disk > select disk (the one that is the NVMe)
c. Run clean
d. Run convert gpt
e. Then format it to NTFS if installing windows. ext4 for linux (note: you may have to format the whole drive first then convert to gpt)
3. copy the Clover ISO to wherever the root of the BDU folder that you downloaded (CloverISO-4961.tar.lzma)
4. Run BDU 2.1.2019.024b this version exactly!!
5. go into configuration and make sure that it is using the ISO in local folder
6. hit Format
7. now make sure the flash drive has a partition in it that is 200 MB, if not hit format again until it does
8. When it does work, Create these new directories on flash drive if they do not already exist
a. Efi\CLOVER\drivers\bios
b. Efi\CLOVER\drivers\uefi
c. EFI\CLOVER\dirvers64
d. EFI\CLOVER\drivers32uefi
e. EFI\CLOVER\dirvers64uefi
9. enter this location CLOVER :\EFI\CLOVER\drivers-Off\ and look for the NVMe driver
a. Note: this folder should contain the auto generated drivers for your system.
Note: NvmExpressDxe-64.efi is the only file you need. But in case it does not work for you then find and use all of the ones below. I think these are the important drivers you need to look for (ii and iii most important) they should be in the drivers-Off folder. So I just dumped them all in all 5 folders hoping for the best. It won’t hurt anything putting them in there. I believe that I only needed NvmExpressDxe-64.efi UEFI, not sure with MBR.
i. i. nvm.efi
ii. ii. NvmExpressDxe.efi
iii. iii. NvmExpressDxe-64.efi
iv. iv. GrubEXFAT-64.efi
v. v. GrubISO9660-64.efi
vi. vi. GrubNTFS-64.efi
vii. vii. GrubLDF-64.efi
Note: the last 4 should be in the Drivers-off folder as well, somewhere.
10. copy the driver into all 5 directories made in step 7
11. Edit \EFI\CLOVER\config.plist with notepad ++ or another sophisticated editor (Note:using window’s notepad will destroy it).
Change the value:
<key>Timeout</key>
<integer>5</integer>
To
<integer>3</integer>
12. insert OS installation medium
13. enter bios and turn on UEFI mode. If you are running this in Legacy then skip this step.
14. boot into clover(you might have to turn on and off the UEFI settings if it doesn’t first boot up)
15. If you got in then you have successfully made a clover key BUT you will not see your harddrive until you install an OS!
PHASE 3 – Installation and Finalization (configuring clover)
NOTE:If you chose method 2 in Phase 1 then these final steps will be a little different, not much different tho.
- Just insert clover, and installation medium and make sure it boots into clover.
- If you cannot boot the installation medium from within clover then you have to just boot directly into the installation medium. This is NOT preferred but it will most likely work anyways, so don’t freak, lol.
Everything should be done this is really just tiding things up and making it smooth. If you had issues im sorry. you have to read as many posts as you can to understand what to do next.
Here are some reminders if it’s not working for you. clover does not find harddrives only installed OSes. You have to run BDU on the computer with the NVMe. The drive needs to be in gpt even if you are booting clover in MBR. And get your rest. That will help a lot!
1. Find out the name of the bootable harddrive within clover. The name might be a weird name like EFI or Boot or something. It shouldn’t be a GUID address. If it is then something is wrong and I don’t think you’ll be able to boot into it. Let alone select it.
2. Clover should automagically boot into any OS that works. So the default should have been changed to 3 seconds but if you want it instant, do this.
3. boot into windows
4. Find config.plst file on clover USB and open it
5. Ctrl+F for the boot section. It should be in the same location as the timeout in step 11 phase 2
6. Don’t be scared, what you are seeing are basic settings you can change. Just instead of clicking a mouse you are typing numbers and such.
7. If timeout it at 0 it will be instant
8. Make sure the name of the drive (as it appears in CLOVER) is entered into the default volume.
9. More information at sourceforge.com . Google “clover sourceforge” click on it then > Wiki > Table of contents > configuration > boot. This will give you the info you need.
Going through the instructions for clover I got stuck at copying the nvmedriver in the new version there doesn’t seem to be a driver64 directory so I just copied the driver from off to Bios and Uefi directories instead. Now when I am trying to boot from the USB it just gets stuck on a blank screen indefinitely. Is there something I am missing?
I tried this but I am still getting a blank screen on boot
First, could you provide some details about your system platform ?
Then, did you use the exact following files from the Clover.zip attachment which I posted in post # 833 ?
• BDUtility.exe (v2.1.2018.023b)
• CloverISO-4961.tar.lzma
If you did, both directories EFI/CLOVER/drivers64 and EFI/CLOVER/drivers64UEFI should have been automatically created in your Clover USB key.
If these directories are missing, then something obviously went wrong during the Clover key creation process.
Install Clover on Usb disk using clover boot disk utility from here cvad-mac.narod.ru - BootDiskUtility.exe (clover boot disk to install on fixed sata disk or usb disk)
Copy NVMExpress.efi from EFI/CLOVER/drivers/OFF to both directories EFI/CLOVER/drivers/BIOS and EFI/CLOVER/drivers/UEFI
Then boot from clover installed on USB disk drive and then install windows 11 in emulated UEFI mode on nvme disks with gpt partition.
or follow few other options from this post for X58 motherboards(lga 1366) to mod bios to support nvme disks natively to boot windows without usb disk.
Hi, thanks a lot for the effort of this project. I tried to implement it and ran into a interesting issue. I can start Clover from my USB key and I can see 4 Windows boot options. However, none of them actually boot. When I try to boot any of them them I see a weird symbol in the middle of the screen, a square with diagonal yellow and blue (or grey?) lines and nothing happens.
My system:
- HP G1 with an i7-4770.
- SATAIII SSD with working Windows installation (boots fine without Clover)
- NVMe SSD connected via PCIe 4x with the cloned Windows installation from the SATAIII SSD. Visible in Windows, but not bootable.
- Issue: Clover starts, but nothing is bootable.
I have one SATAIII SSD with Windows installed that boots fine if I do not plug in the Clover USB key. My NVMe SSD is visible in Windows, but I cannot boot from it, because my Legacy Bios does not recognize it. Hence, I am trying to boot from the NVMe SSD via Clover. My Clover USB key can boot Windows successfully on my other computer (HP G4 with an i7-8700 CPU). This second computer also runs a Legacy Bios.
I tried both the newest version of the BDU from the instructions on top with downloading the latest Clover and the BDU+Clover ISO from Morbius’ post #833. The result was the same, with the only difference that the weird symbol I see only appears for the older Clover version. In the newest version I just see a black screen when I try to boot any of the windows boot options in Clover.
I disabled all security options in the Bios since I thought it might be some security issue. But that also did not help.
Happy to hear your ideas what might be going wrong.