How to convert a basic disk with Windows 10 installed to dynamic?

Question

Windows

There is a laptop with a built-in 64 GB disk (the system is on it). Also included is a purchased Plextor 512 GB PX-512M8VC drive. It was purchased specifically in order to install the system on it instead of the built-in one. But it didn't work out. Hence the idea to make both of these disks dynamic in order to use them as one whole. Plextor has been quietly converted from basic to dynamic by means of Windows. But the boot built-in does not want to. Windows Disk Management gives an error:

Other programs (such as Acronis Disk Director) also give errors.

So the question is how to convert it to dynamic?

PS Also, in principle, the question about installing the system on a purchased disk remains open.

Answer 1

I understand that the answer to my question can be one:

You cannot convert a basic Windows disk to dynamic. Especially, being at this moment in this very Windows.

But the original problem, which caused the current question, I solved.
All the same, we managed to transfer the entire system to the purchased SSD using Paragon Hard Disk Manager, and format the built-in eMMC. Now the laptop boots from the new drive and everything seems to be working. At least I am writing this text from a cloned system.
Thanks everyone for the replies. All were very interesting, and some pushed to solve the problem.

Answer 2

And in any way, windows Does not support loading from dynamic disks.
But if you really need it, then download the iso image of some aomei part assist / pagagon hard disk manager
, upload it to a USB flash drive and just go.

It was purchased specifically in order to install the system on it instead of the built-in one. But it didn't work out.

Maybe you should look for reasons why you can not install the system on ssd?
When installing, the error says why it didn’t install
But if it’s so difficult, then I’ll tell you how to install>
1 pull out the built-in disk, insert the purchased one
2 make the disk basic! convert the GPT disk, delete all partitions, enable UEFI in BIOS
3, fill the image with ultra iso in usb hdd + v2 mode, or with rufus in fat32
Done

Answer 3

Yan wrote that

windows Does not support booting from dynamic disks.

I checked and it doesn't seem to be the case:

For all usages except mirror boot volumes (using a mirror volume to host the operating system) , dynamic disks are deprecated. For data that requires resiliency against drive failure, use Storage Spaces, a resilient storage virtualization solution. For more info, see Storage Spaces Overview.

https://docs.microsoft.com/en-us/windows/win32/fil...
This is how Microsoft suggests preparing a dynamic disk for installing Windows Server on it. It remains an open question whether not Server, but ordinary Windows can be installed this way, but I think it can.
One problem: to convert disks to dynamic, they must be empty. At one time, I tried by hook or by crook to convert a dynamic disk to a basic one without deleting partitions and saving data, and none of the many utilities helped me: neither Acronis, nor any else. Acronis stupidly rebooted, not even trying to do something at boot, the rest knocked out errors. One of the disks, the last one, completely refused to turn into a base one. And all this was not with boot disks, but with ordinary ones. So apparently not everything is so simple with these dynamic disks.
Therefore, I propose an alternative approach: use Macrium Reflect or other software to your liking to transfer the OS to an external drive (do not forget to check if it works), kill all partitions on all internal drives, merge them into a dynamic one according to the guide and transfer the system back.

Answer 4

If I understand correctly, windows limits the use of dynamic disks on a removable drive, which is why such an error occurs, but even if not, you will be able to make the disk dynamic (manually using the standard diskpart console utility, there are not a lot of restrictions on its graphical counterpart, maybe here ride), that is, another limitation:
https://ru.wikipedia.org/wiki/Dynamic_disk

Windows cannot be installed on Dynamic Disk, which has an unpleasant consequence - of all Dynamic Disk RAID configurations, only a “mirror” can be a Windows boot volume (installation is performed on a regular disk, then it is converted to Dynamic, then a “mirror” is created by adding a second half, this is not possible with other RAID configurations).

In theory, it will probably be possible to try to install windows on the second disk using a virtual machine, and by disabling secure boot and uefi (in the BIOS it can be called legacy boot) boot using, for example, grub installed on the first system disk, but the installation process itself may not be simple.
ps If you need to expand the system disk, then you can use symbolic links by moving directories, incl. Program files, ProgramData, MSOCache,.. and possibly some of windows (with care) to another drive and leaving only links to it on the first one. I also remember creating symbolic links to the directories where the system puts major updates ($WINDOWS.~BT it seems) but you will have to do this every time this update arrives, in general, monitor the use of the system disk (I tried to keep windows running on an old machine with built-in 32GB disk, transferring some files to a memory card, this is real but dreary).
be sure to dig into the user profile, a lot of applications store gigabytes of information there, including the application itself, everything is perfectly destroyed by symbolic links - AppData\Local\move_this_directory , AppData\Local\Roaming\or_this
There is a difficulty with the windows directory, its size is about 24GB (20GB ntfs compression) and it is difficult to move anything from there. The fact is that removable disks are not immediately available in the system, and if you move critical system files to such a disk, the system will not be able to boot. Another problem is the copying process itself, ntfs symbolic links, access rights are very actively used inside, and if I understand correctly, even ntfs file stream, but I didn’t check here, and not every copy tool is able to correctly duplicate the data structure, taking into account links, especially this is difficult, since such an operation will have to be done from another OS (booting from a USB flash drive, for example). In general, I remember breaking the installation by making a copy in Far Commander (i.e. everything worked, but the system disk then began to take up much more space as a result).
Using a wim image can help a little (the compression is slightly better than ntfs), but after every major update, you will need to update this image, otherwise it will only get worse.