Hi,
I've just got this board and have tried to set up a bootable RAID 10 volume on 4 SATA SSDs. First time posting on the forum in about 10 years, its all new!
I've followed the steps described above, and get the same behaviour - windows installation detects the array/volume created in RaidXpert after I load the drivers previously copied to the windows installation USB, it installs fine, seemingly installs a bootloader somewhere (no other USB drives/partitions/volumes are present) at the end, and restarts.
Remove the USB stick, windows should attempt to boot, nada. Straight to UEFI. An entry for "[UEFI] AMD-RAID - Windows Boot Manager" shows in the boot device list, but attempting to load it just flickers the screen. Based on my limited knowledge obtained only in the last 24 hours, this seems like the EFI shell launch string pointing to the boot record isn't correct, but I've not enough knowledge on why that might be/how to fix it. Trying random things, Interesting thing I noticed is when I destroy an array while there is a Windows Boot Manager entry to load for it, then attempt to boot that entry, the same behaviour is shown, a small screen flicker... Perhaps nothing but if UEFI is storing an "efi launch string" record somewhere on the motherboard, perhaps that is what we need to play with. Moving on...
I tried testing this method also with a 2 drive RAID 0 setup, imitating your setup, and got the same behaviour.
HOWEVER, I then tried a 2 drive RAID 1 setup, and it was successful. Windows installs (and feels a little quicker doing so, might be subconscious), drive activity can be seen as constant - indicating the array is initializing in the background. Restart, remove USB, it boots fine. Install RaidXpert software and see the array is (by this time) ready, and disk activity has also ceased. Behaving as expected.
This is using beta bios 0007, which was a troubleshooting step I tried after I was getting nowhere with bios 0801.
Interestingly, I then decided to "transform" the RAID 1 array using the web UI into RAID 10, expanding the volume in the process. Clicked it, waited, and it worked... until I rebooted. back to UEFI.
I thought that might happen, so whilst I was still in windows I ran a couple of tests/benchmarks to see if performance was as expected, and it all seemed fine. Disk management showed a single disk with the capacity now doubled, half unallocated.
Can you try these things, and see if you get the same issues/notice anything else?
Anyone else have issues running RAID 0 or RAID 10 on SATA SSDs?