INACCESSIBLE BOOT DEVICE after RAID Software Installation

Got it.

I booted from "Windows 10 Pro English (US) 22H2.iso" image and attempted to install W10.
Interestingly, the Windows 10 setup recognized the virtual drives 0 and 1, along with all their partitions.
However if I select any of the existing partitions I get the following results:


Is this a key to what has happened and how to recover without OS re-installation?

Thank you.

I wouldn't do that! Never!
Try to get an additional Disk and connect it to a SATA-Port. Install your WINDOWS there with the right ISO. (UEFI) From there you should be able to mount the rest and do Repairs

Pentagon said:

I wouldn't do that! Never!
Try to get an additional Disk and connect it to a SATA-Port. Install your WINDOWS there with the right ISO. (UEFI) From there you should be able to mount the rest and do Repairs

Done!

I installed a recovery Windows 10 to a separate drive and booted it.
Now I can see all the virtual drives and their partitions.
Shall I proceed with the registry?

Pentagon said:

A screenshot of "Diskmanagement" is needed!

Rightclick on <Start> and select "Diskmanagement" In the upper part expand the column 1+5 so that it is readable!

Here it is:


Disk 0 is Virtual Drive 0.
Disk 1 is Virtual Drive 1.

Shall I proceed with the registry?

Try these 2 command first:
cmd (admin) C:\Windows\System32>
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD

reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

Pentagon said:

Try these 2 command first:
cmd (admin) C:\Windows\System32>

bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {a0a94caa-356a-11ee-9e95-aeb6ae704582}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {a0a94cac-356a-11ee-9e95-aeb6ae704582}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {a0a94caa-356a-11ee-9e95-aeb6ae704582}
nx OptIn
bootmenupolicy Standard

reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
FirmwareBootDevice REG_SZ multi(0)disk(0)rdisk(0)partition(1)

What shall I do next?

What is your problem?
Disk 0 is not a virtual drive
You booted successfully from disk 0

run cmd
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all >C:\bcd_output.txt

and you get a small txt-file on (C:) bcd_output.txt Upload that file so that I can make a deeper analysis

Pentagon said:

What is your problem?
Disk 0 is not a virtual drive
You booted successfully from disk 0

run cmd
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all >C:\bcd_output.txt

and you get a small txt-file on (C:) bcd_output.txt Upload that file so that I can make a deeper analysis

I booted successfully as you suggested from a clean W10 installation to a separate external drive.
Please see the attached BCD_Output.txt:
BCD_Output_2024-04-29.txt