Bankesy Posted April 13, 2018 Posted April 13, 2018 Good afternoon We appear to be experiencing an error whereby users of a particular security group frequently have Windows 10 file explorer crashing when opening files from mapped drives. The security group itself exists as members of that group get a particular mapped drive but they have the issue regardless of which drive they are opening files from. A bit of a strange one that's been driving us mad so if anyone has any suggestions we would appreciate it. Thank you
ShellfishClive Posted April 13, 2018 Posted April 13, 2018 Check if the mapped drive policy isn't conflicting with any other drives that are already mapped, make sure you're not using the same letter twice.
Bankesy Posted April 15, 2018 Author Posted April 15, 2018 Good afternoon Thank you for the suggestion, although all appears to be OK with the policy and the letters your suggestion as at least forced me to look through our drive mappings (there are a lot due to it being a Trust) and I can see one sort of difference in the problematic drive: It's not been shared as hidden ($) like a lot of our other drives and it also has a space in it where a lot of our others do not, for example it is currently: \\servername\share name instead of \\servername\sharename$ Could this be a possible cause? Thank you
ShellfishClive Posted April 15, 2018 Posted April 15, 2018 It "could" be the space, try removing it and see what happens. UNC paths sometimes don't like spaces.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now