You could actually install clover to the sata ssd and configure clover to wait for 0 seconds at launch and to boot from the nvme drive. You could also use something like rEFInd instead as it supports legacy and efi boot too. To be fair, this could be done any number of ways, but you don’t actually need the USB key to store the boot loader at all. It can go on any drive the system can see on boot and then that points to and loads the target nvme. 😅 it shouldn’t be too hard - I’ll come back and update when I’ve gotten myself going.
A little hint for old mobos with no uefi support to begin with, Use clover legacy and an old clover version like 49XX or something, put windows installation thumb drive only when clover successfully boots, You may need to exit clover, open the boot maintenance manager and navigate to the BOOTX64.EFI on the installation thumb drive, Then after windows is installed, use microsoft efi boot from efi to boot the installed windows. (windows 11 didn't work with me)
Instead of disabling the USB drive it is easier to remove its drive letter in disk manager. This will not say it want to format it or the like anymore and safely remove it from the Explorer etc.
But how will we install the OS on the M2 disk if doesnt boot from BIOS. Will the disk shows up while installing Windows 10 ? I own Dell Optiplex 7010 MT
Normally it will show up while installing Windows 10. Otherwise you can insert the clover and the Windows stick at the same time and boot the clover stick. Then you can select the Windows stick in clover and install it. In my case the Windows stick was the first option in clover. Thanks for watching.
Clover works fine from the USB, but I can't get clover to install on an SSD and I just can't figure out why. There are several different methods for making this work, but none of them actually work on my X58 legacy system. There are a bunch of "how-to" articles that use UEFI BIOSes but at the point that your M/B has a UEFI BIOS, why would anyone want to use the clover UEFI emulator?
Q1 What is the min. USB stick you need for clover will 1GB stick be enough? Q2 I assume you first load windows ISO via USB and install windows 10 to the NVMe as normal (but the NVMe can't self boot). I guess after the install is finish you can then first boot to NVMe with clover.
Please check the link in the description, there are further informations. Q1: A 250MB USB Stick should be enough, clover needs 200MB. Q2 you can do it like you have suggested. I recommend to boot from the clover stick and select the windows stick in clover to install. You have to plug in both sticks. Thats how i did it on several computers and it worked perfect.
could you write me step by step. Because I don't understand steps. For example, nvme must installed on board right? this usb clover disk must plugged everytime for boot? When I want to install windows I plug a windows usb disk on laptop and then > I will install that windows by the way another usb disk (clover disk must plugged) I need these steps
Das Erstellen des USB Sticks mit einer älteren Version hat funktioniert. Ich kann von dem USB Stick booten und sehe die Startseite. Egal welchen Menüpunkt ich auswähle, es passiert nix. Kein booten, keine Fehlermeldung, es passiert einfach nix. Hast du eine Idee, woran es liegen könnte?
@@ermvcorleone3069 I concur. The readme is atrocious. However, I read in another tutorial that was updated, which said that you needed to create folders for use with X64 Windows installations. Also, the filename of that nvme driver was different than in the original readme, which was also explained. I followed the tutorial as best as I could, but I get pretty much a blank screen with a few options in very small font, and for each option selected I get nothing. It did however list a few different boot devices, but no NVMe device. My mainboard is quite stupid. It has UEFI support, but not for NVMe (I have an PCIe adapter for it). Windows can detect it and use it, so no problem there. However, this Clover utility has some documentation, but needs a proper tutorial for a basic setup, not that smear of keyboard keys that it currently has. Tried to find that post, but it would seem I have misplaced it somewhere... On my USB-stick however I made these folders, as instructed: x:\EFI\CLOVER\drivers64uefi x:\EFI\CLOVER\drivers32uefi Into which I copied the file NvmExpressDxe.efi taken from x:\EFI\CLOVER\drivers. I also copied the folder structure (with content) to these parent folders (x:\EFI\CLOVER\drivers64uefi and x:\EFI\CLOVER\drivers32uefi) I didn't see anything that would indicate that this/these files would have to be specified in x:\EFI\CLOVER\config.plist or anywhere else in that readme. It would seem though that you need two USB-sticks (Or one for the Clover, CD/DVD/USB/other media for Windows) so that this can boot Windows install or regular installed Windows. Problem for me lies in that Clover simply doesn't find the NVMe device at all. There's another option, equally as poorly documented way to get an PCIe NVMe device to be recognized in UEFI/BIOS, and that entails you to modify your BIOS. I tried that too, but still can't find that damn device. Whenever I disable the CMS my BIOS beeps in error, restarts and re-enables CMS again. I remember some +10 years ago when I sat with Windows Vista, I think. Not sure, so long ago, but I was able to install Windows on a USB device, and I had installed Windows on a local disk at the time, and I installed another version on that USB disk, and the boot loader read the boot disk and fired up that USB driver and successfully booted from that USB disk. This should be about the same, but it's so far from it. Just for an experiment I installed Windows 7 on an SATA SSD to get a boot device. I then upgraded to 10. Found an old Windows 10 installation that I had on-disk and ran it (The newer versions need product keys, which I have, but were not accepted). Anyways, I did install it on the NVMe disk, in hopes that it would fix that bootloader, but it simply just reboots once it tries to boot it. I read that GPT could be an issue, so I converted it to that from MBR, still the same thing. This is disappointing as I was hoping to upgrade my old Dell server the same way (except for the BIOS which is too old) so that it could become much faster, and I don't feel like using an NVMe as a secondary disk as I would still need to have another disk to boot from.
Yesterday I tried some different configurations. Also tried it on a non-UEFI-computer, and to my (very) big surprise, I got a menu from which I could then select boot device. However, it refused to boot at all on the NVMe drive. It just said something about not able to read files, then it just froze up. One guess would be the file system not being correct, although I converted it to GPT earlier. Might be corrupt, and I have some stuff on it that I didn't want to lose. On my SATA SSD however, it booted Windows 10 just fine. But it was unable to boot either of the two USB-sticks on which I had Windows 10 installation on. Froze there too. I'm also very surprised that Clover didn't detect a boot-CD, which I took for absolute granted that it'd do. That was a certain no-brainer for me. Turns out that it doesn't support it. You can make a boot-CD with Clover, but doesn't do any good if it can't even read a CD, and seeing as how unplugging a USB (with Clover) crashes the entire computer, I fail to see that it would allow for a CD-swap. I also tried tossing in another driver (in all folders I previously mentioned), which I currently can recall what it was named, but it suggested iGPU in the name, which would be CPU's internal graphics, so I yanked the PCIe GPU and went on the on-board graphics card, but still no graphics/menu. However, there was one thing that was new, although I can't remember when exactly it happened, but as I chose, I think, bootmanager or boot-device manager (?) from the non-graphic menu (Which btw, is all-white), I was able to select boot from image, from which I selected x:\efi\boot or whichever it was. That was from the USB-stick containing the Windows installation program. Did get it to boot, but it was unable to get pass the selection of disks as it refused to install on the NVMe-drive. Something's is very FUBAR with this Clover, that's for damn sure. Mostly annoying is that it almost worked on my old POS computer, but freezes up, while on my semi-supported UEFI-computer it doesn't seem to load the GUI properly and there's no visible log to check, and no way to exit to the shell. It seems that it's based upon Linux, but the kernel-stuff doesn't load any interpreter so you only have basic commands (Type: "help" to list available ones), but a few of these makes no sense that they're there, but that's besides the point. Clover needs to be more universal before it can be useful for weird computers. This is actually the only real issue I've had with this machine, an ASUS P8H77-V LE motherboard, i5-3570 CPU. BIOS is atrocious to deal with when it comes to CMS. Disabled it refuses to get past the NVMe to PCIe-card. It beeps, then resets the parameters and CMS is enabled again. Then there are a few options that allows me to continue, for eg. if I put an UEFI-flashed USB-stick in the USB it goes past that. Don't remember exactly, but I did a combo och BIOS-settings along with that stick, but there was an error that meant I had to press a button to select the next boot medium, so no automation there....
Is your nvme ssd drive has clone window on it , did u disconect all HDD exept Nvme ssd before you restart , your guide is appreiated . I tried but it is not work .thanks
hi my friend, I need a personel help I tried everything but I m doing wrong things I guess. Please help me I have Acer vn7 571g and I bought crucial P2 CT250P2SSD8 250 GB disk, I install windows but it can't boot I tried everything But this way to solve this I couldn't do, please help me
Hi, i will try to help. I think the problem is that your notebook only can use Sata SSDs and this is an M.2 NVME. The trick with the USB Stick only works on desktop computers with an PCI-Express adapter. Does the drive show up in the BIOS? Does the Windows installer see the drive when you run it on the notebook?
@@pcandservertips8864 Not show up in the bBIOS, but windows installer see that disk and install windows but does not boot :( if we have a chance we can look up via teamviewer or something else
@@pcandservertips8864 I can install windows but BIOS doesn't see the drive. When I install windows it cant boot I couldnt recognize usb stick - windows installation - nvme plug how can I do I don't know. could you help me via team or something ? I can't use my laptop for 2 weeks I need it
@@alien6334 www.win-raid.com/t2375f50-Guide-NVMe-boot-without-modding-your-UEFI-BIOS-Clover-EFI-bootloader-method.html follow this instruction, you should be able to boot the stick and select the drive.
I have a question for you guys regarding "PC that can't boot NVMe". We have a PC with "SATA-HDD+NVMe-SSD only, Linux installed on HDD, this is Tool, Clover written on HDD-ESP, 21H2-USB installed on SSD, when rebooting, WindowsBootManager is at the top of the list. Enter UEFI-BIOS configuration mode, rearrange the order to Clove's kick (hd1,gpt1)/EFI/clover/CLOVERX64.efi (hd1,gpt1 at the top, Ubuntu - 2nd, WindowsBootManager - 3rd, HDD - top 4th, and reboot) The installation continued, the SSD became the start screen, and Win10-21H2 was successfully installed and rebooted. Question Can you please write down the main points and the order in a way that I can understand? No. I plan to do this in turn to other "NVMe unbootable PCs". Translated with www.DeepL.com/Translator (free version)
*************************************** Solution at the bottom of this text: *************************************** Does anyone know what the hell is wrong with my stuff? I've tried numerous configs, and bit by bit I'm almost getting it to work. First from a white background (CSM, and wrong version of the file "boot" in root folder of USB flash drive), to an almost usable menu like show in multiple images & clips, except no disk icon, until I hooked up my SATA SSD it showed three disks, and the first one booted that SATA drive, no surprise there, but was unable to do so with the other two. I could understand if the NVMe SSD that I have in a PCIe slot wouldn't boot due to mongoloid partition (MBR/GPR), it's just that without the SATA SSD, nothing shows up so I'm unsure what the hell's going on here. According to some tests with one configuration with the USB-stick (Tried multiple times) I was able to see (In shell mode) that the driver for NVMe had been loaded by typing "drivers", so it should by all accounts, work. But, no disk is displayed. I tried with installing Windows from another USB-stick in UEFI-mode to the NVMe-drive. The installation went like clockwork. Partitions were erased prior so it was blank. I read in some forums that the partition need to be GPR, so I tried to convert it in one attempt, but I was unsuccessful. I'm running out of ideas, so anyone has any idea as to where I did it wrong, or need more info, please holler. Thank you. ************* So, a small update: I managed to get a different result. Still no luck on getting it to detect the NVMe drive though. Gathered from several web pages out there, I think the problem lies with either the NVMee adapter, which seem to only support 2X (as reported by another computer with an identical adapter, although it's in an 16X slot (And the module should work at 4X, since that's its limitation). I also tried several other slots as this is a server motherboard it also have dual AMD Opteron 6378 16-core CPUs, thus it has enough bandwidth. The other probability is that Clover's NVMe driver doesn't support my motherboards. When testing on two other older computers, one with UEFI, and one without, I did manage to get it to save the log (F2-key in Clover UI), as well as screenshots. It doesn't list the GUID for the drive, but lists the other SATA SSD as well as the thumb drive. I was able to use the shell and access the command "pci" to list found devices, and it did see a "mass storage device" as "non-volatile memory", but no GUID. Here's where I'm suspecting the driver is failing. Although, the logs stated that it was loaded, but something about needing some configuration (don't have the log at the time of writing). I say, this Clover is a neat little utility, but the guys who made it sure as hell didn't make it even the slightest user friendly. I have almost 30 years of computer knowledge (Mostly DOS, later Windows, but a small dabble in Linux here & there over the years), so I'm not completely lost, but damn, I found this a complete mess, and GitHub is not easy to navigate, nor is some of the idiots out there who try to explain how to use it. I have yet to dive deep into some of the pages that I found links to, a Forum I think, to see if there's anything that would explain why it's doing this. Also, for some reason, on my UEFI-compatible PC, I was unable to get the shell64U (Says so, something about failing to load, then this name but no further info than that), and when I pressed F2 to get it to save logs, it threw EXCEPTION in mainly red on the left side, and some cyan blue on the right with garbage characters. If I ever get this working, I'm making several backups of this thumb drive because I don't ever want to redo this again, but that's a tall order right now. ************** So, another update. I tried something else, and lo and behold - It's finally working. I suggest you try this out if you're experiencing the same symptoms/problems as me: winraid.level1techs.com/t/guide-nvme-boot-for-systems-with-legacy-bios-and-uefi-board-duet-refind/32251/248 Just make sure to set BIOS to boot as UEFI on the boot devices (and probably set PCI devices to the same) I just changed that, since I got some "BErrorart" in red, and after making sure to boot in UEFI mode, it started right away and was presenting a menu that I worked so damn hard to get loading using "regular" Clover by following several other "guides". This just worked, right the F off from the start. Just make sure to follow the tutorial on the site and you can't fail, or, at least I hope it won't....
stavo per rimandare tutto indietro! questo video mi ha salvato parecchio tempo ed energie!
You could actually install clover to the sata ssd and configure clover to wait for 0 seconds at launch and to boot from the nvme drive. You could also use something like rEFInd instead as it supports legacy and efi boot too. To be fair, this could be done any number of ways, but you don’t actually need the USB key to store the boot loader at all. It can go on any drive the system can see on boot and then that points to and loads the target nvme. 😅 it shouldn’t be too hard - I’ll come back and update when I’ve gotten myself going.
Absolutely right 👍
what if you only have 1 storage device ?
@@Crux161 So how? can you tell me how to get rid of the need to use a usb stick?
When I write Clover to HDD ESP without USB, it can boot.
However, Clover's zeroTIME did not work and EnterKey input was required.
Brother please explain the process in which I don't have to always use USB to boot windows.
A little hint for old mobos with no uefi support to begin with,
Use clover legacy and an old clover version like 49XX or something, put windows installation thumb drive only when clover successfully boots,
You may need to exit clover, open the boot maintenance manager and navigate to the BOOTX64.EFI on the installation thumb drive,
Then after windows is installed, use microsoft efi boot from efi to boot the installed windows. (windows 11 didn't work with me)
Instead of disabling the USB drive it is easier to remove its drive letter in disk manager. This will not say it want to format it or the like anymore and safely remove it from the Explorer etc.
Thanks bro. Worked on my Optiplex 9010.
But how will we install the OS on the M2 disk if doesnt boot from BIOS. Will the disk shows up while installing Windows 10 ? I own Dell Optiplex 7010 MT
Normally it will show up while installing Windows 10. Otherwise you can insert the clover and the Windows stick at the same time and boot the clover stick. Then you can select the Windows stick in clover and install it. In my case the Windows stick was the first option in clover.
Thanks for watching.
@@pcandservertips8864 Let me give it a try, just ordered a PCI x16 NVMe card and once I get will need to order NVME and give it a try.
Clover works fine from the USB, but I can't get clover to install on an SSD and I just can't figure out why. There are several different methods for making this work, but none of them actually work on my X58 legacy system. There are a bunch of "how-to" articles that use UEFI BIOSes but at the point that your M/B has a UEFI BIOS, why would anyone want to use the clover UEFI emulator?
I already have this for my windows install but today I installed ubuntu on the same nvme ssd and it wont show up in clover can anyone help me?
When i try to install win 10 on nvme to pcie adapter like ur i cant install it goes back to install now
Q1 What is the min. USB stick you need for clover will 1GB stick be enough? Q2 I assume you first load windows ISO via USB and install windows 10 to the NVMe as normal (but the NVMe can't self boot). I guess after the install is finish you can then first boot to NVMe with clover.
Please check the link in the description, there are further informations. Q1: A 250MB USB Stick should be enough, clover needs 200MB. Q2 you can do it like you have suggested. I recommend to boot from the clover stick and select the windows stick in clover to install. You have to plug in both sticks. Thats how i did it on several computers and it worked perfect.
Link doesn't work anymore. I need to do this with a Dell Studio XPS 8100 from 2010. Any help?
how did you prepare usb clover
You can create latest version of Clover EFI Bootloader with "Boot Disk Utility".
@@モノノフ-n1j HOla y donde encuentro el boot disk utility, he tratado de instalar el clover configurator en windows y ninguno funciona
I need your help, after instaling kali linux, i can't boot it in to kali linux
How to set autoclover boot. ?
could you write me step by step. Because I don't understand steps.
For example, nvme must installed on board right?
this usb clover disk must plugged everytime for boot?
When I want to install windows I plug a windows usb disk on laptop and then > I will install that windows by the way another usb disk (clover disk must plugged)
I need these steps
the stick needs to be plugged in for every boot.
@@pcandservertips8864 So after boot i can remove the drive?
@@iambenji_1 Yes
man how to be done with this i can not boot the pc,, i need all time to boot from usb
You need to boot the usb stick all the time
can you post how to prepare usb clover thanks
Yes, viedo is in production :-)
You will find allways people like this! Useless videos no fruitfull
@@pcandservertips8864 Did you manage to make the video?
does dis work with m2 or msata?
Do this work on MSI Z77A-GD55
It should work on any Motherboard
Kannst du bitte mal zeigen wie man den USB Stick mit BootDiskUtility erstellt?
Can you set clover up default os on specific drive and or partition with custom timer waiting without enter button?
Yes, that is possible. It starts the system without entering a button.
Das Erstellen des USB Sticks mit einer älteren Version hat funktioniert. Ich kann von dem USB Stick booten und sehe die Startseite. Egal welchen Menüpunkt ich auswähle, es passiert nix. Kein booten, keine Fehlermeldung, es passiert einfach nix. Hast du eine Idee, woran es liegen könnte?
Ist auf der M.2 SSD Windows installiert?
@@pcandservertips8864 Ja, Windows 10.
did you somethng else in clover folder
I installed Clover on a USB stick but when I start Clover it still does not detect my NVMe. What should I do?
You need to copy the nvme file to the right spot on the stick. It is described in the instructions.
@@pcandservertips8864 can you explain how? That wasn't really clear in the instructions.
@@ermvcorleone3069 I concur. The readme is atrocious.
However, I read in another tutorial that was updated, which said that you needed to create folders for use with X64 Windows installations.
Also, the filename of that nvme driver was different than in the original readme, which was also explained.
I followed the tutorial as best as I could, but I get pretty much a blank screen with a few options in very small font, and for each option selected I get nothing.
It did however list a few different boot devices, but no NVMe device.
My mainboard is quite stupid. It has UEFI support, but not for NVMe (I have an PCIe adapter for it). Windows can detect it and use it, so no problem there.
However, this Clover utility has some documentation, but needs a proper tutorial for a basic setup, not that smear of keyboard keys that it currently has.
Tried to find that post, but it would seem I have misplaced it somewhere...
On my USB-stick however I made these folders, as instructed:
x:\EFI\CLOVER\drivers64uefi
x:\EFI\CLOVER\drivers32uefi
Into which I copied the file NvmExpressDxe.efi taken from x:\EFI\CLOVER\drivers.
I also copied the folder structure (with content) to these parent folders (x:\EFI\CLOVER\drivers64uefi and x:\EFI\CLOVER\drivers32uefi)
I didn't see anything that would indicate that this/these files would have to be specified in x:\EFI\CLOVER\config.plist or anywhere else in that readme.
It would seem though that you need two USB-sticks (Or one for the Clover, CD/DVD/USB/other media for Windows) so that this can boot Windows install or regular installed Windows.
Problem for me lies in that Clover simply doesn't find the NVMe device at all.
There's another option, equally as poorly documented way to get an PCIe NVMe device to be recognized in UEFI/BIOS, and that entails you to modify your BIOS. I tried that too, but still can't find that damn device.
Whenever I disable the CMS my BIOS beeps in error, restarts and re-enables CMS again.
I remember some +10 years ago when I sat with Windows Vista, I think. Not sure, so long ago, but I was able to install Windows on a USB device, and I had installed Windows on a local disk at the time, and I installed another version on that USB disk, and the boot loader read the boot disk and fired up that USB driver and successfully booted from that USB disk. This should be about the same, but it's so far from it.
Just for an experiment I installed Windows 7 on an SATA SSD to get a boot device. I then upgraded to 10.
Found an old Windows 10 installation that I had on-disk and ran it (The newer versions need product keys, which I have, but were not accepted). Anyways, I did install it on the NVMe disk, in hopes that it would fix that bootloader, but it simply just reboots once it tries to boot it.
I read that GPT could be an issue, so I converted it to that from MBR, still the same thing.
This is disappointing as I was hoping to upgrade my old Dell server the same way (except for the BIOS which is too old) so that it could become much faster, and I don't feel like using an NVMe as a secondary disk as I would still need to have another disk to boot from.
Yesterday I tried some different configurations.
Also tried it on a non-UEFI-computer, and to my (very) big surprise, I got a menu from which I could then select boot device.
However, it refused to boot at all on the NVMe drive. It just said something about not able to read files, then it just froze up. One guess would be the file system not being correct, although I converted it to GPT earlier. Might be corrupt, and I have some stuff on it that I didn't want to lose.
On my SATA SSD however, it booted Windows 10 just fine.
But it was unable to boot either of the two USB-sticks on which I had Windows 10 installation on. Froze there too.
I'm also very surprised that Clover didn't detect a boot-CD, which I took for absolute granted that it'd do. That was a certain no-brainer for me.
Turns out that it doesn't support it. You can make a boot-CD with Clover, but doesn't do any good if it can't even read a CD, and seeing as how unplugging a USB (with Clover) crashes the entire computer, I fail to see that it would allow for a CD-swap.
I also tried tossing in another driver (in all folders I previously mentioned), which I currently can recall what it was named, but it suggested iGPU in the name, which would be CPU's internal graphics, so I yanked the PCIe GPU and went on the on-board graphics card, but still no graphics/menu.
However, there was one thing that was new, although I can't remember when exactly it happened, but as I chose, I think, bootmanager or boot-device manager (?) from the non-graphic menu (Which btw, is all-white), I was able to select boot from image, from which I selected x:\efi\boot or whichever it was.
That was from the USB-stick containing the Windows installation program.
Did get it to boot, but it was unable to get pass the selection of disks as it refused to install on the NVMe-drive.
Something's is very FUBAR with this Clover, that's for damn sure. Mostly annoying is that it almost worked on my old POS computer, but freezes up, while on my semi-supported UEFI-computer it doesn't seem to load the GUI properly and there's no visible log to check, and no way to exit to the shell.
It seems that it's based upon Linux, but the kernel-stuff doesn't load any interpreter so you only have basic commands (Type: "help" to list available ones), but a few of these makes no sense that they're there, but that's besides the point.
Clover needs to be more universal before it can be useful for weird computers. This is actually the only real issue I've had with this machine, an ASUS P8H77-V LE motherboard, i5-3570 CPU. BIOS is atrocious to deal with when it comes to CMS. Disabled it refuses to get past the NVMe to PCIe-card. It beeps, then resets the parameters and CMS is enabled again. Then there are a few options that allows me to continue, for eg. if I put an UEFI-flashed USB-stick in the USB it goes past that. Don't remember exactly, but I did a combo och BIOS-settings along with that stick, but there was an error that meant I had to press a button to select the next boot medium, so no automation there....
Hello , nice helpfull video , i see u used DELL Workstation MOBO may its T3610 , are you use standart ATX PSU or some adapter.
I make my own 24pin mobo supply adopter
Is your nvme ssd drive has clone window on it , did u disconect all HDD exept Nvme ssd before you restart , your guide is appreiated . I tried but it is not work .thanks
I did a fresh install on the NVME
Thank you!
link of the program to boot the pendrive
Link for the forum thread ist in the description
@@pcandservertips8864 no esta en la descripcion
donde descargo clover??
Thank you for this Video. I want the COLVER soft. Would you like tell me, Where to Download the soft, and how to install to the USB.
Thank you, there is a Link in the describtion how to do this
Link down, could you please reupload it?@@pcandservertips8864
hi my friend, I need a personel help I tried everything but I m doing wrong things I guess. Please help me
I have Acer vn7 571g and I bought crucial P2 CT250P2SSD8 250 GB disk, I install windows but it can't boot I tried everything But this way to solve this I couldn't do, please help me
Hi, i will try to help. I think the problem is that your notebook only can use Sata SSDs and this is an M.2 NVME. The trick with the USB Stick only works on desktop computers with an PCI-Express adapter.
Does the drive show up in the BIOS?
Does the Windows installer see the drive when you run it on the notebook?
@@pcandservertips8864 Not show up in the bBIOS, but windows installer see that disk and install windows but does not boot :( if we have a chance we can look up via teamviewer or something else
@@pcandservertips8864 I can install windows but BIOS doesn't see the drive. When I install windows it cant boot I couldnt recognize usb stick - windows installation - nvme plug how can I do I don't know. could you help me via team or something ? I can't use my laptop for 2 weeks I need it
@@alien6334 www.win-raid.com/t2375f50-Guide-NVMe-boot-without-modding-your-UEFI-BIOS-Clover-EFI-bootloader-method.html follow this instruction, you should be able to boot the stick and select the drive.
hallo , geht es auch mit msi z77 g43 - cpu ist 3570k ?
Ja das geht auf jeden Fall
remove drive letter of usb on disk manager
thank you alot
Cool!
Link down :(
Thank you, i put the new link in the describtion.
tyvm@@pcandservertips8864
Nyc
motherboard is look like from world war 2
It works fine without any fancy LEDs and cover plates ;-)
Try using a real camera instead of a potato the next time you record a video
Yes, i will try 😁
I have a question for you guys regarding "PC that can't boot NVMe".
We have a PC with "SATA-HDD+NVMe-SSD only, Linux installed on HDD, this is Tool, Clover written on HDD-ESP, 21H2-USB installed on SSD, when rebooting, WindowsBootManager is at the top of the list. Enter UEFI-BIOS configuration mode, rearrange the order to Clove's kick (hd1,gpt1)/EFI/clover/CLOVERX64.efi (hd1,gpt1 at the top, Ubuntu - 2nd, WindowsBootManager - 3rd, HDD - top 4th, and reboot) The installation continued, the SSD became the start screen, and Win10-21H2 was successfully installed and rebooted.
Question
Can you please write down the main points and the order in a way that I can understand?
No.
I plan to do this in turn to other "NVMe unbootable PCs".
Translated with www.DeepL.com/Translator (free version)
***************************************
Solution at the bottom of this text:
***************************************
Does anyone know what the hell is wrong with my stuff?
I've tried numerous configs, and bit by bit I'm almost getting it to work.
First from a white background (CSM, and wrong version of the file "boot" in root folder of USB flash drive), to an almost usable menu like show in multiple images & clips, except no disk icon, until I hooked up my SATA SSD it showed three disks, and the first one booted that SATA drive, no surprise there, but was unable to do so with the other two.
I could understand if the NVMe SSD that I have in a PCIe slot wouldn't boot due to mongoloid partition (MBR/GPR), it's just that without the SATA SSD, nothing shows up so I'm unsure what the hell's going on here. According to some tests with one configuration with the USB-stick (Tried multiple times) I was able to see (In shell mode) that the driver for NVMe had been loaded by typing "drivers", so it should by all accounts, work. But, no disk is displayed.
I tried with installing Windows from another USB-stick in UEFI-mode to the NVMe-drive. The installation went like clockwork. Partitions were erased prior so it was blank.
I read in some forums that the partition need to be GPR, so I tried to convert it in one attempt, but I was unsuccessful.
I'm running out of ideas, so anyone has any idea as to where I did it wrong, or need more info, please holler. Thank you.
*************
So, a small update:
I managed to get a different result. Still no luck on getting it to detect the NVMe drive though.
Gathered from several web pages out there, I think the problem lies with either the NVMee adapter, which seem to only support 2X (as reported by another computer with an identical adapter, although it's in an 16X slot (And the module should work at 4X, since that's its limitation). I also tried several other slots as this is a server motherboard it also have dual AMD Opteron 6378 16-core CPUs, thus it has enough bandwidth.
The other probability is that Clover's NVMe driver doesn't support my motherboards.
When testing on two other older computers, one with UEFI, and one without, I did manage to get it to save the log (F2-key in Clover UI), as well as screenshots.
It doesn't list the GUID for the drive, but lists the other SATA SSD as well as the thumb drive.
I was able to use the shell and access the command "pci" to list found devices, and it did see a "mass storage device" as "non-volatile memory", but no GUID.
Here's where I'm suspecting the driver is failing.
Although, the logs stated that it was loaded, but something about needing some configuration (don't have the log at the time of writing).
I say, this Clover is a neat little utility, but the guys who made it sure as hell didn't make it even the slightest user friendly.
I have almost 30 years of computer knowledge (Mostly DOS, later Windows, but a small dabble in Linux here & there over the years), so I'm not completely lost, but damn, I found this a complete mess, and GitHub is not easy to navigate, nor is some of the idiots out there who try to explain how to use it.
I have yet to dive deep into some of the pages that I found links to, a Forum I think, to see if there's anything that would explain why it's doing this.
Also, for some reason, on my UEFI-compatible PC, I was unable to get the shell64U (Says so, something about failing to load, then this name but no further info than that), and when I pressed F2 to get it to save logs, it threw EXCEPTION in mainly red on the left side, and some cyan blue on the right with garbage characters.
If I ever get this working, I'm making several backups of this thumb drive because I don't ever want to redo this again, but that's a tall order right now.
**************
So, another update.
I tried something else, and lo and behold - It's finally working.
I suggest you try this out if you're experiencing the same symptoms/problems as me:
winraid.level1techs.com/t/guide-nvme-boot-for-systems-with-legacy-bios-and-uefi-board-duet-refind/32251/248
Just make sure to set BIOS to boot as UEFI on the boot devices (and probably set PCI devices to the same)
I just changed that, since I got some "BErrorart" in red, and after making sure to boot in UEFI mode, it started right away and was presenting a menu that I worked so damn hard to get loading using "regular" Clover by following several other "guides". This just worked, right the F off from the start.
Just make sure to follow the tutorial on the site and you can't fail, or, at least I hope it won't....
how did you prepare usb clover
I make a how to Video soon