Yes!
Hi Fernando. I have been following this issue very carefully every since I tracked down our issue to the recent update. I utilized your most recent drivers (“Latest nForce Driverpacks for Win7-10” from HERE) and appear (crossing fingers) to have gotten past a few reboots after the update was applied. One thing I did notice is that in POST the RAID is reported as degraded. I took the following screenshot of the device manager and am wondering if I am limping along on a single drive instead of the usual 2 which I had setup in RAID0. And yes, my boot drive is inside the RAID (something I noticed in your post that directions would be forthcoming for but I jumped the proverbial gun). 
Also, is there any more MediaShield for monitoring/changing RAID inside Windows?
Thanks for your help and drivers!
EDIT: On another “required” reboot I got BSOD and the old INACCESSIBLE_BOOT_DEVICE error. I used the restore point that I made per your instructions and am back to boot. I have locked down Windows Update so it can’t pull anymore crap (because even “hiding” the unwanted update doesn’t do anything). Here’s hoping for a solution from MicroSloth sooner than later. Bastards.
Worth noting, the RAID is still degraded on POST
@PsiFire :
Welcome at Win-RAID Forum and thanks for your report!
Yes, the "raidtool" application is within all my nForce driverpacks. If the tool has not yet been installed, you can do it by running the SETUP.EXE, which is within the IDE\Win764\raidtool subfolder.
Good luck!
Dieter (alias Fernando)
@ all affected nForce RAID users, whose system drive is within the RAID array:
According to my knowledge it is a bug of the Win10 hardware detection, which makes the nForce RAID array unaccessable after having completed the Win10 “Anniversary Update” procedure.
Details:
For a proper detection and function of the nForce RAID array it is an absolute requirement, that the following devices of the Device Manager’s “Storage Controllers” section use the exactly same NVIDIA nForce RAID driver:
a) the “NVIDIA(R) nForce RAID Controller” and
b) all usually hidden members of the RAID array named “NVIDIA(R) nForce RAID Device”.
Unfortunately Microsoft has done a severe mistake while creating the v10.0.14393.0 of the Win10 v1607 in-box INF file named scsidev.inf, with the bad consequence, that the Windows Update routine detects the members of an nForce RAID array as “Generic SCSI Array Devices”, which don’t need any real driver (= *.sys file). That is the exact reason why nForce RAID users, whose system drive is within the RAID array, cannot boot anymore into Win10 after having completed the update to Win10 v1607.
Possible solution:
It is a wellknown fact, that the freshly installed storage drivers and the related updated device names are already shown within the Device Manager, but will not be used until the final reboot.
Maybe there is a chance to correct the installation of the wrong “driver” at this point of the Windows Update, that means before going to reboot the system.
The procedure will be very similar to my guide, which is within post #146, but with the following changes:
The execution of the points 1-3 should be done before starting the Windows Update, whereas the other points (4-6) thereafter, but before doing the final reboot.
It would be fine, if anyone can test it and report here about the result.
That’s a good thought and I thought about trying to “catch” the drivers before they got changed as well. Problem is - I checked the driver version before every reboot
and always had your 11.x version showing before booting yet still got BSOD. 
I tried this the other day actually, after confirming that the August Cumulative Updates [ACU] did also trigger the INACCESSIBLE_BOOT_DEVICE after the 2nd reboot (which I had seen mentioned previously, but was focused on the Anniversary Update [AU] at the time).
This test also explained something else I encountered one time in the original barrage of testing; when trying to install your driver, my Nvidia RAID Device changed to the Generic RAID Device. I replicated this action in the latest test. After allowing the ACU to install with the MS in-box drivers and requisite reboot (went fine), I then manually installed the latest v9.99 drivers; and this is where installing the Nvidia RAID Device changed to the Generic RAID Device, so I once again installed the same v9.99 driver, then it went back to the Nvidia RAID Device. Then I rebooted and everything was still working (still pre-AU). However, applying the AU once again triggered the INACCESSIBLE_BOOT_DEVICE BSoD. I plan to try the ‘clean install test’ to see if it will load your signed driver, and if that works, I will try the install. Anyone try this already? I’m naively awaiting a new Insider Fast Ring build first though, in hopes that MS has fixed it. "Don’t hold your breath," I know…
Well, it may or may not be helpful, but here is the transcript of my painful discussion with nVidia just now:
Kenny: Hi, my name is Kenny. How may I help you?
Phil: Hi. Just throwing in with the others having nForce issues due to Windows 10 August updates. Is there an ETA for any sort of fix? My RAID drives are GONE!
Kenny: Unfortunately this chipset is not supported with Windows 10 and there will be no driver developed for this legacy product.
Phil: ? It is being reported on several sites that nVidia is aware of the issue and working on a fix. Are you telling me that is not true?
Kenny: It’s not an issue Philip, it’s just that nForce chipset are legacy and these aren’t compatible with Win10
Phil: Are you telling me that nVidia is NOT working on a fix as is being reported?
Kenny: If you are looking for the Win10 drivers for nForce chipset then I’m afraid to say that you won’t get any driver for this as the chipset can’t handle Win10
Kenny: I would hence suggest staying with your existing operating system.
Phil: So, you are telling me that nVidia is NOT working on a fix as is being reported?
Kenny: yes , but please understand that this is not an Issue
Phil: It is not an issue that none of my RAID arrays are available for use any longer? I disagree.
Kenny: That could be because the nForce chipsets don’t have drivers now as it is win10
Phil: From a related forum - "NVIDIA support is saying that they are working on a nForce-Update, but also: "And we do not have any ETA on that."
Phil: This is why I am contacting you. It is being reported in several places that nVidia is working on an update. You are telling me that this is not true.
Kenny: But that’s not an official update, it’s just a forum. In forum users will post all their assumptions and guesses
Kenny: So let me inform you this Philip that this chipset will not have a driver for Win10 OS
Phil: It has had one and still does. I’ve been using it for a long time. The latest Windows update broke it for thousands of people. We are all trying to get our systems working again. I’m one of the lucky ones that didn’t use RAID for my boot device. those that did are severely crippled.
Kenny: if the issue has started after Windows updates then please contact Microsoft to report the issue because we never released a driver for this chipset
Phil: Were you aware of this issue before I contacted you?
Kenny: No
Phil: Is there anyone available that is aware of this issue that I could speak to, please?
Kenny: I’m afraid because it’s not an update from our end which caused the issue
Phil: Can I please speak to someone that is aware of this issue?
Kenny: I can surely pass it to someone however I’m afraid the solution will be the same provided by them too
Phil: Can I speak to someone that may have been aware of this issue?
Kenny: 1. As per your request I can transfer to some other engineer.
2. For the nForce chipset issues in Win10 is not a problem from our end because this chipset is not supported in Win10
Phil: OK. Please transfer me to someone that was previously aware of this issue.
Kenny: Please hold on
Phil: Thank you.
Kenny: most welcome
Rajath: Hi, my name is Rajath. How may I help you?
Kenny has left the chat.
Rajath: Hello Phillip
Phil: Hello. Thank you for talking to me.
Phil: There is an issue concerning the anniversary update for Window s 10 which disallows the system to see the nVidia RAID devices correctly. It has been reported that nVidia is looking to help the thousands of end-users that now have their RAID drives unavailable to them. Is nVidia looking into this and if so is there a timetable of any type? Thank you in advance.
Rajath: I apologize for the inconvenience caused phillip, This is a legacy chipset that is no longer supported for windows 10.
The same setup might have worked fine before the anniversary update unfortunately there are no drivers available for nforce chipsets while using windows 10.
The only option that you can try would be to rollback (restore) the system to the earlier condition before the anniversary update. Unfortunately there are no drivers that would be available for nforce chipsets while using windows 10.
You may continue using the system without updating to anniversary update (if it worked fine earlier) or you would have to use an earlier operating system which supports drivers for the Nforce chipset.
Phil: So, nVidia is NOT working on any sort of fix for this widespread issue?
Rajath: This is a legacy product that is not supported for windows 10 hence there are no plans of driver support for this product (for windows 10)
Phil: So, to be clear, nVidia is not working on anything that would alleviate this issue?
Rajath: Yes, There are no drivers that are being developed for nforce chipsets to work with windows 10.
Phil: OK. Thank you.
Rajath: Thank you for your time.
Again this is not an issue its the hardware that is not being supported with windows 10 and there are no updates for the same.
Rajath: Check if there are options of restoring the system to an earlier condition before the update
Phil: It is most definitely an issue to the thousands of people that no longer have access to their data on nVidia RAID arrays.
Rajath: I completely understand that phillip, As i mentioned you can choose one of the options in order to continue using Raid
Rajath: You may continue using the system without updating to anniversary update (if it worked fine earlier) or you would have to use an earlier operating system which supports drivers for the Nforce chipset.
Phil: I understand. But telling people that "it is not an issue" is not going to go over very well. Thousands of people that are receiving automatic updates on their PCs are losing the ability to get to their data and many of those people can no longer even boot their systems. The impact of this should not be trivialized.
Rajath: I understand, But this update is not something that we can control as its directly from the OS (microsoft)
Phil: Yes, I know. But nVidia could look into the issue to see if there is something relatively simple that they could do to help. But you are telling me that they are not going to do that.
Phil: Again, thank you for your time.
Rajath: Thank you for your time and patience.
Rajath: Have a good day, Again i am sorry for the inconvenience caused.
EDIT by Fernando: Blank lines removed (to save space and for a better readability)
Questions:
1. Did you check the driver version of the listed "NVIDIA(R) nForce RAID Devices" resp. "Generic SCSI Array Devices" as well?
2. Are you sure, that the installed drivers were the mod+signed nForce RAID drivers v11.1.0.43, which are attached to post #146, and not the original ones as part of my "Latest nForce driverpacks", which I am offering within the start post of >this< thread??
@jwhickman :
Thank you for doing some tests to find out, whether my mod+signed drivers will be accepted by the Win10 Setup, if they are loaded from scratch.
We are awaiting your report.
@KylJoy :
Welcome at Win-RAID Forum and thanks for having posted all details about your discussion with NVIDIA employees about this topic.
It is hard to believe, that NVIDIA as one of the biggest chipset manufacturers until 2010 is not interested in helping the users of their chipset to get access to their data.
Although I don’t have any nForce chipset since many years, I will not give up trying to find a solution for the nForce RAID users.
Kind regards
Dieter (alias Fernando)
Well, my PC took an update just now from Microsoft. It did not resolve my issue. BUT… I followed the procedure you outlined in post #146 and I am working great now! I am unsure if I had failed to follow the procedure correctly before or if the update from Microsoft changed something that allowed this to work.
Thank you very much! My data is back! 
@KylJoy :
Thanks for your report! I am glad, that you succeeded by installing the mod+signed nForce SATARAID drivers, which I had attached to post #146 and following my related guide.
Additional question: Is your system drive containing the OS inside or outside the nForce RAID array?
I use an independent SSD for the OS so I was not as bad off as some. I store large amounts of data and some applications on RAID arrays. This PC is still going strong thanks to you!
I see build 14915 just came out…unfortunately I will be out-of-town through Sunday, but I will continue this testing then; unless someone figures it out in the meantime! 
I’m having trouble installing Windows 10 on my nForce RAID
it used to work, but since Windows 10 anniversary update, it no longer detects the SATARAID array. I have even tried adding the drivers in this post during the install, but no luck - it does still not detect.
I have a nForce 730i chipset with 2 drives in a RAID0. This raid group is my system (boot) drive.
Has anyone else come across this problem since anniversary update?
-js
@narf :
Welcome at Win-RAID Forum!
Since there is already a special thread about your problem, I have moved your post into that one.
Summary of the current situation:
- All NVIDIA nForce RAID users are affected by the recent Win10 Update issue, which makes the existing nForce RAID array unaccessable.
- Obviously neither NVIDIA nor Microsoft are willing to fix the problem.
- Meanwhile we have a solution for users, whose nForce RAID array is outside the system drive (look into post #146).
- There is yet no solution for nForce RAID users, whose system drive is part of the nForce RAID array, to get their Win10 updated to v1607 ("Anniversary Update").
- Any ideas or suggestions are welcome.
Regards
Dieter (alias Fernando)
thanks @Fernando
has anyone had success hiding the update using the windows 10 Hide update tool? https://support.microsoft.com/en-us/kb/3073930
it seems after a while to ignore and install anyway.
even tried blocking driver updates http://www.howtogeek.com/223864/how-to-u…-on-windows-10/
but it ignores that as well!
I’m back on Windows 7 until someone finds a solution.
-narf
@nForce RAID users, whose system drive is within the RAID array:
As I already have written, I doubt, that Microsoft or NVIDIA will help you to get Win10 v1607 (“Anniversary Update”) properly installed onto your nForce RAID array. So we should work ourself on a solution.
This is my idea:
Since it is the wrong resp. not matching Win10 v1607 in-box “driver” named scsidev.inf v10.0.14393.0, which is installed by mistake instead of the correct NVIDIA nForce RAID driver, all your troubles may be gone, if you do a clean install of Win10 v1607, where the related INF file (scsidev.inf) had been previously removed from the Win10 image.
To make it as easy as possible for you, I have already created such “modded” Win10 x64 v1607 ISO file, which contains the complete Win10 Pro x64 EN-US Retail image, but without the “bad driver” named scsidev.inf. This file has been removed by me from the INSTALL.WIM and BOOT.WIM by using the tool NTLite.
Since I do not have access to any nForce system, we need someone, who is willing to test a clean install of Win10 Pro x64 v1607 EN-US onto his/her nForce RAID array by using the ISO file, which has been prepared by me.
Interested users should send me a PM.
They can decide, whether they want the link to the EN-US ISO file, which has been already customized by me, or want to create the customized ISO file themselves by using a special free NTLite version, where the author nuhi has enabled the usually blocked option to remove the “driver” named scsidev.inf (big thanks to nuhi for this extra work!). The procedure can be done according >this< guide.
On behalf of all affected nForce RAID users I hope, that we will find someone for the required test.
Good luck!
Dieter
Fernando: I wish I could remember where I retrieved the drivers. I don’t know if I got them from Post 146 or from the other page you mentioned. I just checked my downloads and that doesn’t seem to help solve the mystery.
EDIT: I just looked and The directory I have is “Fernandos Latest 64bit nForce Driverpack for Win7-10 x64 v10.4” so it appears I did NOT use the drivers from Post 146. Sorry about that. I’ll pull those drivers you posted there and see where they get me. I’m gonna try to rebuild the degraded array and go from there. With a little luck I may even be able to step back to before the update and see if I can insert the drivers in there somewhere.
I’m going to PM you as I’d be interested in fresh installing with the ISO you mentioned. I pulled my backup drive from the vault and will make a new RAID Mirror with that and one of the old drives and keep the other for backup.
I’m in the same boat. Gonna try Fernando’s ISO for a fresh install and see where that gets me. But barring that I’m going back to Windows 7. It’s absolutely ridiculous that MS would FORCE an update on us that doesn’t work and give us NO WAY to keep it from installing.
EDIT by Fernando: Unneeded parts of the fully quoted text and blank lines removed (to save space)
@PsiFire
What I can’t believe is in Windows 10 Microsoft can simply deprecate hardware whenever they feel like it. My system passed the upgrade assessment from win7 no problems. All of a sudden they pull the plug with no way to opt out! That would never happen in win7.
I’m worried, if Fernando fixes this issue, what’s to say they don’t do something down the track to break it again?