Macrium Reflect - Fix Boot Problems not working

A bit complicated, but here goes:

HP Z4 G4, originally delivered with Windows 10, upgraded to Windows 11, etc etc. No issues. System drive was HP 256GB SSD M.2 NvMe mounted in motherboard slot.

Used Macrium Reflect to clone this SSD to a pair of Samsung 960 1Tb SSD drives running in RAID1 off of Adaptec hardware card. Resultant array is bootable immediately, so removed old 256GB drive.

Discovered that I can run bootable RAID array off of Intel VROC software using pair of motherboard slots. Installed a pair of Samsung 970 M.2 NvMe drives there, no issues.
My idea now is just to clone the currently running Windows 11 system to the new M.2 RAID array - which I was able to do with Reflect. I did this, but the resultant cloned drive array will not boot.

Created Rescue Disk with Reflect, booted to it with Windows PE environment. Tried to use Fix Boot Problems to render M.2 array bootable. Reflect sees the Windows 11 install on the M.2 array, reports fixing boot problems, asks for restart. But the new M.2 array will not boot.

So, stalled at this point. It occurred to me that I could use the Windows PE environment to ask Reflect to use a drive IMAGE to restore to the M.2 array, but am not sure this would be worth the effort. It is apparent that closing a single SSD to a RAID1 array is not problematic, but perhaps trying to clone a Windows 11 OS from an existing RAID array to a different RAID array might just not be feasible.

Any boot error message will be helpful.

Well, just the "inaccessible boot device" on the blue screen. But, after a lot more head-scratching and a brief call to HP, I found the issue, as crazy as it might seem. There is NOTHING wrong withe Macrium cloned drive array. There is inside the HP BIOS controls, a selection for UEFI boot device order. Last in the list was the RAID array - BUT - is was shown as (Disabled) - the default, I guess. Changing the RAID to first in the boot order - AND - toggling it's state to not being "Disabled" did the trick. It sure is puzzling to me that the various settings for setting up and managing the RAID nowhere suggest that once it is created and working, and its status inside the Intel RST UI in Windows 11 is shown as "Bootable," that you have to go into the BIOS UEFI boot menu to enable you to boot to it. Crazy stuff!

In this video guide, i'm going to talk about the Windows stop code - Inaccessible Boot Device error and the solutions for it.