Hi i was afected by te update 1607. In the last oportunity the computer work fine whit the nforce latest driver. (Windows 10 pro Latin 64bits). This happen in RAID 0 on mcp61pm.

That only can i do to use my computer is install Windows with the first media creation CD released for Windows (ver 10.0)

In this moment im trying to install the versión 1607 from a recently created media creation CD.

Booting the Cd, this cant identify de HDD.
Trying to install/update from CD inside Windows, the computer go to reestar & in the booting cancel the install.

This is the actually ver of Windows that i can use with "64bits nForce SATARAID drivers v11.1.0.43 mod+signed by Fernando".

But i cant do a update.
In this moment i go to try changing the drivers to: test1/test2/test3.

Ill comment the resultados. The procedure Will be install/update inside Windows.

Im So sorry, is cant*** the cellphone auto corrected the word :(

im first tryin to do the update only inside windows.

Hi all, and probably for the last time,

The analysis I promised won't be possible, since after the next Cumulative Update (Sept.) was installed, I had no subsequent issues with my array. No drivers or INFs were overwritten.

Anyone who still has issues with the INACCESSIBLE_BOOT_DEVICE on a boot array, please PM me - I'm convinced I can get it working.

Thx to all,

Justin

Hi Justin,

Please share your results and the process you used to get this working. Did you have your Raid array as a bootable OS?

I was able to get fernando's drivers working BUT only after implementing them after booting to a non raid SSD. Once I had applied the Win-RAID CA and changed the drivers (show hidden devices etc...) I was able to see my Raid array but only as an additional extra drive. I have NOT been able to use the device or set it as a bootable raid device.

I've been looking at this for over a week now and getting tired. If you have any information to share that would be great for everybody on this forum :)

I am currently going through the list of activities that Fernando requested. I should have the results later today.

Much Appreciated.
K

Hi,

Please find attached test results as per requirements from Fernando. I hope they make sense.

Kind Regards,
Kenny

The results!!!
Trying to install booting the CD win10 pro 64bits latín.
...this no detecte tehe array, neither driver can be loaded, only the WHQL can be loaded buthi this don show the array 0.

The results!!!
Trying to install/update the versión win10pro 64bits latín inside Windows after install Fernando drivers the install is loaded but in the reebot show a recoger screen, in this only can be selected startup advanced options/off/etc etc.

But in the next reebot loging in Windows, show this screen.

Zitat von ENAJonas im Beitrag #279

---

Anyone who still has issues with the INACCESSIBLE_BOOT_DEVICE on a boot array, please PM me - I'm convinced I can get it working.

---

Hi, Fernando my next TEST will be Edit/erease/remplace a file from Win10.iso (ver10.0) to Win10.iso (ver1607) .
But my cuestion is, wich files/folder have to be modified in the Win10.is (MOD)???|addpics|at2-1-67b2.png|/addpics|

EDIT by Fernando: Unneeded fully quoted post removed (to save space)