Windows 10: Problem with disk marked Disk0 instead of Disk1

I installed a second disk in my Lenovo laptop and got big troubles when Windows Update installed files today. Windows 10 is on C: Disk1 boot and the second disk D: is on Disk0, I've learned today that you can't switch the disk numbers, it's the moderboard who sets the numbering. After several hours I concluded that the blue screen I've got depends on that the second disk is Disk0. The blue screen never disappeared because it didn't collect any error information, it said 0% completed for one and a half hours before I did a hard shut down. After that I tried everything, I tried to uninstall th

:)

 

Problem with disk marked Disk0 instead of Disk1

I installed a second disk in my Lenovo laptop and got big troubles when Windows Update installed files today. Windows 10 is on C: Disk1 (boot) and the second disk D: is on Disk0, I've learned today that you can't switch the disk numbers, it's the moderboard who sets the numbering. After several hours I concluded that the blue screen I've got depends on that the second disk is Disk0. The blue screen never disappeared because it didn't collect any error information, it said 0% completed for one and a half hours before I did a hard shut down. After that I tried everything, I tried to uninstall the update (KB5026361) which didn't work, also tried to restore yesterdays Restore Point which gave me an error message "...failed to replace the file (D:\Users..." error code 0x80070780. I don't have any Users catalogue on D, it is on C. I opened my laptop and took out the second disk, then I installed all Windows Updates without problems and created a new Restore Point. Now the second disk is back into the computer as Disk0. Is there anything I can do to avoid these problems when the next Windows Update is here?

 

Can I switch disk1 to being disk0, and disk0 to being disk1?

I have 1x Intel SSD 660p series (Model number: INTEL SSDPEKNW512G8), and 2x WD HDD (Model number: WDC WD10EZEX-00BBHA0) housed in my desktop PC.

The OS (Windows 11 22H2, OS build 22621.675) is installed in the Intel SSD 660p series, which is NVMe protocol.

The two WD HDD are SATA drives.

The system shows the two SATA HDD as Disk0 and Disk1 and the Intel SSD with OS as Disk3, even though the OS resides on it!

The Intel SSD with OS is shown as Disk0 only when I disconnect the two SATA HDD from the system and reverts to Disk3 as soon as the two SATA Disks are connected back.

The question is - Why can the system not identify the NVMe SSD as Disk0 all the time regardless of the SATA HDD installed?

I prefer to have the disk with OS always identified as Disk0, irrespective of whether it is of NVMe or SATA protocol.

Is there some way, a registry tweak or similar, by which the NVMe SSD with the OS is always identified as Disk0?

Thank you.

 

OS is on disk1, System Reserved is on disk0. Cannot allocate the rest of disk0

Windows 10 was installed on a 1 TB SSD (disk1) and used all the space on that drive. The System Reserved space was placed on a 4 TB HDD and 2 TB of space was allocated to a 2nd volume. The problem is that there is another 2 TB of unallocated space on Disk0!
I been reading online and both disks are formatted with MBR. As I understand it there is a limit with a disk formated in MBR and that limit is 2TB. My question is

How do I allocate that unused space on disk0?

The normal right-click menu items are grayed out that would allow me make a simple, spanned, or spliced volume. My system will not boot if I disable disk0 (unplug), the one with the System Reserved space. I have since read that I should have installed Windows
10 with my 2nd drive disabled, but ... water under the bridge now. I have tried to 'Repair Installation' by booting the original Windows 10 DVD but it doesn't do anything. I made a system repair disk and tried the same with the same results. I tried booting
into windows, inserting the windows DVD then unplugging disk0 to try to 'reinstall' windows 10 on disk1 (C but got error message saying that windows could not determine if I could upgrade or not. I guess that would because the System Reserved area contains
the boot configuration etc. Here is a picture of my Disk Manager.

Does anyone have any idea of how I can allocate that unallocated area to a new volume or expand E: to span the unallocated space. The menu item to expand the volume on drive E: is also grayed out ( I assume due to the 2TB limitation on MBR formatted drives.
)