@sibliss thank you for your quick response. It is so wrong that all those softwares allow users to clone the OS without noticing them that they have to run Sysprep first and the run their cloning software from a live-CD.
"The disk does not have any extended/logical partition". I have 4 logical partitions that I need to deal with before any attempts. (I have: System Reserved, Win 10 partition, two for storage, and 3 for Ubuntu ). For now, let's assume I have dealt with this issue.
If I do the conversion, the old OS will no longer boot in legacy BIOS but both old and new should show up in Clover, right? Also, once the conversion is done I will have to use Sysprep. The only modification that Sysrep will to is that I will have to use the OOBE again (on both the old OS and the cloned one) and my files/programs won't be changed, right?

@mariustelcean
Unless you have a really old motherboard I would be surprised if it can't boot the old drive once it's converted to gpt and yes you can always boot it through clover.
The use of sysprep if you can get it to work is alot more than just the oobe sysprep actually removes all the identifiers from the os image, thus hopefully you shouldn't need to stuff around with registry hives. To the best of my knowledge you shouldn't loose any data from doing the sysprep, just remember there is a limit to how many times an image can be set in sysprep but you get a few go's and it only counts if sysprep works there are a heap of reasons why sysprep may fail though so you will have fun with that.
Good luck and happy modding.

@sibliss My motherboard: https://www.asrock.com/mb/AMD/760GM-GS3/
I read on the link you provided that you can't revert the partition table back to MBR and be able to boot again. So much trouble for not being able to transfer some programs that were tailored to my needs...
"here is a limit to how many times an image can be set in sysprep but you get a few go's and it only counts if sysprep works there are a heap of reasons why sysprep may fail though" I will watch some YT videos before doing it. Maybe it will help.

Hi all, my first post here and thanks for all the information.

Here is my setup:

My motherboard: https://www.asus.com/Motherboards/M4A785DM_PRO/

Specs: https://www.asus.com/Motherboards/M4A785...specifications/

Its has : AMI Bios ver. 1001, with an AMD Phenom II X4 9650 processor, windows 10 dual boot option of a linux Dist.

From reading ths thread i was confidient enough to buy a NVMe ssd with an adapter off Amazon:

https://www.amazon.co.uk/gp/product/B07J...0?ie=UTF8&psc=1

https://www.amazon.co.uk/gp/product/B07R...0?ie=UTF8&psc=1

First i hope it will all work for me given my setup above, what i want to know is this:...can i partition the nvme ssd in 2 partitions ? before insalling windows... one for windows and one for linux for dual boot?

Thanks for your help,
D

@Damoedge
Hi and welcome to the forum I see no reason why that ssd and adapter won't work with your setup.
I also have a dual boot setup on one of mine incidentally also and Asus m4 series board.
The easiest way is just to install Windows first as normal then simply shrink the large partition via partition manager leaving the free unused space at the end of the drive.
then you can just tell Linux to install to that space as usual during setup it's not much different to normal dualboot except that we use clover as the bootloader.
....my clover shows both Windows and Linux partitions and boots them just fine. One of the reasons I prefer the clover option.

Hello, my name is Thomas and I come from Germany. I registered here because I can find very little information about booting with Clover in connection with a PCIe NVME adapter in German forums. The topic is probably not widespread in Germany.
Please excuse my bad english. I don't speak this language very well and so I use Google Translator.
I haven't read all the posts in this thread yet. It is very difficult for me to understand everything.


I have the following problem:
I created a USB stick exactly according to the instructions described here. I first installed Windows 10 and then W10 started normally via Clover. The system was completely redesigned.

However, it happens very often that W10 suddenly "no longer starts". I first see the CLOVER boot menu and then only a black screen for about 10 seconds. The computer will then automatically restart and try again. However, all attempts fail.

However, one thing is very strange.
If the computer is in the CLOVER menu, the preset time of 5 seconds expires. If I navigate to another drive with the arrow keys in these 5 seconds (it doesn't matter which drives / partitions I navigate to) and I want to boot from this other drive, of course nothing happens.
And now the strange .......
Since the computer cannot boot from the other partitions, of course, I have to switch the computer off manually (power off).
Then I restart the computer (Power on) and now select the correct partition W10.
Then, and only then, will W10 start.

I don't know where this behavior comes from.
I have already tested all possible settings in the BIOS, unfortunately without success. I also tested several USB sticks and various USB slots in the computer. Unfortunately without success.

Here are some data about the computer:
Fujitsu m730 Power Workstation, 32 GB Ram, latest BIOS, XEON 2667 v2, Quadro K5000, PCIe NVME adapter, Samsung 970evo 1T, W10 with all current updates


I thank you for your valuable time.


Thomas

@THomas
have you ensured to place the NVMExpressdxe file in the correct places on the usb as mentioned in the updated link at the top of the first post ? you are required to always boot from the USB.

@sibliss
Hi, yes, I hope so. NVME file (NvmExpressDxe.efi) is in following folders.
Boot_Stick:\EFI\CLOVER\drivers\BIOS
Boot_Stick:\EFI\CLOVER\drivers\UEFI


Thank you very much


Thomas

@THomas
i would also try copying the driver this this folder it will do no harm
Efi\CLOVER\drivers32uefi

you may also like to run some repair utilities from within windows it seems that perhaps the windows bootloader needs fixing.
you could try tools like
Bootrec /fixboot
Bootrec /rebuildbcd
they may help, i will generally also advise doing an SFC /scannow aswell

beyond these though the issue must be in the clover config.plist somewhere it is hard to say what you will likely need alot of trial and error to figure it out.

@sibliss
Many thanks for your help. I just searched the "Clover_Stick", but I do not find a folder with the name "drivers32uefi"

Thomas

@THomas
if you read the additional and updated information i had pinned to the first post you will see that i did say you may need to create it if you don't have it.

Zitat von sibliss im Beitrag #493

---

If it still isn't booting and detecting the nvme drive Some users may also need to create the following directories (unless you already have one or both) and copy the NvmExpressDxe driver to them aswell

Efi\CLOVER\drivers32uefi
And Or if 64 bit (try this instead if you found you had x64 folders in the above section)
Efi\CLOVER\drivers64uefi

---

Oh shit, I probably didn't read that.
I just saw that this note is at the top of Post #1.

I have now created both folders and copied the NVME file into these folders.
Until now, restarting the computer works fine.

I would like to thank you very much for your advice and your time. Thanks. You have helped me a lot.

Thomas :-)

Hello

MB: M5A97
disk is gpr

I followed the first post and the latest revision to add the driver into the drivers32uefi and drivers364uefi folders.
Somehow I cant start clover in uefi mode (I just got a black screen) so I used legacy clover.

if I use "Boot Maintenance Manager"->"Boot from file"->efi/boot/bootx64.efi I can install win10pro on my NVMe SSD with an adapter till the first restart. Then it boots back into the clover and won't boot/find windows.

Maybe someone has an idea?

@temm
I would advise to place the driver in all 3 of the uefi folders anyway as it will not harm the configuration in anyway.

The use of legacy clover is perfectly fine for our purpose as once we hand of to the windows bootloader it will do it's own thing anyway.
normally not being able to see the nvme drive in clover is because the driver is not being loaded correctly or the drive is not formatted correctly as you've already stated you are already running gpt i suspect driver.

Please note you can of course manually edit the clover config.plist further to change various clover behaviors such as which drives to show under clover and which ones to hide.

Hey guys! Just a little question 🙂
Usbkey should I always keep inside?