Asus H97M-PLUS Main/Motherboard.
Intel i5 4690 (Haswell) CPU.
Intel HD Graphics 4600
Intel H97 chipset.
16GB DDR3 667Mhz system RAM.
5 X Seagate 250GB SATA III 7200 RPM RAID 0 Array.
Hello, I am currently running windows 11 on this “fine specimen”.
Although I found a way around no disk found error code on windows 11 setup by integrating the latest driver I have found another problem.
Using the built in RAID support I see a list of drives and the option to enter the Intel RAID setup menu that shows before the post screen. Unfortunately when I recently updated the installed windows 11 system with “windows CA 2023” signed bootloaders no more RAID status or setup screen ability!
Although I can still use the configured RAID I no longer can enter RAID setup or see its status on boot!
I can’t find any tools to manually update the latest BIOS ROM so I am stuck with how the heck to reconfigure the RAID now!
I have the latest official BIOS ROM in the system. Available here.
Any help would be appreciated.
Thankyou.
Edit by Fernando: Thread moved into the “BIOS Problems” Category and title specified
@zapbuzz
What lets you think, that you can solve your problem by a BIOS modification?
Please keep in mind, that modern Windows Operating Systems do not 100% support old Intel RAID0 Arrays.
If you want a good performing and stable running Win11, I recommend to install it onto an NVMe SSD. Additional question:
Which “latest” Intel RAID driver version did you integrate into the Win11 Images?
By the way - the latest ASUS BIOS for your mainboard contains the EFI RaidDriver module v13.0.0.2075.
I don’t have the money for NVMe and I also don’t like their lifespan. Windows 10 supports this RAID controller out of the box no problems. My idea of a mod would be an updated controller BIOS option ROM version to overcome the bug. I attach an image of the latest driver for this controller. If I had the tools I would do it myself
@zapbuzz
It is not the age, but the RST development platform (e.g. v13/14/15/16) of the on-board Intel RAID BIOS module and the in-use Intel RAID driver, which matters.
The BIOS of your mainboard contains an Intel RAID EFI module, which belongs to the Intel RST v13 platform (v13.0.0.2075). Windows 11 has natively an Intel RST RAID driver in-the-box, which belongs to the v15 platform (v15.44.0.1015) and you have obviously integrated an Intel RST RAID driver v16.8.5.1014.
Probably because your secure boot keys have older keys (if you used asus stock secure boot keys). I could be wrong tho, i think if your windows bootloader changed into 2023 while your secure boot keys have no 2023 certificate (KEK 2023, Windows and Microsoft UEFI CA 2023, Microsoft Option Rom UEFI CA 2023), it might wont load the raid driver inside your bios.
your not very helpful. I will not bother to explain to you the cans and cannot with RAID you simply should know better. Perhaps if you used this equipment like I do on a daily basis.
After about 5 reboots after disabling secure boot the RAID display and settings started to re appear. I successfully reconfigured for RAID windows boot and discovered the CA 2023 keys are retained to reinforce in secure boot mode when re enabled (RAID menu disappears again). Still, there’s a bug to fix and ASUS ghosted me in support because its out of warranty.
Yes, secure boot on: Raid setup disappears, and secure boot disabled: raid setup appears.
The motherboard BIOS offers either Windows secure boot or “other OS” Selecting other enables RAID status and setup at boot. If I clear the keys in the updated secure boot database and apply the motherboard ones OS no longer boots and RAID status and setup will still not work until I select “other” OS. I had to reinstall windows with the soon expiring certificates on “windows OS” secure boot mode then re apply the new certificate keys in windows to re establish updated secure boot. So in the BIOS there is problem an additional certificate from Microsoft is planted and has changed how my system behaves about secure boot and non secure boot. I am searching for a universal BIOS flash tool to force the official BIOS file into the motherboard BIOS which is refusing the correct file and revision due to the Microsoft change which is not reflected on motherboard BIOS but it appears the real problem is something to do with UEFI and certificates preventing RAID from displaying in secure boot but it still works and I do not know if it will continue to work in 2027 I will have to change the date and time on the machine and boot.
If you cant extract the updated secure boot keys in the bios, or you could extract but not append the updated keys, you can use the script i’ve made to extract and apply the updated secure boot keys if you ever need to reset your bios. Secure Boot 2023 Update.zip (188.7 KB)
How to use:
Install current secure boot keys
make sure you use the latest 25h2 (idk why it cant be done on version less than 25h2 in my testing)
run each .reg and Apply Registry Secure Boot Updates.cmd, after that reboot, and do the rest of .reg (you could only do the .reg once, so in total you would do 4 times)
Check if all secure boot keys is all updated to latest 2023, if all updated, use Extract Keys.cmd to pull the secureboot keys
If you ever reset the bios, you would only need to do secure boot enabled in bios and set it at custom/user but do not install keys, boot to windows and use apply keys.cmd instead.
Maybe with all updated keys (KEK, DB, and DBX to the latest), it might be able to install and boot with Raid.