is unavailable if the location is on this pc expandrive

#IS UNAVAILABLE IF THE LOCATION IS ON THIS PC EXPANDRIVE PLUS#
#IS UNAVAILABLE IF THE LOCATION IS ON THIS PC EXPANDRIVE WINDOWS#

The normal way by just disconnecting in win explorer. Not only did the drive have write-access, but now I could delete the mapping in What finally worked was, especially under my 20/20 hindsight vision, very simple: first re-mapping the offending driveletter to a different share, then to the right share again. I tried most of the above tricks - to no avail. This SEEMED to work, but in fact, access was still read-only! Then - here it gets hairy - I tried mapping to that share using a different driveletter: the mapping was read-only! Suspecting that somehow first completely deleting the driveletter was essential, (By the way: if this is just an explorer issue, then how come the drive doesn't exist in a cmd-window?) Then I tried to just re-map the driveletter, this time using the user's own credentials, without first disconnecting. So i tried to delete it, but ran into the situation more-or-less as described here: in explorer, drive has red cross in the registry, drive is not to be found under 'net use', drive is not listed in aĬmd-window, drive does not exist. When the oversight had been corrected (the user now had read/writeĪccess to the share) I wanted to re-do the mapping. So I made a mapping using different user-credentials, which at least provided the user with reading-rights. This is why:Ī user (win8.1) did not have, through an oversight, the rights to a certain share. It's a fix preventing the issue from reoccuring that we need, not yet another time consuming method for repairing Explorer after it starts displaying false information.)

(And please no more suggestions for workarounds.

#IS UNAVAILABLE IF THE LOCATION IS ON THIS PC EXPANDRIVE PLUS#

(That means fixing the three symptoms of the problem reported by chiptech above, plus the fourth I report here.)

#IS UNAVAILABLE IF THE LOCATION IS ON THIS PC EXPANDRIVE WINDOWS#

Mr Microsoft, how can we officially enter this bug in your bug tracking databases, and make sure that Windows Explorer gets fixed at last? Is really a serious issue, as this can potentially lead to data loss, by misleading the user to copy or erase data on the wrong shares!!! For example, here's a 2006 post that reports exactly the symptoms I'm having today with Windows 8: Īs in that 2006 example, I'm regularly affected by the consequence, where Windows Explorer reports the OLD share name (the one that refused to go away after the drive became disconnected) even after the same drive letter is mapped on a DIFFERENT share. This bug has been in all versions of Windows since at least Windows XP. This is a serious bug in Windows Explorer, and I'm very much surprised that Microsoft failed to address it for so long:Īll workarounds posted here or else where basically work by killing Explorer, or worse still by rebooting Windows.

Is unavailable if the location is on this pc expandrive