OK, I'll contact Fernando for the details and give it a serious try in a few days, need to finish the current update first.
If until then you don't solve it, I'll aim to automate forcing signed drivers onto selected hardware, just like you can manually do from Device Manager.

@nuhi

Zitat von nuhi im Beitrag #245

---

@Nvidiapaddel, by nvraid I meant NVidia RAID driver, the nvraid.inf is the filename. There is one in Windows, and the other one you are integrating, IF the filename is the same, unimportant.
OK, thanks for the info, will see what can be done.

---

Zitat von Fernando im Beitrag #246

---

@all nForce RAID testers:
Recently I have created a lot of differently mod+signed test variants of the nForce SATARAID drivers v11.1.0.43 and v9.99.09 and uploaded them to >this< OneDrive folder, which is open for the public.
Additionally I have added my previously mod+signed nForce SATARAID drivers v11.1.0.43 and vv9.99.09, which I had attached to the posts #146 (v11.1.0.43) resp. post #154 (v9.99.09). They are named "new 32/64bit nForce SATARAID drivers".

---

Hi All,
Yeah I have exactly the same issues as edv.kleini :( On a EVGA 790i and Asus 790i Striker II Extreme. Successful boot and nvidia nforce raid detection using the built in drivers on Win10 X64 Pro.iso from JULY (Build 1511) - until you do the MS updates then its INACCESSIBLE BOOT DEVICE.

Booting from a Win10 X64 Pro.iso from AUGUST (Build 1607). Sees NO disks on install (except non raid). Unable to browse add drivers as they are not digitally signed. My knowledge is limited and not sure what else to try. Really don't understand what the hell MS has done as I don't think the updates are even related to storage/RAID devices. I'll keep tinkering and see if I find anything...

@ edv.kleini - Sorry to hear all attempts failed. I was hoping you would be the Person to confirm a fix. We cannot be that fair away.


Kind Regards,
Kenny B

Zitat von Fernando im Beitrag #259

---

@Nvidiapaddel:
@edv.kleini:
If I understand you correctly, the mod+signed drivers are not accepted by the Win10 Setup, if they are loaded at the beginning of the installation procedure.
On the other hand they are obviously accepted and used, if they have been integrated into the Win10 image.
Is this correct?

---

OK... I have attached working scsidev.inf locations and files from a working Win.10.1511 before the MS updates and a NON working 1607 build that wont see any RAID disks.
I have 1 x non raid SSD and 2 x WD disks in Nvidia RAID 0.

I did attempt to have a go using NTLite. I replaced all occurrences of the new scsidev.inf with the old one. Also removed the original Nvidia drivers and replaced with Fernandos new drivers on BOTH the INSTALL.WIM and the BOOT.WIM.

The PC found the Nvidia RAID disk :) DRIVE 0 PARTITION 1 - but it will NOT use it. You can format it... but nothing more (error - we couldn't create a partition or locate an existing one. Refer to log file? Not that I know where the log file is?)

Not sure if this is related to permissions as I couldn't work out how to replace the scsidev.inf files when the .WIM were loaded as I didn't have permissions... so I just found a reg file that allowed me to take ownership. Maybe I screwed up the permissions - which may explain the above?

Another issue I have noticed during this time is that it doesn't actually find or detect my other non raid ssd drive during this time.

One thing I did notice. During one of the tests using a new 1607. I was able to load windows on the non raid SSD. The Nvidia raid disk is not available during this time. if you then install Fernandos new drivers. Do the SHOW HIDDEN DEVICES thing etc (which I forgot to do last time! ) change all the nVidia and Generic SCSI ones - it does actually allow you to see the nVidia RAID disks after a reboot and you can format it etc - but that doesn't help anybody that wants to used the RAID disks as a bootable OS option.

My knowledge at this point is becoming limited but I hope this update provides some useful info to somebody.

Kind Regards,
K

UPDATE: Re-attached files. Provided a better screen shot. Please note I have 2 x SSD attached. One running the working Win10.1511 using the default nVidia drivers before any MS updates and the other Win10.1607 with no changes so not seeing any attached RAID disks. I can provide any further files if needed...

Hi,

1. a) original (untouched) Win10 v1607 image

DONE: Downloaded it today from:
https://www.microsoft.com/en-us/software...d/windows10ISO/

Choose version and language. I believe this to be the latest version.

Using x64 version. Fails to see nVidia RAID disks.

2 b) modded Win10 v1607 image, where the "bad MS driver" named scsidev.inf had been removed (BOOT.WIM+INSTALL.WIM) ?

is that just a remove... then test? or replace with an older 1511 version before creating the iso and testing?

I would just like to add...
I also took the already working Win10 X64 1511 from JULY and stripped out all the default nVidia drivers from both INSTALL and BOOT WIMS. I replaced them with your version - new 64bit nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando.

I can confirm the this test iso worked. It picked up the RAID array. It allowed me to create a partition. It booted and loaded windows. The nVidia drivers all show as 11.1.0.43 but listed as NOT digitally signed. So I guess running the Win-RAID CA Certificate will need to be executed at this point. I'll try that another time. Pointless working on an older ISO when we need to resolve the issues with the new version.

I'll crack on with tests and provide feedback as soon as I can.

Kind Regards,
K