I just tried disabling digital signature enforcement, and updated the nvrd64.inf from the 64bit 11.1.0.43 driver pack from post #119 with the following:
%NVRAID_DESC%=nvraid,SCSI_NVIDIA____Raid_Disk_20
and this has enabled me to install the moded 11.1.0.43 driver on my MVIDIA nForce RAID Device.
if you could add that to the nvrd64.inf file and re-sign the pack, it should enable me to use the 11.1.0.43 moded signed driver
The list of nvraid entries in my current unsigned version is:
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20____
%NVRAID_DESC%=nvraid,SCSI__NVIDIA____Raid_Disk_20
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI_NVIDIA____Raid_Disk_20
Thanks for your report.
Since I had already prepared freshly modded and signed 32/64bit NVIDIA nForce SATARAID drivers v11.1.0.43, I will attach them.
Here is the related part of the nvraid32.inf resp. nvraid64.inf:
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20____
%NVRAID_DESC%=nvraid,SCSI__NVIDIA____Raid_Disk_20
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,_NVIDIA_______Raid_Disk
This variant of the last (bold style) line may be even better usable than yours, because it is part of the HardwareIDs, which were shown by the "Generic SCSI Array Devices".
Please test this freshly mod+signed driver and give us a feedback regarding the result.
Good luck!
EDIT: The originally attached driver packages have been removed from here, because they obviously didn’t work. Better working drivers are now attached to post #146, where the new guide about how to get these drivers installed is located.
Tried the new one, but it still fails to install for the NVIDIA nForce RAID Device with the message that the folder doesn’t contain a compatible driver for my device.
The extra line you added has too many underscores to match the HardwareID on my device
All the values for mine are:
SCSI\Array__NVIDIA____Raid_Disk_20____
SCSI\Array__NVIDIA____Raid_Disk_20
SCSI\Array__NVIDIA
SCSI_NVIDIA____Raid_Disk_20
_NVIDIA____Raid_Disk_20
ScsiArray
2 underscores before NVIDIA and 4 underscores after.
The line you’ve added has 7 underscores after NVIDIA.
@tandeejay :
Thanks for your report.
Meanwhile I have removed the packages, which I had attached to my last post, and replaced them by freshly modded and signed ones.
Here is the related part of the nvrd32.inf resp. nvrd64.inf:
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20___
%NVRAID_DESC%=nvraid,SCSI__NVIDIA____Raid_Disk_20
%NVRAID_DESC%=nvraid,_NVIDIA____Raid_Disk_20
Please test it and report.
Good luck!
I have tested the updated package, and it works!
Excellent work!
Thanks for having tested the freshly customized and signed drivers!
This is good news and hopefully may solve all the current problems of the affected nForce RAID users.
This is my analysis:
There are obviously 2 different sorts of "NVIDIA(R) nForce RAID Devices" (Raid_Disk and Raid_Disk_20). Until now I have focussed my modding on systems with the "Raid_Disk" model and obviously forgot the systems with the "RAID_Disk_20" model. That would explain why my previously mod+signed nForce SATARAID drivers worked for some systems and for others not.
Next steps:
At first the new mod+signed drivers have to be tested by other nForce RAID users, whose RAID array is outside their system drive, but not accessable after the last Windows Update.
This is what they should do:
- Download and unzip the "new 32bit resp. 64bit SATARAID driverpack v11.1.0.43 mod+signed by Fernando", which are attached to this post (they are identical with those, which were attached to post #140).
- Import the Win-RAID CA Certificate by doing a right-click onto the file named Import Win-RAID CA.cmd, which is within the driverpack, run it as Admin and enter "Y" (for "Yes!).
- Create a System Restore Point.
- Run the Device Manager, choose the "View" option "Show hidden devices" and manually update - one after the other and without rebooting in between - the driver of the following devices, which are listed within the "Storage Controllers" section:
a) all devices named "NVIDIA(R) nForce Serial ATA Controller" (maybe there are more than 1 listed),
b) the device named "NVIDIA(R) nForce RAID Controller" and
c) all devices named "NVIDIA(R) nForce RAID Device" (there will be more than 1 listed). If there are no devices with such or similar name listed although you had checked the "Show hidden devices", expand the "System Devices" section of the Device Manager, search for devices named "Generic SCSI Array Device" and update the driver of all of these devices - one after the other.
This is the exact driver update procedure:- Right-click onto the device and then choose the options "Update Driver Software…" > "Browse my Computer…" > "Let me pick…". Then hit the "Have Disk" button, navigate to the stored unzipped driverpack and choose the matching INF file (nvraid32.inf for Win10 x86 resp. nvraid64.inf for Win10 x64).
- Don’t reboot when prompted to do it!
- Repeat the procedure with all devices, which I have listed above.
- Make sure, that all above mentioned devices now have the same driver version v11.1.0.43 and are listed within the "Storage Controllers" section of the Device Manager.
- After having completed the driver update of all named devices, you can reboot.
- Now you hopefully will see and have access to your nForce RAID array.
- Please post your report about the result into this thread.
If we should get only positive test results from nForce RAID users, whose RAID array is outside the system drive, I will post the procedure for the nForce users, whose system drive is within the nForce RAID array.
Good luck!
new 32bit nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando.rar (428 KB)
new 64bit nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando.rar (460 KB)
I tested this solution and it works well! Thanks Fernando, you rock!
@harrytoddler :
Welcome at Win-RAID Forum and thanks for having tested the mod+signed driverpack!
I am glad, that it worked for you.
Regards
Dieter (alias Fernando)
Well, I tried all of the latest SATARAID drivers on my MCP61 with system drive in the RAID array. This also included a full Windows Reset; trying to install the AU fails and reverts back to v1511. I also tried the Group Policy setting to not allow driver updates for all Hardware and Compatible ID’s of the three nForce devices, along with the Fast Ring build, to no avail. There may be a newer one now, but I won’t hold my breathe… :-/
Anyone else had any luck with the AU, when the system drive is in the array?
I would think that using one of Fernando’s signed drivers as a third party driver at OS install would work, right? I was really hoping to avoid a full reinstall. The last time I did the ol’ F6 method was -many- years ago in XP. :-/
@jwhickman :
Have you already tried to install my new mod+signed 32/64bit NVIDIA nForce SATARAID drivers v11.1.0.43, which are attached to post #146? If not, you should try it.
Just follow my guide (at post #146) and try the Windows Update after having completed the driver update. Although I am not yet sure, I am confident, that you will be able to boot into the nForce RAID array afterwards.
Hey @Fernando ,
Yes, I tried the x64 drivers from #146, following the detailed steps. I tried it several times actually, including after the Windows reset, and again with the Group Policy driver update blocking. After the reboot everything works fine, and verify the expected drivers are still installed. But the AU always reverts to the v1511 build after the download, in-Windows prep/install, then reboot.
@jwhickman :
Thanks for having tested the drivers from post #146 and thanks for your report.
It is a pity, that the Windows Update doesn’t complete the update to v1607 despite the presence of customized nForce SATARAID drivers.
For testing purposes I attach another mod+signed variant of the 32bit and 64bit SATARAID drivers v11.1.0.43.
Maybe you or someone else can test them.
Good luck!
32bit nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando test variant.rar (428 KB)
64bit nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando test variant.rar (460 KB)
Hi Fernando,
a quick question?
You recommended the special driver Version 9.99.0.9 for a better raid performance.
When I added the needed lines for generic array device to the inf file I run into an hash error.
Can you please provide your special driver 9.99.09 with support for generic array device?
Thanks in advance
database-uli
Attached are the requested mod+signed "new 32/64bit nForce SATARAID drivers v9.99.09", which have been modified the same way as those, which I had attached to post #146.
Good luck!
new 32bit nForce SATARAID drivers v9.99.0.9 mod+signed by Fernando.rar (362 KB)
new 64bit nForce SATARAID drivers v9.99.0.9 mod+signed by Fernando.rar (383 KB)
Hi Fernando,
great work. The installation was no problem.
I will now test which version is the best for my configuration.
Many many thanks.
Database-uli
NVIDIA support is saying that they are working on a nForce-Update, but also: "And we do not have any ETA on that."
Maybe we can speed things up if more people are asking NVIDIA: http://nvidia.custhelp.com/app/chat/chat_launch
btw, they first answered that “It seems to be an issue with the Windows 10 update”. Only after I said that “there is an other discussion which says that there should be a driver update from NVIDIA”, the support said that they are working on an update.
Thanks again @Fernando , but still no luck with those. Would I be able to load your drivers at Windows installation ("text mode"), to try a clean install of the AU build v1607? I recall you mentioning before that the drivers couldn’t be rolled into the ISO due to the self-signed cert; would that be an issue if text mode is used?
Speaking of which, I found this doing a search:
https://msdn.microsoft.com/en-us/windows…on-requirements
+1 
Asus M2N32 Sli Delux. Raid1.
Thanks for having tested them.
It is a pity, that even these latest test drivers, where I had integrated the complete list of possible HardwareIDs into the INF file, obviously do not work for systems, where the system drive is within the nForce RAID array.
You can check it without touching your current data:
- Boot off an USB Flash Drive containing the clean Win10 v1607 image and choose, that you want to do a fresh install the OS.
- When you come to the point, where the Setup shows you all detected Disk Drives, but not your existing nForce RAID array, hit the "Load Driver" button, navigate to the previously stored desired mod+signed "new 32/64bit nForce SATARAID driver" v11.1.0.43 or v9.99.09 and load it.
- After having done that, you will get the information, whether the loaded mod+signed nForce SATARAID driver
a) will be accepted by the Win10 Setup and
b) is able to detect the existing nForce RAID array or not. - Now you can stop the test without having changed any of your data.
I am rather unsure, whether the Win10 Setup will accept at this early stage of the OS installation any driver, which doesn’t have the WHQL stamp given by Microsoft. The problem is, that the import of the Win-RAID CA Certificate requires a running Windows OS.
Maybe you can improve the chances to get one of my mod+signed drivers used by Win10 v1607 from scratch, if you had previously
a) removed the in-box nForce SATARAID driver v10.6.0.23 from the original Win10 v1607 image and
b) integrated the desired mod+signed nForce SATARAID driver v11.1.0.43 or v9.99.09 (attached to post #146 resp. #154) instead
according >this< guide.
Good luck!
Hi @Fernando I think my previous post was tl;dr, apologies for that.
It sounds like these steps would be useful for checking whether my Win8 system could be returned to Win10 (which was installed until the recent issues). Am I right to think that I can perform these steps as a test, then abandon the installation (whether the drivers work or not) and return to Win8 ?
Thanks very much for all your help here.