Windows 10: Configure 2 Disks, Nvme and Sata3 in Windows 10

Hi and sorry for my English...
I have a PC with a solid NVME disk in PCI-e mode connected to its M2 port. I have installed Windows 10 Pro and I have configured the bios so that the 1st boot option is the windows boot manager that is on that NVME disk.

Every time the PC started it was very fast to enter Windows and the disk manager appeared as disk 0.

Up to here everything worked perfectly !!!

The problem starts when I connect the second HD Sata3 disk that I want it for data.
Now when I start the PC it takes a lot to start Windows 10 (which is in the NVME) and when I go to the disk manager to initialize the HD Sata and format the solid disk NVME that was disk 0 when I was alone, now it appears now as a disk 1 and the new HD Sata that I am going to format appears as disk 0.
When connecting this HD Sata in the PC the numbering of the discs has been changed when the logical thing is that if the NVME was disk 0 it would follow in 0 and when adding the Hd Sata it would appear as disk 1.

And the other problem is that now the boot is much much slower.
In my opinion it is as if I were looking for the boot on disk 0 which is now the Sata and when it is not found out to disk 1 which is now the NVME although in Bios I have as the 1st boot option the NVME where the Windows is boot manager
The boot should be on disk 0 but the problem is that when I only connect the solid disk NVME in PCI-e mode it recognizes it as disk 0 but when I connect the 2 disks (NVME mode PCI-E and HD Sata3) it changes the order of the discs and the disc 0 that was the Nvme happens to disk 1 and the HD Sata3 that I have not yet formatted goes to disc 0 and it generates slowness to me when starting.

The board is an Asus Maximus XI Hero (wifi).
Sata's PCH Storage Configuration is in AHCI
Solid NVME disk is in PCI-E mode on M2 port _1

I hope you can help me because I've tried everything.

:)

 

Windows 10 installer don't detect NVMe drive

I have 2 drives:

• disk1 (SATA SSD, with Ubuntu 16.04)
  • partition1 (sda1: flag /boot)
  • partition2 (sda2: flag /home, encrypted by LUKS)
• disk2 (NVMe SSD)

So, the goal is to install Windows 10 on disk2 and boot it from GRUB (which is on sda1).

What is the problem ?

In disk-choose step, disk2 is missing. However Ubuntu 14.04 installer "see" this disk, so I assume that is software issue, rather than my hardware.

What I tried to solve this problem ?

• loaded Samsung NVMe drivers from this thread
• patched Windows image using DISM tool by adding 2 updates. I followed this guide
• tried to run Windows 10 installed on USB stick to install it

All of them failed.

Please help me to solve this issue.

 

Windows 10 installer don't detect NVMe drive

Thanks. This helped but only partly.

NVMe disk is now listed in choose-disk step but installer says that its unable to install WIndows on this disk because it has MBR partition. Windows can only be installed on GPT disks in EFI systems.

What should i do now ?

 

Use bootloader from a SATA disk to boot Windows installation on a NVME disk

I want to move my Windows 10 installation to a new NVME disk (disk 2). I have cloned the original SATA disk (disk 1) to the NVME disk. Unfortunately I have an older motherboard (ASRock H77 Pro4/MVP) that does not support booting the NVME drive directly.

Both disks are using a MBR, have a 'system reserved' partition and a partition holding the OS. If I understand correctly, the system reserved partition contains the Windows bootloader. Windows seems to be handling the NVME drive just fine. Is it possible use
the bootloader and the 'system reserved' partition from disk 1 and have it start the OS from disk 2?





I have tried adding the OS on disk 2 as an alternative boot entry using EasyBCD. This restulted in the following BCD configuration:

Code:

Windows Boot Manager

--------------------

identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}

device                  partition=\Device\HarddiskVolume3

description             Windows Boot Manager

locale                  nl-NL

inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

default                 {868eec41-5821-11e8-a835-e2488662881a}

resumeobject            {868eec40-5821-11e8-a835-e2488662881a}

displayorder            {868eec41-5821-11e8-a835-e2488662881a}

                        {44fda4da-5819-11e8-a499-c54e35723be3}

toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}

timeout                 30

Windows Boot Loader

-------------------

identifier              {868eec41-5821-11e8-a835-e2488662881a}

device                  partition=C:

path                    \WINDOWS\system32\winload.exe

description             Windows 10

locale                  nl-NL

inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

recoverysequence        {44fda4d8-5819-11e8-a499-c54e35723be3}

displaymessageoverride  StartupRepair

recoveryenabled         Yes

allowedinmemorysettings 0x15000075

osdevice                partition=C:

systemroot              \WINDOWS

resumeobject            {868eec40-5821-11e8-a835-e2488662881a}

nx                      OptIn

bootmenupolicy          Standard

hypervisorlaunchtype    Auto

Windows Boot Loader

-------------------

identifier              {44fda4da-5819-11e8-a499-c54e35723be3}

device                  partition=I:

path                    \Windows\system32\winload.exe

description             Windows NVME

locale                  nl-NL

osdevice                partition=I:

systemroot              \Windows

This does not seem to work. When booting the second option, the systems complaints about '\Windows\system32\winload.exe'.

Any ideas on how to get this working? Should the Windows bootloader be able to access the NVME drive? Is there something wrong with the BCD configuration? Can this be achieved using an alternative bootloader?