Finally got it working. Some leftovers from attempts to install had caused MBR errors.
Now up windows 10 working.
One remark: If I look at the NVIDIA drivers 11.1.0.43 they are not digitally signed, also, I don’t succeed in loading your 64bit nForce SATARAID drivers v11.1.0.43 for orig scsidev mod.
Jaap
Why did you wat to "invoke" the already integrated drivers again? What do you mean with "invoke" at all?
You obviously have done a mistake (proof: I have done the same operations very often by using the same tool and the same files and I never got an error message).
Thanks for your feedback. It is fine, that you finally succeeded.
Yes, this is already wellknown:
1. It is generally not possible to directly replace any driver by exactly the same driver. I have never modified the real driver (= *.sys file), just the associated INF file.
2. A mod+signed driver, which had been successfully integrated into a Windows OS image, is accepted by the OS and works as a WHQL certified driver. So it is absolutely useless to import the Digital Signature Certificate.
If you should nevertheless want to replace any mod+signed driver, which is shown by the OS as being "unsigned", by a "correctly signed" variant, you may have
a) to import the Win-RAID CA Certificate (if not already done),
b) to manually "update" the currently running driver by any other driver version,
c) to reboot (maybe a critical situation) and then
d) to force the re-installation of the desired mod+signed driver again.
Well,
I don’t mind about a certificate, but in an earlier post you wrote:
b) “for orig scsidev” (may be used once the OS is successfully installed to prevent later problems during a Windows Update, INF files additionally contain some HardwareIDs of the original MS in-box scsidev.inf file incl. the word “Array”)
So how is it possible to install this driver, or is it not neccesary?
I hope, that it is not necessary, but if you really need to install these especially modded nForce SATARAID drivers, you probably have to replace the currently running mod+signed nForce SATARAID drivers (e.g. v9.99.09) by another version of my mod+signed nForce SATARAID drivers (e.g. v11.1.0.43).
This is not very difficult to understand (not even for me).
Do you really think, that the NTLite functionality is different for a German and an English language ISO file containing the same OS Edition (processing of an English ISO works, but doing the same tasks with a German ISO not)?
I really doubt, that this an NTLite bug and think, that you have done something wrong while processing the ISO file. It has been obviously the first time, that you worked with the tool NTLite…
Hi, please can someone help.
This is exactly what happened to me. When I installed Windows 10 v1511 it all worked fine, but when I applied the anniversary update I then got “INACCESSIBLE BOOT DEVICE”, so I am now trying a clean install of v1607.
I have 4 disks in 2 arrays:
-3x 1TB HDD RAID 5 (storage)
-1x 500GB SSD SPAN (system)
However neither of them are detected in the Windows 1607 installer (1511 installer sees them fine).
I followed the article (really great btw!) and removed the nvraid.inf and scsidev.info from both the BOOT.WIM and INSTALL.WIM sections. I then added Fernando’s mod scsidev and the mod SATARAID 11.1.0.43 driver to both sections. Created an ISO then created a USB drive with Rufus, but the 1607 installer still says I have no disks present.
I am really stuck.
Did I miss a step?
Could it be anything else?
If someone could please help me I would be VERY grateful!
PS - My system is:
ASUS M2N-68AM motherboard (with NVIDIA nForce 630a chipset)
3000+ AMD Athlon X2
4GB RAM
3x 1TB HDD RAID 5 (storage)
1x 500GB SSD SPAN (system)
@martinzima :
Welcome at Win-RAID Forum!
This error message is not easy to understand, because your system drive, which contains the boot sector, is outside the RAID array. So a clean Win10 v1607 install wouldn’t even have been necessary, if you would have temporarily unplugged your RAID array members while running the "Anniversary Update".
Nevertheless the clean install of Win10 v1607 should work. I have no idea why it didn’t.
The only advice I can give is: Unplug all unneeded disk drives (in your case inclusive the nForce RAID array members), before you (re)-start the OS installation.
Regards
Dieter (alias Fernando)
Thanks for getting back to me @Fernando
In my case, my BIOS SATA controller has two modes:
- RAID (makes RAID available)
- SATA (disables RAID)
If RAID is selected, the BIOS on my ASUS M2N68-AM motherboard then only allows RAID arrays to be bootable (in the BIOS BOOT PRIORITY menu). This means my system/boot drive has to be in a RAID as well. If I do not set it up as a 1-disk RAID array, my motherboard will not boot to it.
So, to clarify/recap, I have:
ARRAY 1: SPAN/JBOD - 1x 500GB SSD, disk 1 [boot]
ARRAY 2: RAID5 - 3x 1TB HDD, disks 2,3,4
So I can’t really un-plug all my RAID arrays as you suggested.
*** TECHNICALLY, I can delete ARRAY 1 (I set port 1 to DISABLED in the RAID controller). This DOES make DISK 1 (my SSD system disk) visible to the 1607 installer!.. HOWEVER I get an error/warning saying: “Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure the disk’s controller is enabled in the computer’s BIOS menu.” - I assume this is because of what I described above where the BIOS only lists RAID arrays in the BOOT PRIORITY menu.
-----------
If I could please ask a questions:
1. Are you familiar with the “windows cannot be installed…” message. Can I get round this?
2. Was my following of the steps correct (i.e. was it correct to use to 11.x mod SATARAID driver with your mod SCSIDEV (and delete both nvraid and Microsoft scsidev from the ISO)?
3. Should I have used the orig versions of both drivers (if so, do I still delete both the OOTB drivers on the ISO?
4. What is the main difference between the SATARAID 9.x, 10.x, 11.x please (… I mean, why did you kindly spend your time to give us 3 versions?)
Thanks in advance!
… I really hope you can help me to get this solved… I have been looking for a solution for months 
@martinzima :
Thanks for the details of your nForcesystem. Your special configuration indeed makes it more dfficult to get Win10 v1607 proper installed.
Nevertheless I generally recommend to unplug all disk drives, which are not needed for the OS installation (in your case the members of the RAID5 array), before starting the OS install.
Usually you get this message, when you choose a target destination for the OS installation, which is either unusable or too small sized.
Yes (provided, you have done it correctly).
No, it is better to remove the original drivers from the ISO image and to replace them by the modded ones. The alternative drivers are meant for as alternative, if any Windows Update later on should replace the modded driver by an updated original one.
Although all 3 modded driver versions probably will support all nForce chipset systems from nForce4 up (I have added the missing HardwareIDs into the related INF files), there are some differences:
1. The old nForce SATARAID drivers v9.99.09 are primarily designed for "LEGACY mode" nForce chipsets (nForce4 AMD=CK804, nForce4 Intel=MCP04 and nForce 430/410=MCP51) running in RAID mode.
2. The nForce SATARAID drivers v10.6.0.23 are the Win10 in-box ones and may run with all nForce chipsets.
3. The nForce SATARAID drivers v11.1.0.43 are the latest NVIDIA has ever released and are recommended for all nForce chipsets from MCP65 up.
Thanks for your continued help @Fernando !
It’s a shame (almost) that I did everything right, I was kind of hoping that it I had missed a step and if I tried something different it would work, but will see how I go.
PS - If I disable RAID the disks are visible, so as a last option I could go to a non-RAID setup (but don’t really want to do this due to the obvious data loss risk).
I will try again with the 9.x and 10.x drivers, just in case that makes a difference. Fingers crossed. (I will update with the results tomorrow).
Thanks again Dieter!
@martinzima :
I wish you good luck!
Important information for all nForce RAID users:
The latest free NTLite versions from v1.2.0.4400 up do fully support the required customization procedure of the Win10 v1607 ISO file. A big thankyou goes to our Forum member nuhi, who has implemented these enhanced functions into his free NTLite tool.
Since this new NTLite version is available for the public, I have removed the “special” NTLite v1.2.0.4247 Beta, which had been offered by nuhi for the nForce RAID testers, from my OneDrive account.
Meanwhile I have added this information to my guide about how to do the special customization of the ISO file (>LINK<).
Good luck!
Dieter (alias Fernando)
@Fernando
v10.6.0.23 worked!
The Windows 1607 installed detected both RAID arrays and I was able to install Windows as normal.
Thank you so much for your time and effort, creating these files and helping myself (and others) get through this Microsoft issue!.. If you ever come to London, I will buy you a drink! 
One question, now that I added your mod drivers to INSTALL.WIM (and so my system), what is to stop Microsoft doing another update which replaces the scsidev.inf again?
You mentioned something about replacing the the mod file with the orig after install?.. Is that correct, please could you explain a little bit more about what I should do to avoid a similar disk issue in the future.
Thanks!
Martin
PS - Recap for anyone else with issues…
I have…
- Asus M2N68-AM motherboard (quite old, about 7 years)
- NVIDIA nForce 630a / Geforce 7025 chipset
- RAID for my system drive
To get it working, I…
- Used a Windows 10 v1607 x64 ISO (from Microsoft)
- Removed Components > Drivers > Storage Controllers > NVIDIA | nvraid and Components > Drivers > System Devices > Microsoft | scsidev.inf
- Added Fernando’s mod scsidev.inf and Fernando’s mod v10.6.0.23 NVIDIA nForce RAID
- I did this to BOOT.WIM Windows Setup, BOOT.WIM Windows PE, INSTALL.WIM Windows
- Created an ISO and loaded to USB with Rufus
- Installed as normal
First of all, A Great thanks to Fernando for he´s fantastic work. Second of ty Martinzima, i´v also had the same issue thou not same setup, just 2 old raptor disks in raid 0, but untill i tried the 10.6.0.23 i couldn´t find my array either.
Now i got my old server up and running again, but i got a question.
I did the ISO as guide stated with the mod scsi and nvidia raid drivers. Is there anything i need to do in windows to prevent next patch to ones again screw things up?
//Seraduxos
@martinzima :
Hello Martin,
I am sorry for my late reply, but I was travelling the last days and had no time to go online for a longer time.
Thanks for your feedback and your report about what you did! I am glad, that you succeeded with the clean install of Win10 v1607 onto your nForce RAID array.
Although I am rather unsure, whether it will prevent any future problems, when my mod+signed scsidev.inf file will be overwritten by a new original scsidev.inf file as part of a future "Cumulative Update" delivered by Microsoft, I recommend to install any of my mod+signed nForce SATARAID drivers with the word "for orig scsidev" after having successfully installed Win10 v1607.
The INF files of these mod+signed drivers do additionallly contain some HardwareIDs of the scsidev.inf and my hope is, that this will prevent, that the required nForce RAID driver for the nForce RAID Array Devices will be replaced by the updated original MS scsidev.inf "driver".
@Seraduxos :
Welcome at Win-RAID Forum!
You may try what I have written above. Maybe it will prevent future problems.
Regards
Dieter (alias Fernando)
Thanks @Fernando
No problem. Am amazed at the speed you reply anyway to be honest… Most forums I look at are "last reply 2014" and no-one (not even the moderator) has bothered to respond. Like I say, so far you have been the ONLY man/website to get my PC working, so I am really grateful!
So I guess, just to be clear, when you say "install"… I should go into…
1. Device Manager
2. select the NVIDIA Storage Controller
3. Go to update driver
4. Select your NVIDIA for orig scsidev driver
Is that right?
Also, I should make NO changes to the mod scsidev file currently in my Winows installation?
Thanks again!
Yes, but you have to manually update the driver of all nForce RAID related devices: NVIDIA nForce Serial ATA Controller, NVIDIA nForce RAID Controller and all listed NVIDIA nForce RAID Devices (they are usually hidden, to make them visible, you have to hit the "View" tab from the menu and to check the option "Show hidden devices").
Important:
1. Before you start with the driver update, create a restore point (to be able to return to the currently running driver in case of any trouble).
2. As first step you should import the Win-RAID CA driver signature Certificate.
3. Maybe you have to install a NVIDIA nForce SATARAID driver with another version than the one you are actually using, because the OS may not accept a driver "update" by using the exact same driver (only the content of the associated INF file is different).
4. You probably have to force the driver update by using the "Have Disk" button.
5. Don’t reboot unless you are sure, that all above mentioned devices have gotten the updated driver variant.
Yes, you should not touch the scsidev file.
Hey Fernando
Well I have had all good reports from my friends with Nvidia Boards so that great news.
Just one issue that I have found. I also have a Nvidia Board which has I use as a backup PC Media Center. I use a bootable USB created by Symantec System Recovery 2013 R2 to create backup images of the OS depending if I am using Win7 or Win10.
Its been a while since I used it but I created a bootable USB the other day. It should add the drivers from within the current OS - but its not working. I am speaking to Symantec about this. In the meantime I am trying to sort it out myself by messing about with the USB image. I did try to add the scsidev.inf driver to the USB when creating it with SSR 2013 R2… but it complaining there is no .sys file for it?
Any ideas on getting a scsidev.sys file created? not sure where to get one from to be honest? Was hoping you might have a possible solution? I don’t even know if this will work… but its my first step at trying to add the scsidev.inf to the USB image to enable it to see my RAID OS for BACKUP and RECOVERY of OS images.
Kind Regards,
Kenny
@kingkenny :
The SCSI devices, which are managed by the Win10 in-box MS file named scsidev.inf, don’t need a real driver (= *.sys file), an scsidev.sys file is neither available nor usable. Even if I would be able to create such *.sys file, it would not work.
Nevertheless it is possible to use the MS scsidev “driver”, which has been modified and signed by me. You can find it within my OneDrive folder, which I have linked within >this< post.
Hi, Fernando
I have motherboard GA-M750SLI-DS4 (rev. 1.0) NVIDIA nForce 750a SLI Chipset.
short history:
1.Win7 Ultimate 64bit installed on RAID0 all ok
2.Upgrade to Win8 (RAID0) all ok
3.Upgrade to Win8.1 (RAID0) all ok
4.Clone system from RAID0 to separate HDD.
5.Disconect two HDD’s (RAID0) from motherboard
6.Boot OS from separate HDD (all OK)
7.Upgrade to Win10 (on separate HDD) (all OK)
8.Connected two HDD’s (RAID0) to the motherboard
BIOS see array as “Healthy"
I manually update the nForce SATA and RAID drivers.
NVIDIA nForce Serial ATA Controller - installation ok
NVIDIA nForce RAID Controller” - installation ok
but
NVIDIA nForce RAID Devices - installation fail with windows error code 31
Windows Explorer and Disk Management not see the RAID0 partitions (with a lightly different name).
I see all physical HDD’s (plugged to motherboard) in “NVIDIA nForce Serial ATA Controller” , on tabs "port…"
I tried all possible drivers, the same effect (NVIDIA nForce RAID Devices - instalation fail with windows error code 31)
Maybe you have any suggestions?
Robert
@trojanrob :
Hello Robert,
welcome at Win-RAID Forum!
Since your post matches better this thread, I have moved it here.
Questions:
1. Did you try to install any of my mod+signed nForce SATARAID drivers, which you can find within >this< OneDrive folder?
2. How did you try to install the nForce RAID driver for the nForce RAID members named "NVIDIA nForce RAID Device"?
3. Are the usually hidden devices named "NVIDIA nForce RAID Device" listed within the "Storage Controllers" section of the Device Manager at all?
4. Have you read >this< and >this< post?
Regards
Dieter (alias Fernando)