Windows 10: Connecting to NAS drives on initial boot

I am getting the usual problem that windows has never fixed. On boot up quite often I get the message that network drives could not connect. They are 'X'ed out, but on clicking they are really there. It used to be the random way windows boots all the drivers up. But on reboot it all seems to work. Is there any boot item that needs to be delayed to allow network card to fire up before it tries to connect to the network. This does not affect internet connection just nas drives.

:)

 

Ovi Suiye 2.1 - Initialising Failed (Unable to proceed with the installer execution)

Same thing happened to me too. Didn't initialized even from a NAS drive. Copied to local drive and installing OVI worked fine.

 

Blue Screen with DRIVER_POWER_STATE_FAILURE when iSCSI device is absence

I has a Synology NAS and set up a iSCSI Target. My SP3 connected the iSCSI target via
iSCSI Initiator, which is located at "C:\Windows\System32\iscsicpl.exe".

The error occurs when I power up the SP3 when the NAS is powered down or not connecting the WLAN where the NAS serser locates.

 

I had a similar problem that went away after I disabled the NAS sleep function. I put it down to too long a delay at NAS wakeup.

Not saying this is the same as yours but may be worth looking at.

 

I sometimes get this and I think its because there is some delay when Windows actually connects to the internet and other connections. Sometimes you can see the triangle on the network icon in systray before it actually connects.

 

I've also seen that triangle but just on one comp but that seems to have gone away now.