New
#11
When I created that install, I had a flash drive created with the Media Creation tool. I just ran it, selected the drive to install, and the Install did what it wanted to.
When I created that install, I had a flash drive created with the Media Creation tool. I just ran it, selected the drive to install, and the Install did what it wanted to.
It says it's partition 5.
So
Diskpart
Sel Disk 1
List Part
and you have the partition numbers in order if you can't tell from the partition manager.
Earlier I gave you another method as well.
fireberd, As it is now, you need drive 0 to boot into the NVMe drive
If I were you I would make the two drives independent:
- I would create a 100M Fat32 on the NVMe drive and install the boot manager on it.
bcdboot X:\Windows /s W: /f UEFI
Replace X: with the partition letter assigned to the Windows partition when booting from disk 0
W: is the partition letter temporary assigned to the Fat32 partition created on NVMe drive
- Once you able to entirely boot from the NVMe drive with drive 0 detached, I would create a disk image of drive 0 partitions 2,3,4&5, clean the drive and then recover the partitions expanding partition 4 almost to the end leaving 650M for partition 5 (recovery partition)
Just for s & g, wanting to test the 2.5" drive anyway and having to mow the yard I did a hardware clone of a 3.5" 250GB HDD to a 2.5" 1TB SSD, only took about 1.5 hours. Hardware cloning does Byte for Byte, no manipulation.
After it was done I removed the 250GB HDD, reconnected the USB 3 cable and used Disk Management to create the New Volume. The dock I use for hardware cloning cannot be connected to a computer during the process.
Old Volume = 232GB New Volume = 698GB
The reconfigured drive booted OK the first time I tried it. This drive is for my recording studio and only used when needed. I went back to the other Win 10 as that is the default on my dual boot. All was "well" until I rebooted and it came up with an error and wouldn't boot. I had to recover by booting with a Macrium Reflect rescue USB drive and a boot repair (on my main drive). After booting my main drive I then used Easy BCD to add the recording drive and now back to dual boot.
FWIW here is current drive configurations.
Drive with partitions unallocated (I'll reconfigure later)
Primary Drive
@Megahertz
I have some questions on what you posted above.OK, so one Recovery partition is created when first installed Windows on Sata disk, how does the 2nd active Recovery Partition for NVMe SSD get created on the SATA disk ?Be careful. As You have two Win 10, one on the SATA drive and on on the NVMe, you have two active Recovery partitions, one for each Win 10 installation.How do you know the Recovery Partition for Windows on the NVMe SSD is on the Sata disk ?which Windows created this Recovery partition ?As on the NVMe drive there is no EFI or Recovery partitions, they are on the SATA drive.True, you'll have a Recovery Environment for each Windows 10. So assuming I have 3rd or 4th Windows Installation for Triple boot/quad boot then is that true I would have to have a third/fourth recovery partition on the Sata Disk ?You will have to keep two Recovery partitions on the SATA drive, one for each win 10.Really ? Is this the only way to find out which Recovery partition used on the Sata Disk ?You have to boot from each Win 10 and find out witch Recovery partition it use on the SATA drive. (reagentc /info) Delete the other partitions.
From disk manager images I knew that both drives are UEFI-GPT
Dino, I didn't know, I supposed it had as:
- Sata drive had many Recovery partitions and NVMe didn't have one.
- Every clean install creates a Recovery partition. As there were no one on the NVMe, I supposed it was on the SATA drive.
- The Clean install on the NVMe was made with the SATA drive attached as the EFI partition on the SATA drive also has the Boot manager for the NVMe.
All this information made me believe that the NVMe Recovery partition was on the SATA drive. In fact, the NVMe installation has no recovery (as you can see on post #9).
I just said to be careful as one of the Recovery partitions could be from the NVMe installation.