Hello Igor.
Thanks for reply. I have to mention, when boot my Virtual disk service, I do receive message from Windows about disk #11. Disk # is not online and needs to be initialized. If I click on a new message, the device is not ready. Up until now, I have not focused on this message and whether it has any meaning at all, just my desire for a clean installation. I suspect this device to be a 6TB Western Digital with a fault in either the SATA III or the power cable.
Here you see the picture of my disks, where disk #0 is the bot disk. The disk was prepared for a clean Windows installation, only Windows, and later an image storage of the OS was restored. During the allocation of the size for this boot disk (DISKPARK), that part, the partition, was not optimally sized in relation to what it can be at most (930.84TB). But I'm not sure why, if anything, this relationship could have any impact on a successful clean installation with keeping apps?
The volume for disk #0 is a pre-mounted m.X2 SSD placed on the MoBo. I see from the image of Volumes that disk #0 has 2 partitions (in volume image of the device), while the graphical image (Dynamic) of the disk shows 3 partitions. Partition 2 is 100MB, EFI system partition, no file format. Partition 3 is 589MB, basic data partition, NTFS file system. Partition 1 must be the accessible data area partition and is NTSF formatted file system.

Disk 1 is equal to tisk 1 in SSD type.
