WARNING: As of the Windows 8.1 Preview if you set a drive mapping to “Remove” or “Replace” it will forcefully disconnect the drive and close any open files you have to that location. That one explains the background update principle and concludes with this: New Background Drive Mappings in Windows 8.1 There are several posts about the same issue under Windows 8.1, for example: In the Group Policy Object (GPO) where drive maps are defined, edit User Configuration > Preferences > Windows Settings > Drive Maps. The solution? Change the group policy to Update rather than Replace the drive mapping. As of Windows 8.1, the group policy refresh happens not only at logon but periodically in the background while users are working. It turns out that if drives are mapped in group policy and the policy specifies Replace, the drive will disconnect and then reconnect every time group policy is refreshed. Finally I found this article:įollowing Windows 10 upgrade, mapped drives disconnect briefly One 2010 article talked about disabling SMB2 to solve app crashes, but you’d think SMB2 would be working by now. So something is wrong with the 2012 R2 Essentials server? Then I realized that other Windows 10 machines on the network were having the same problem. I was wondering if I needed to go back to Windows 7. The outages were very brief: I could immediately connect to the location again. If I had File Explorer open, it loses its location:
One of my database programs relies on a mapped drive and keeps crashing. The most frustrating problem has been that mapped drives on my server frequently disconnect. A few weeks ago, I upgraded from Windows 7 Ultimate to Windows 10 Pro.
0 kommentar(er)
