@opel07 : Thanks for posting the requested screenshots.
Afaik, for a working driver, there must be 1 match between device IDs in Device Manager and INF File. So adding the line %NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk makes the driver matching line 4 of the device manager.
Ok, attached are the mod+signed 32bit and 64bit NVIDIA nForce SATARAID drivers v11.1.0.43, where the included INF files have just been modified by me according to your proposal.
@Fernando Dieter, this worked like a charm! Updated the RAID drivers and the disks and the S-ATA Controller as well, signature accepted by Windows, rebooted, everything’s up and running. Installed the NVIDIA Control Panel from the package in the OP and now I have a fully working system with 1607! I cannot thank you enough!
It would be interesting if installing this driver also works for bootable arrays. Imho it should, if automatic driver update is disabled.
@all nForce RAID users: If I get some more success reports from affected users, I will customize the SATARAID drivers of all my “mod+signed nForce Driverpacks” the same way.
Just for your information: Besides the added line according the proposal from opel07 there are some additional differences between the original WHQL certified nForce SATARAID drivers v11.1.0.43 and the mod+signed variants, which I have attached to my last post:
The original drivers do only support MCP51, MCP55, MCP61, MCP73, MCP77 and MCP79 RAID systems, whereas my mod+signed ones hopefully will support all nForce RAID systems from NF4 (AMD/Intel) up.
Contrary to the original drivers, which have been designed by NVIDIA just for Vista and Win7, my mod+signed drivers are designed for all Windows Operating Systems from Win7 up.
I am having the same problem. Tried a BIOS update, checked the boot config, nothing seems to work. Might be time for a new motherboard, but I did read something about PUIS (power up in standby mode) which may or may not be the problem. Definitely a combination of Nvidia nForce drivers and Windows 10. I am also considering a PCIe RAID controller instead of swapping out the board. I think the bigger problem will be that the RAID will probably need to be rebuilt if I go that route.
I am going to roll back the update until I hear if there is a solution that doesn’t involve hardware upgrades!
@8019 and @shondryrocks: Welcome at Win-RAID Forum!
There is already an intensive discussion about this problem within >this< thread. Please read the last posts, where you can find a solution for nForce RAID users, who have their system drive (with the OS) outside the RAID array, but we don’t yet know how to solve the problem, when the user is not even able to boot into the OS. In the latter case it will be the best option to restore the previously used Win10 version.
EDIT: Maybe this procedure will solve even the problems of nForce users, whose system drive is within the RAID array:
If you are already affected by an unbootable system after having installed the “Anniversary Update”, restore your previously running system.
Download and unzip the 32bit resp. 64bit SATARAID driverpack, which I have attached to >this< post.
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) NVIDIA nForce Serial ATA Controllers, b) NVIDIA nForce RAID Controller and c) NVIDIA nForce RAID Devices. To get the mod+signed driver installed, you have to force the update by using the “Have Disk” button.
After having completed the driver update of all named devices, you can reboot.
Provided, that you can boot fine into your OS and everything is running fine, retry the update to Win10 v1607 (“Anniversary Update”).
My original plan was to post on this thread (but I wasn’t sure which post to reply to) NVIDIA: Optimized nForce Driverpacks for Vista/Win7-10 However, I think my question does apply to your recent edit of your own post.
Thank you very much for maintaining this forum. I have now read much of the information you have provided over several years, as well as your updates, in the last week or so. These are excellent and do not exist in any useful form elsewhere.
I am just trying to decide my next steps with my machine, and perhaps to add some info for other users. I have put quite a lot of details here for clarity. You are very welcome to edit/shorten this post as you feel is suitable.
I’m having problems with my machine (details in my signature) that had successfully upgraded from Win 8 to Win 10 32-bit (on 26 July 2016). I have a single disk (raid 0 disk array), which both contains the OS and is used to boot the machine.
On Friday 12 Aug, the machine would not boot. In my efforts to resolve this I have returned to Win 8 (via the return to a previous build option). Win 8 runs without problems. However, repeated attempts to upgrade to Win 10, from 12 Aug to 14 Aug, failed with the 0xC190010 - 0x20017 error. Mostly from this site, I understand this is related to nvidia raid drivers. The event log contains several nvraid error 11 messages.
By the way, I did not choose to install the anniversary update, and am not aware of any system message about it.
I was going to ask about creating a custom Windows 10 image, with NTLite and following your guide: [Guide] Integration of drivers into a Win7/8/10 image The steps in your post suggest this is not necessary. Am I correct? In step 1, you refer to a “previously running system”. Does this refer to both Win 8 and Win 10? My machine (I am guessing) had no previous Win 10 build to return to.
If I get back to Win 10, do I need to stop the drivers being overwritten by Windows 10 (whether due to updates or other methods)? If so, is there a post on this site that gives clear advice? I have a concern that if I do get the machine back to Win 10 and do nothing, I may end up with the same problems I have now. Or is it the case that the modified certificate prevents Win 10 from unhelpful driver updates?
As I have a working Win 8 system, there is no immediate need for me to resolve this problem, but I would prefer to return to Win 10 (in part so I can upgrade to 64-bit).
I used your guide to get access to my nvraid. The current situation is that I have V11.1.0.43 drivers in place for Sataraid and Nvidia_Sataide controllers. In the details I saw the connected ssd for each controller, but I was not able to get the generic_disk_array devices updated with the right driver.
Your help is appreciated.
I have currently no idea where I make the mistake ?
did you use the driver from Post #119? can you share the Device IDs of your Generic SCSI Array Devices?
Embarassing: I definitely have the issue (and cured it with Fernando’s driver), but checking winver I am still on 1511. Therefore the Problem seems to be with the Aug 9 Update ( https://support.microsoft.com/en-us/kb/3176492 ) and not 1607. I suspect the kernel mode driver update to be the bad guy that breaks device enumeration: https://support.microsoft.com/en-us/kb/3177725
EDIT by Fernando: Post number corrected (caused by its movement to this new thread)
I just tried installing the driver pack included in post #119. I was able to install the driver for “NVIDIA nForce Serial ATA Controller” and "NVIDIA nForce RAID Controller" But when I try to install the driver for “NVIDIA nForce RAID Device” I get an error that it can’t find a suitable driver for my device. I think you’ve removed too many lines as I can’t see any that match my Hardware ID’s in the version in post 119.
The moded 10.6 driver worked ok. Here is the Device ID from my system:
EDIT by Fernando: Post number corrected (caused by its movement into this new thread)
yes I used the driver from #119. will check later this evening the *.inf file I used. Maybe there is the problem.
I try to use have disk but always get the error no suitable driver found. It was late yesterday evening
Thanks and regards, Ulrich
EDIT by Fernando: The above mentioned post number has been corrected by me to avoid any misunderstanding by the visitors of this new thread. Due to the extraction of this discussion from the former thread all post numbers have been changed.
@all: Beginning at 18. July 2016 reported many nForce RAID users within >this< thread about the sudden unavailability of their nForce RAID array. Later on it turned out, that this severe issue has been caused by a Win10 Update, which switched the absolutely required “NVIDIA nForce RAID Devices” to not usable “Generic SCS Array Devices”. The bad consequence was, that the nForce Array could not be detected anymore by Windows.
Since the problem and the related discussion had/has nothing to do with my “Latest/Special nForce driverpacks for Win7-10”, I decided to create this new thread and added the recent contributions from other Forum members, who had already started a separate thread about the same topic. This way it will be much easier for us all to follow the discussion about a possible solution of the current problem.
I hope, that the movement of your contributions is ok for you.
well, this line should work for you as it did for me: %NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk -> did you install with "Have Disk" and provide the correct folder?
I’m sure I used the "Have Disk" option, I’ll recheck tonight when I’m back on my nForce based computer. That line you referenced doesn’t match any of the Hardware ID’s in my system there are too many underscores.
It looks to me like the following line should be added as it might be common amongst more systems. %NVRAID_DESC%=nvraid,SCSI\Array__NVIDIA This is the only line from the 10.6 version that matches any Hardware ID’s in my system.
Hmmm… will have to go and re-look at my nforce system. The one that worked for me was the 10.6.0.23 version that you posted around #550 in the other thread. Haven’t found it in this new thread yet. It is the one attached in post #79.
The Win10 in-box nForce SATARAID driver hasn’t been changed by Microsoft. It is exactly the same before and after July 2016. It obviously is the altered hardware detection routine, which caused the problems.
