no_connection
Patron
- Joined
- Dec 15, 2013
- Messages
- 480
This bug as been around for many years, yet Microsoft never seems to care.
Network dives comes up with a red X in them while Windows happily notifies you that it failed to mount all network drives.
Clicking on a drive mounts it. But if you try to access a file (like a song in a playlist) it will fail. Leaving you with annoyance.
Reinstalling Windows *might* fix it, but who has time to do that. From what I know there is no fix.
I am forced to use a .bat file to mount my drives with net use at startup. But even that is not reliable enough as it might fail leaving me with less than optimal number of drives.
Any tips on how to reliably mount drives at startup?
Network dives comes up with a red X in them while Windows happily notifies you that it failed to mount all network drives.
Clicking on a drive mounts it. But if you try to access a file (like a song in a playlist) it will fail. Leaving you with annoyance.
Reinstalling Windows *might* fix it, but who has time to do that. From what I know there is no fix.
I am forced to use a .bat file to mount my drives with net use at startup. But even that is not reliable enough as it might fail leaving me with less than optimal number of drives.
Any tips on how to reliably mount drives at startup?