If you should mean the 32/64bit "test variants", which I had attached to post #152, you can find similar variants of the nForce SATARAID drivers v9.99.09 attached to this post. You may try it and report about the results you got.
Yes, I have already seen it before. As long as the user hasn’t enabled the "Secure Booting" within the BIOS, the installation of my mod+signed drivers should not be a problem. Even the integration of any of my mod+signed drivers into any Win10 v1607 image seems to be possible. I have tested it and the integration itself worked flawlessly. What I do not yet know is, whether the inserted driver will be still used after the first reboot during the OS installation.
Hello, everyone. I just want to share my experiences on Windows 10 1607 clean installation with nForce RAID Arrays (Success!).
My System. Nvidia nForce 630a with RAID 0 (2 SATA HDD.). Modified Nvidia nForce sataraid driver version 11.1.0.43 (nvstor.sys on Microsoft driver version 10.6.0.23 often freeze system during boot on old my Windows 10 1511). Windows 10 Enterprise 2016 LTSB.
Preparing Step. Modify Windows 10 Enterprise 2016 LTSB image with NTLite both install.wim and boot.wim (only Windows … Setup, except Windows PE…).
Remove nvraid.inf driver (important! if don’t remove this driver I can’t boot).
Add modified nforce sataraid driver version 11.1.0.43, maybe can use Fernando’s modified driver (post #146), my modified nforce driver only add 2 these lines
I copy (or create) these key's value from HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx and paste to HKEY_LOCAL_MACHINE\TEMP\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx
1 2 3 4 5
ClassGUID DeviceDesc Driver Mfg Service
Repeat to yyyyyyyyyy key too, Unload Hive and then reboot.
After reboot, recheck driver under "Storage controllers" should have "NVIDIA nForce RAID Device" no "Generic SCSI Array Device" if not, manual update driver to nforce modified 11.1.0.43 (Choose Browse on my computer => Let me pick from a list... because it's not digitally signed).
My PC can boot and successfully Windows 10 1607 installed on nForce RAID Arrays.
Thank you very much @Fernando and @ENAJonas for yours guides.
Sorry for my poor English language, I'm from Thailand :D.
@aokake : Welcome at Win-RAID Forum, congratulations for your success and thanks for your report about how you succeeded to get Win10 v1607 clean installed onto your nForce RAID array. This procedure will help other nForce RAID users to get the "Anniversary Update" of Win10 properly installed.
Add modified nforce sataraid driver version 11.1.0.43, maybe can use Fernando’s modified driver (post #146), my modified nforce driver only add these 2 lines
Although I can read and understand your contribution, I will not reply to it unless you have translated it to English. This is an English language Forum and all visitors from all countries should understand all the questions and the answers. I am hoping for your understanding.
Regards Dieter (alias Fernando)
By the way: I am a registered member of DRWINDOWS Forum since many years as well.
@edv.kleini : Thanks for your reply in English language.
By the way: I just have posted there a reply to your post in German language.
According to my knowledge the NVIDIA nForce RAID array will not be detected, if you just load any of my especially "mod+signed" SATARAID drivers, which are attached to the posts #146 resp. #154. I suspect, that the Win10 in-box nForce RAID driver has to be previously removed from the BOOT.WIM and INSTALL.WIM of the Win10 image.
Yes, NVIDIA would have been able to deliver a corrected NVRAID.INF file to Microsoft, which matches the new Win10 hardware detection routine, but they didn’t and probably are not willing to do it. It seems to be easier for them to announce, that all nForce RAID arrays are "LEGACY" and not supported anymore by the latest Builds of Win10.
Although I have given at least 6 nForce RAID users a link to a differently customized Win10 x64 v1607 ISO file, I didn’t yet get much feedback.
Nevertheless I have meanwhile created and uploaded another Win10 v1607 Pro x64 EN-US ISO file, where I had a) removed the in-box nForce RAID driver and b) inserted the “new 64bit nForce SATARAID driver v11.1.0.43 mod+signed by me” (identical with the one I had attached to post #146).
Interested testers should send me a PM and I will give them the download link.
Sorry, I don’t understand your question but I’ll show my summarize installation below:
Boot with modified Windows 10 USB boot disk.
Now, I can installing Windows normally because Windows Setup detected RAID Arrays disk that come from modified driver in USB boot disk.
Windows Setup can copy any Windows setup files to RAID Arrays disk then it will reboot my PC.
Before PC boot up I change boot order to boot from RAID Arrays disk first in BIOS, now Windows Setup continue installing from RAID Arrays disk (Getting devices ready …% screen).
After Windows Setup running 100% it will reboot PC again. (Now Windows on RAID Arrays disk use scsidev.inf driver that not work, therefore I fix this on step 4.)
Before PC boot up I change boot order to boot from Windows USB boot disk first for modify driver on RAID Arrays disk to use modified sataraid driver v.11.1.0.43 by compare keys and values from two systems registry.
System 1 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx (this registry on Windows Setup RAM disk from USB boot disk).
System 2 (load hive from ?:/Windows/System32/config/SYSTEM by set TEMP key name) HKEY_LOCAL_MACHINE\TEMP\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx (this registry on RAID Arrays disk).
After modified System 2 registry and unload hive, I can reboot PC to boot Windows on RAID Arrays disk.
Step 1., 2. and 4. processing on Windows USB boot disk. Step 3. processing on RAID Arrays disk
Sorry for my poor English language but I hope you understand me.
Regards, AokAke
EDIT by Fernando: List code optimized (for better readability) and unneeded parts of the quoted text removed (to save space)
To clarify, you are saying that your Windows boot installation is on your RAID 0 array, then? Thanks for these details!
Sorry, I don’t understand your question but I’ll show my summarize installation below…Hey @aokake , sorry, I wasn’t clear… This regards the distinction between systems where Windows is installed on the RAID array, versus on a non-RAID drive separate from the RAID array. The latter is easy to workaround after the upgrade, while the former is where these ISO’s and other methods are being tried. It sounds like your setup is the former, like mine; so I wanted to clarify that point, since you indicated success in fixing the issue.
@Fernando , I have read that Windows determines the driver to install/retain partly based on its DriverVer field; is that true? As in, if the existing driver is older -OR- a lower version, then it will use the new MS driver…? E.g., then the v9.99 driver fails both of those checks, while the v11.1 fails one. If so, perhaps it would be sufficient to just change the date and version of the .inf’s without the need to modify the ISO? Such as (for v9.99): DriverVer=01/17/2008,9.99.0.9 to DriverVer=09/09/2016,10.9.0.9 or similar. [based on the MS driver being v10.6]
@jwhickman : It is true, that Microsoft’s Operating Systems prefer drivers with a higher version number and a newer date, but in this case I do not see any danger for nForce RAID users, that Microsoft will automaticly install a newer nForce RAID driver. Simple reason: Microsoft does not develop and deliver NVIDIA nForce RAID dtivers and NVIDIA has stopped the development of the nForce chipset drivers already in 2009/2010. Consequence: A manipulation of the driver version or date is possible by modifying the INF file, but doesn’t make sense. Furthermore any manipulation of the driver’s version number or date would be absolutely misleading for the users. By the way: If a user has installed an older driver or a driver with a lower version number than the in-box one, he may have to force the installation by using the “Have Disk” option, but the OS will never change the in-use driver.
I can confirm that the latest customized Win10 x64 v1607 ISO from @Fernando allow the install of Windows 10 Pro to progress past the drive selection screen. My Raid Array (Raid 0) on my Nforce 650 Sli can be seen and the install completes successfully. However, after the first boot i get the message "Boot Device Inaccessible" message. So I completed the following step 4 as per aokake’s guide -
Once this is done I can load windows 10 successfully. What I noticed on First boot was that the system had defaulted back to the generic scsi.inf file and associated drivers.
Thanks to Fernando for you good work and to others that have also contributed to getting this far.
Thanks, Steve.
EDIT by Fernando: Quoted text and its list code optimized (for better readability)
@ENAJonas : @aokake : @SteveyB : @edv.kleini : On behalf of all nForce RAID users I want to thank you for your great efforts spending a lot of hours to test, whether and how it is possible to get Win10 v1607 clean installed onto your bootable nForce RAID array, and to report about how you did it. The fact, that you succeeded at least, verifies, that it is possible to solve the problem even for nForce users, whose system drive is inside the RAID array.
@all nForce RAID users: Thanks to the tests done by the above mentioned Forum members we now know, that a) the problem regarding the topic of this thread is solvable, b) the Win10 v1607 in-box nForce RAID driver v10.6.0.23 is unusable and c) the Win10 v1607 Setup will accept and use nForce RAID drivers, whose INF file has been correctly customized and digitally signed (pre-condition: the in-box Force RAID driver had been removed from the OS image).
Despite the now available success reports and the related guides about how to do it, we are obviously not at the end of the rooad: There must be a way to get Win10 v1607 clean installed onto an nForce RAID array without getting the “UNACCASSIBLE BOOT DEVICE” message while rebooting and the need to repair the registry during the OS installation.
The most interesting questions for me are the following:
Which Win10 v1607 in-box “driver” resp. INF file is responsable for the trouble, which requires the reparation of the registry at the end of the OS installation? Note: According to my knowledge it cannot be the file named “SCSIDEV.INF” v10.14393.0, because it doesn’t support anymore the “Generic SCSI Array Device” (as you can see >here<).
What happens, if the initiator of the “UNACCESSABLE BOOT DEVICE” bug will be removed from the Win10 image as well (no matter whether it is an INF file or a real driver)?
Please let us know, if you know the answers.
Some remarks about the tool NTLite:
The removal and insertion of specific drivers from/to the Win10 v1607 image by using the tool NTLite can be done according >this< guide.
Since the officially released free version of NTLite doesn’t offer all required options regarding the removal of certain Win10 in-box storage drivers, you may need a special NTLite version, where these options are enabled. Our Forum member nuhi, who is the author of the NTLite tool, has already created such special NTLite version with advanced options for Forum members, who are willing to do some tests regarding the topic of this thread. Big thanks to nuhi for having done that!
Interested testers may send me a PM and I will give them the link to that special NTLite version.
Are you loading the SYSTEM hive after you boot from USB (as TEMP) copying all the relevant values from USB boot registry and then unmount the SYSTEM (TEMP) hive?
This is what I did and the settings remain every time I Boot from RAID disks.
For sure I did that, but only regarding the WIN.INSTALL index of the Win10 Professional.
If you want to integrate any storage driver into any Win7/8/10 Image, you have to do the same procedure with the BOOT.WIM and the INSTALL.WIM. Otherwise the inserted driver will be not available during the second part of the OS installation, when it comes to the detailed Hardware Detection and the final storage and PnP driver installation.
I have an Nvidia Nforce G8300 Chip on an Asus M4N78 Pro mainboard and my System Disk is NOT on the Disk RAID. I encountered the RAID Problem with Nvidia driver version 10.6.0.23 for my data disk after installing KB3176493. First I deactivated this patch, but after applying the new Update KB3185614 the problem reappeared (see #213). So I tried to follow the suggestions of #146 to get a permanent solution with the following result:
- Importing Certificate OK - Updating Drivers for Generic SCSI Array Device OK After Update and Reboot two Nvidia RAID Devices are shown with correct driver version 11.1.0.43 - Updating ATA Controller and RAID Controller claims, that the driver is allready the most recent version But this is an ERROR, the Driver version remains 10.6.0.23.
I even deinstalled the RAID Controller, but after updating the HW, again the old driver version 10.6.0.23 appeared. The RAID Disks are not visible and I guess that somehow the two active different driver versions are not copmpatible. My system still uses the old drivers for ATA and RAID Controller and does not allow an update.
@NetAktiv : Hello Rainer, welcome at Win-RAID Forum!
You should not believe such messages given by the OS Device Management. Note: If you want to replace a WHQL certified or OS in-box driver by any other not WHQL certified driver (no matter which version or date it has), you have to force the installation by using the "Let me pick…" > "Have Disk" option. The option "Browse for drivers on your Computer" is only usable, if you are going to install a WHQL certified driver, which is newer than the currently running driver.
This regards the distinction between systems where Windows is installed on the RAID array, versus on a non-RAID drive separate from the RAID array. The latter is easy to workaround after the upgrade, while the former is where these ISO’s and other methods are being tried. It sounds like your setup is the former, like mine; so I wanted to clarify that point, since you indicated success in fixing the issue.