@krasnit

Zitat von krasnit im Beitrag #434

---

Has anyone ever managed to install Clover boot manager on a GPT hard drive? For those that have a UEFI BIOS which does not support NVME it would be useful if the Clover boot is on a hard drive larger than 2tb. That way, you can use the remaining portion of the Clover drive as a large data drive while using a NVME PCIE for the system and main Windows OS drive.

---

So I must be doing things wrongly to make the Clover boot hard drive. When I use BDU to make the Clover on a GPT hard drive I click format, but that wipes everything and changes the hard drive back to MBR. Is there another procedure to make the Clover drive that would retain the GPT on the drive?

It works !
Sorry for a long time, I had no time to write back.
It turned out that the main problem was a poor USB stick with Windows, I checked on another computer and had bad sectors.
I added the nvme driver with the Gigabyte Windows USB Installation Tool.
In addition, when booting through a Clover disk from BTU, you need to press F3 and then a hidden disk appeared.

I found a much better way of installing Clover for my needs under Windows than using BDU:

https://www.aioboot.com/en/clover-bootloader-windows/

With this way, you can update Clover without wiping your whole disk, and it works for GPT drives.

Remember Clover is designed for fooling macOS that its running on Apple hardware when in fact its running on a PC.

So given this thread is about Windows, any driver loading is purely for Clover (like the NVMe driver) as option roms loading and the rest of Clovers features are purely for Apple macOS.

I have successfully (and simply) installed a fresh Windows 10 and got it working through Clover BUT I spent a day last week trying to get a legacy Windows system to boot via NVMe and nothing worked. I was trying to clone an existing Windows 10 installation on the NVMe using the normal tools.

What I think I have discovered (correct me if I am guessing wrong) is that Windows 10 will only boot on an NMVe drive if its called from an UEFI and the drive must subsequently be formatted as GPT (not MBR). You can't clone an existing MBR partition onto a GPT partition. No matter how hard I tried (and I tried!) I couldn't get Windows 10 to boot from the Clover legacy boot options.

Clover appears as a UEFI boot device to Windows, so thats OK, and if you wipe the NVMe and install a fresh copy of Windows 10 on it, Windows will use GPT and all works via EFI Boot. If you want to Clone an existing Windows 10 install from an MBR partition then...

1) Install a fresh copy of Windows 10 on the NVMe drive and get Clover to boot into it.

2) Backup your old Windows 10 installation and then convert it from MBR to GPT using the Windows tool designed for that purpose. You can do this by booting the fresh install of Windows 10 but you may also be able to do the conversion directly too (to the same drive you are booting from).

3) Then Clone the main Windows partition only (the big one) from the old drive to the NVMe drive.

Thats how I managed to Clone an MBR Windows 10 onto a legacy BIOS machine through Clover....Phew...

The free version of EUSEUS Partition Manager will easily convert an MBR to GPT keeping all tha data intact. I have used it to do this, but it has also on occasion given me problems, so I would clone the drive first to have a backup.
I find it curious that Windows 10 on a MBR NVME will not boot through Clover, because it will boot vanilla USBs with an OS on them such a s Linux as well as ordinary MBR hard drives with OSs. There is nothing about a NVME that requires it to have an EFI partition to boot. The problem may be that UEFI BIOS uses Window Manager to boot the MBR disk which it automatically sets up, but Clover does not. You may have to reset the Windows boot configuration on your NVME for Clover to direct the BIOS to it. Have you tried booting a Windows repair disk for the NVME MBR Windows? I think the repair disk has NVME PCIe drivers to recognise the NVME MBR installation.

You need to copy the system partition aswell not just the big partition as Windows requires that to boot (it seems the commenter above used the system partition leftover from the clean install)
you also need to adjust some registry settings as mentioned in one of my previous comments ( I linked to another site which explains that ) so that it has the correct drive ID to boot from. Also you may wish to copy over the recovery and backup partitions aswell if you have them.
On Another note Windows 10 will always natively prefer and will by defualt set a drive to GPT when installing and formatting. most of the time an MBR install is the result of one of these two things performing an in place upgrade to Windows 10 from an older Windows installation which is MBR such as Windows 7 or deliberately opting to install Windows 10 to an MBR drive.
I have also got a suspicion that the nvme driver in clover is expecting uefi ready drives ie drives running GPT partition table system over MBR but I cannot say for sure.

Not NVMe, but it should work with NVMe as well :

^I copied all system files from my main PC's EFI partition (GPT drive).

@agentx007
I'm actually surprised it works with the EFI/system partition at the the end of the drive not at the start.... it used to be that the bootloader had to be within i think it was the first 200mb of the drive and therefore the system partition always had to be at the start of the drive.
by the way nice way to copyright your image
But i would highly recommend against copying a system partition from another computer as it would likely cause miss-configuration issues for the bootloader in said system partition.

I always thought "active" flag for partition takes care of where BIOS/booting software searches for files (where partition is located doesn't matter).

Actually, you are first one since I'm started doing this (that's 10+ years), to actually see it as copyright method ;)

I planned to use BCD Edit to "correct" any issues that may arise from copying EFI partition.
However, it simply worked for me.

@agentx007

Zitat von agentx007 im Beitrag #445

---

I always thought "active" flag for partition takes care of where BIOS/booting software searches for files (where partition is located doesn't matter).

Actually, you are first one since I'm started doing this (that's 10+ years), to actually see it as copyright method ;)

I planned to use BCD Edit to "correct" any issues that may arise from copying EFI partition.
However, it simply worked for me.

---

This is a follow-up to using Clover in my experiments of running Windows 10 Enterprise from a NVME PCIe drive whose motherboard UEFI Bios does not support booting from such PCIe drives. If one recalls, I managed to install Win 10 Enterprise by first installing the Pro version and then updating to Enterprise, and then used PCMover to transfer all the apps and documents from the old clunker system hard drive. All done it worked, but I was having problems connecting the machine to the workgroup. But there is a much easier and sure way.

The free version of Easus Partition Manager also allows migrating a system disk to a SSD. For this, one uses the migrate OS feature, not the clone disk feature. Because Easeus PM uses the Windows OS to perform its operations at boot-up, it loads NVME drivers first, so Easeus can see the NVME to migrate the old system disk to. The operation is flawless and works 100% and saves hours of work. It will even migrate a larger system drive onto a smaller SSD if there is enough room for all the data on the SSD. All you need to do is to boot the appropriate drive through Clover boot manager first, for instance, using a Clover USB stick. Once migrated, you use Clover boot manager to boot the NVME drive as usual. To do that, I re-use the old clunker drive by putting a small fat32 partition (200mb) for Clover on it, from which the boot process starts, as per my post further up. The rest of that clunker is used as a large data drive. No need for USB Clover sticks. And my link above allows you to update Clover at any time without destroying any data on the drive.

The whole point of all this is to gradually upgrade computer systems. It makes no sense to get SATA SSDs because they are much slower than NVME PCIe SSDs and only a bit less expensive. Even with only PCIe 2.0 support on the motherboard, the NVME PCIe will still be faster than a SATA III SSD. Eventually, the motherboard can be upgraded to one with PCIe 3 and a UEFI Bios that supports NVME booting, which are already common and prices are dropping. At that point it will be a simple matter of putting in the old NVME drive into the new motherboard as all the work of setting up the migration will have already been done- and in the meantime the user will profit by the old system's much higher speed now.

Hello

I bought a Corsair MP510 (960GB) plus an PCIe adapter card and what should I say its not working.

My system Asus P6X58D Premium (2010 or 2011)
Bios 1501 (from 2011 its the newest version)
I7 CPU 930 (triple channel)
18GB RAM
GPU: GTX1060 (6GB)

I tried to install Win 10 on the new disk, and as expected the system could not boot.
So I tried this boot manager. Generated the clover disk (also copied the NvmExpressDxe.efi to EFI\CLOVER\drivers\BIOS and EFI\CLOVER\drivers\UEFI) and started the loader. But in the loader, I never see the PCI-SSD. I see the USB-sticks and Hard drives. If I try to boot from one of them the system goes back to the clover main screen and nothing happens. If I go to “continue” also nothing happens.

Here the screenshot of the Bootloader, and yes its seems different from the other how have a graphically surface. And also, a screenshot from my bios.

Please could anybody help me?

@no_good_name

Zitat von no_good_name im Beitrag #448

---

Hello

I bought a Corsair MP510 (960GB) plus an PCIe adapter card and what should I say its not working.

My system Asus P6X58D Premium (2010 or 2011)
Bios 1501 (from 2011 its the newest version)
I7 CPU 930 (triple channel)
18GB RAM
GPU: GTX1060 (6GB)

I tried to install Win 10 on the new disk, and as expected the system could not boot.
So I tried this boot manager. Generated the clover disk (also copied the NvmExpressDxe.efi to EFI\CLOVER\drivers\BIOS and EFI\CLOVER\drivers\UEFI) and started the loader. But in the loader, I never see the PCI-SSD. I see the USB-sticks and Hard drives. If I try to boot from one of them the system goes back to the clover main screen and nothing happens. If I go to “continue” also nothing happens.

Here the screenshot of the Bootloader, and yes its seems different from the other how have a graphically surface. And also, a screenshot from my bios.

Please could anybody help me?

---

Thanks for your help,

meanwhile I found a solution to install it with another bootloader. So I can start Win10… but its not working correct.
Now I have the problem that win10 is running very slow… about every 5 seconds the system “stops” for 0.5 seconds. Soundstops, mouse and for example if I try to play a game, the game is as fast as if I had no GTX 1060 inside.
I know from old Win7 that I have to install the x58 drivers. After installing x58 drivers everything was ok. The Problem is there are no x58 drivers in Win10.
On the https://www.intel.de/content/www/de/de/s...processors.html there stands that my CPU (i7 930 Nehalem (Bloomfield)) is not supported anymore… Installing the drivers manually also failed.
No idea how I should fix this…


update: I removed the nvm and installed Win10 on a SATA... same Problem. Mouse and sound "stops" ervery 5 secound. GPU ist not working with fullpower