I have been through almost a month of hell now with Asus support (which is the biggest embarrassing idea of a support help desk as there could be unless you need to know how to turn on a PC and the fact "they really look forward helping you with your issue"). I decided to reach out to the superuser community to see if my answers could be found here.
I have been having issues with getting 2 NVMe raided drives to show up as a boot drive in BIOS or to be recognized by the Windows installer no matter what raid drivers I use. I keep getting hung up on the fact that I can not see my array as a boot device. Now that I finally have managed to find out how to enable raid on the motherboard and specifically for NVMe, I have created a raid (1) mirror array successfully with two of my NVMe 1TB drives. Now in the BIOS I can see the 1TB raid array (OS) and the remaining 2TB NVMe drive (storage) along with my USB stick for OS installation (Windows 10) and USB stick for raid F6 drivers etc. I can see all this on the BIOS in EZ Mode (shown below) under "Storage Information".
Now when trying to install Windows 10, I get the "No signed device drivers were found." error message. But I suspect that the raid array might not even be available at the time of installing the OS due to me not being able to see it as a boot drive.
I have tried using raid drivers from many places. Asus has been just throwing all kinds of links at me and I have been searching the web for days trying anything I can to get this to work right. Below are a few of the drivers I tried...
When I try to enable either XMP I or XMP II the machine will do a reboot and take forever to boot up (attempts to restart the PC like 3 times). Then the BIOS panics and then boots into some type of "safe mode" for the BIOS. This disables XMP and allows me to change BIOS settings again. So I can't find a way to safely enable XMP either. Though the first issue is my main concern.
Some of these steps might not be necessary but just in case you are trying any possible solution to get it to work (like I was) I will try to detail all the things I did. To get RAID to be able to create an array and have windows see it I did the following...
1.Downloaded the correct ASUS RAID drivers from the ASUS website. I grabbed the Intel(R) Rapid Storage Technology Driver V19.0.0.1067 for Windows 10 64-bit drivers.2. Boot into BIOS.3. [F5] Load Optimized Defaults.4. On the EZ Mode screen [F7], Ensure X.M.P. is disabled. Intel Rapid Storage Technology should show off at this point too.5. When in BIOS go into advanced mode [F7] and go to the "Advanced" menu.6. Go into System Agent (SA) Configuration.
If you wish to enable, restrict or control certain administrative functionality in Windows, thereare multiple ways you can implement tweaks. But in the end, it all comes down to registry changes. Youcan make these manually, with a registry editor (regedit.exe) or you can make them using Group Policies. The latter is a set of administrative templates that allowsystem functionality to be shaped and then replicated across multiple nodes, simplifying management.Although changes still happen in the registry under the hood, Group Policies are exposed to users viaa friendly human-readable UI editor, and they are safer than manual registry work. The onlyproblem is, you don't get Group Policies in Windows Home.
Indeed, I've noticed a lot of people clamoring over the fact that Windows 10 Home does not have thismagical group policy editor, which comes with a handy name of gpedit.msc. This is nothing new. Going asfar back as Windows XP at the very least, Home editions of the Windows operating system did not havethe group policy editor, and people who wanted to make changes had to make registry tweaks. Which iswhere the utility namedPolicy Plus comes in. After me.
I shall. First, the attempt to include gpedit.msc into Home versions of Windows is not a new thing.It's been done for every single version of Windows, and always with rather bad results, I must say. Youwould get tweaks that show how to enable or run the Group Policy Editor in Windows Home, but it meanthacking system files and possibly invalidating the support/warranty, and worse yet, this rarely worked.Sometimes, you'd have a UI but the changes would not actually be implemented into registry. You'd onlyget a bogus visual effect. For that reason, I'm not going to talk about any method where you hack filesacross system folders.
Policy Plus does things differently. It presents a UI, in a manner, style and wording that is verysimilar to how gpedit.msc looks and behaves like, but it uses its own functions to access the registryand make necessary changes. Policy Plus is a standalone tool, it is compliant with Windows support, andit works in all versions and editions of Windows, namely 7 through 10, Home through Enterprise,although technically, you do not need this for Pro, Ultimate, Education, or Enterprise builds.
I download the tool and ran it (as admin). It is very consistent with gpedit.msc, but then, it alsodiffers slightly in how it behaves. By default, it will present a smaller subset of administrativetemplates than what you'd expect. But it also has the option to download these (wait, don't). We will get to that soon.
The tool has a lot of nifty features. Apart from the obvious usage, which is just like gpedit.msc,it lets you import and export policies and registry changes, so you can replicate those across multiplesystems. It also comes with a powerful search function, with detailed filtering.
However, please note that if you filter, say at least Windows 10, it will only show options thathave been added in Windows 10, but there are also options from previous versions of Windows that maystill be applicable. This means the presented set is more sort of an exclude rather than includelist.
I started by trying a few obvious, visible changes. Like camera access. For each selected policy,you have several options. You can implemented changes for the computer (all users) or for your user.Some policies are only available for one or the other, some for both. You get detailed explanations onwhat each policy does. Moreover, in some cases, you will note a non-intuitive Enabled option toblock/stop/disable certain functionality, and in others, the other way around. Some of the policies arekind of double-negative options, like do not allow whatever, which means you need to enable it toprevent something from running.
If you want to learn even more about the particular policy, you can right-click. There are severaloptions here, all extremely useful. You can check the Semantic Policy Fragment, i.e. how the system interprets the particularsettings (and then you can script this if you need to). You can also get policy details - again, usefulfor scripting. Finally, the Element Inspector will show you the detailed breakdown of registry paths,keys and values that are affected by the particular policy, so you know exactly what's happening behindthe scenes.
Policy Plus contains only a subset of available administrative templates. You can import more. Youcan manually download and installthese, or do it through the tool's menu. Now, this will effectively import all administrative templatesfrom around Windows 2000 onwards. This is good if you need to administer multiple systems runningdifferent editions of Windows, but it will create an unnecessary clutter otherwise. I tested this inWindows 10, and then had to sift through hundreds of policies that were only applicable to XP orWindows Vista or alike. There's really no reason to do this unless you truly need to. Just keepwhatever's available by default, as that's the smallest subset that will actually result in actual,meaningful functionality changes on your system. If you do use all these templates, search andfiltering can help.
Once you're done, you must save the changes via the file menu. Otherwise, policy changes won'tbe written and you won't see any difference in the system behavior. Let the tool write the changes andthen you can test what gives. BTW, should I remind you that having system backups and images is always useful before doing something like this?
Policy Plus works as advertised. The camera example from earlier is a good example. With the newpolicy in place with forced deny, the user no longer has the option to turn the camera on/off. I triedsome other random settings, and again, you get the expected results.
One thing that you need to remember - Policy Plus is NOT a replacement for buying the "higher"editions of Windows. For instance, on Windows 10 Home, there was no option to stop telemetry or WindowsUpdates. Certain features are just not there, and having a UI does not change that. Policy Plus canonly do what the system can do, with a nicer frontend and more safety than rummaging through theregistry. This is definitely not a short way of having enterprise functionality. It does not work thatway.
Policy Plus is an excellent administrative tool for advanced Windows users. It makes most sense forthose running Home editions of their operating system. There are some rather cool features inPolicy plus, like the ability to inspect each option in detail, powerful filtering, and the extratemplates. The usage isn't trivial though, and you need to be careful, but overall, it works reliablyand safely.
You should also be aware that Policy Plus does not replace missing functionality. It will not renderWindows Home into an omnipotent enterprise player. It's all about exposing the registry in a moreconvenient way and replicating the work across multiple machines - that's its true strength. Forordinary work, well this is an overkill. My testing with Windows 10 Home shows that you can implementmost of what you need through the settings plus some extra tweaks of various services. But whenyou need a little bit of extra admin rigor, this program can be quite useful. It's definitely a keeper.Take care.
I just purchases two five packs for the Riing Plus RGB Premium 12's and 14's. I loaded the software today and for the life of me I can't fix why it won't start in windows. I did the right click on the tray icon and blackened the run with windows starts up selection. The problem is it won't start with windows but will start if I click the icon. I tried moving the icon to the startup folder and no luck their either.
c80f0f1006