Windows 10, especially SSD's, intermittently losing manually mapped drives
Windows 10 pro workstations, ESPECIALLY SSD's, lose mapped drive connection with file shares on a Server 2008 R2 server. Everything fine after a restart. No problem initially joining the network or setting up network shared apps like Timeslips or addressing network shares. It's just some sort of timeout/standby/sleep feature that kicks in and I haven't found a real cause or solution. I know it's anecdotal, but I've seen this over several clients in different locations and I "know" it doesn't happen with Windows 7 machines OR with standard HDD's. And, there isn't a set timing, other than it does not seem to happen while a user is actively working and engaging...this is good obviously, and would seem to point at a standby mode, BUT a mapped drive can stay solidly mapped and accessible for days before balking.
Additionally, the mapped drives tend to "bake in" over time, and the users obviously stop complaining, and all my hoop-jumping seems to have been for nothing.
-These are manually mapped drives, not group policy maps.
-All Windows Updates, Office updates and firmware/BIOS/chipset driver updates have been performed and are current.
-Power saving properties have been set to maximum wherever possible.
Very frustrating, luckily not mission critical, but I'd love to find a real solution and/or fix. Happy to jump thru a few more hoops if we get on the right track.
thanks
Jarrod
Additionally, the mapped drives tend to "bake in" over time, and the users obviously stop complaining, and all my hoop-jumping seems to have been for nothing.
-These are manually mapped drives, not group policy maps.
-All Windows Updates, Office updates and firmware/BIOS/chipset driver updates have been performed and are current.
-Power saving properties have been set to maximum wherever possible.
Very frustrating, luckily not mission critical, but I'd love to find a real solution and/or fix. Happy to jump thru a few more hoops if we get on the right track.
thanks
Jarrod
Cliff Galiher
If you upgraded to 1809, it is a known bug. You can see it in the current 1809 release notes.
ASKER
should I google 1809?
ASKER
OK, googled. Does 1809 fix it or is it a known issue because of 1809? I've had this issue occur on various machines for 6 months to a year...
Then you have something else going on. This is a new bug in 1809 with no fix yet. 1809 hasn't been out that long.
I'd guess it is an underlying network issuem mapped drives do drop under poor network conditions.
I'd guess it is an underlying network issuem mapped drives do drop under poor network conditions.
We have Domain machines here on V1809 and it tells us network drives did not reconnect but in fact they do connect and so (for us) the big is a visual distraction but does not prevent working
ASKER
Cliff...anything I should do to test the network condition? I'm not saying it's bulletproof, but it's wired with semi-new ethernet, within 4 years. Unmanaged Dell switch with 32 nodes, maybe 25 active at any given time.
As for the disconnext, is Win 10 more sensitive than Win 7 and especially ssd Win 10 machines? I've got 20+ others without an issue, the only ones that had an issue previously are Win10 ssd's...
As for the disconnext, is Win 10 more sensitive than Win 7 and especially ssd Win 10 machines? I've got 20+ others without an issue, the only ones that had an issue previously are Win10 ssd's...
As for the disconnect, is Win 10 more sensitive than Win 7 and especially SSD Win 10 machines?
From my own point of view, I would say no. I have been using Windows 10 at clients and their servers for 3 years now.
Do you have legacy or incompatible Anti Virus / Firewall? After V1607, we have been adopting Windows Defender and Firewall and that is working very well.
From my own point of view, I would say no. I have been using Windows 10 at clients and their servers for 3 years now.
Do you have legacy or incompatible Anti Virus / Firewall? After V1607, we have been adopting Windows Defender and Firewall and that is working very well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks "Hecgo" my user computer wasn't available for troubleshooting over the holiday, so I will check back in with him this week. All I've heard is that the problem is still present.
Does this ring any bells folks?
-I signed in remotely at 7am, and the drive and access was normal and solid, fast even. User reports that the mapped drive was functioning when he sat down this morning, but after 30 mins he received the message error again " There has been a network or file permission error." I'm trying to gather even more info from him about the specific file he's working on, if the more sensitive Timeslips program is affected by this, etc.
I was a bit surprised by this behavior, because to the best of my knowledge, other users who have experienced this were solid once the drive was engaged and it was long pause/overnight type of thing when mapped drive was lost. Not sure if the timing makes a big diff, but wanted to share, just in case.
Does this ring any bells folks?
-I signed in remotely at 7am, and the drive and access was normal and solid, fast even. User reports that the mapped drive was functioning when he sat down this morning, but after 30 mins he received the message error again " There has been a network or file permission error." I'm trying to gather even more info from him about the specific file he's working on, if the more sensitive Timeslips program is affected by this, etc.
I was a bit surprised by this behavior, because to the best of my knowledge, other users who have experienced this were solid once the drive was engaged and it was long pause/overnight type of thing when mapped drive was lost. Not sure if the timing makes a big diff, but wanted to share, just in case.