Windows 10: Previously mapped network drive now showing as disconnected but is still readable and writable.

I have all my music files on a WD MyCloud drive which is connected to my home network. I previously mapped my M:/ drive to the music folder on my MyCloud drive via it's IP address. Then the IP address of the MyCloud drive changed and the drive showed as disconnected. But the drive's contents are still readable and writable by windows explorer But now I cannot disconnect the drive (This Network Connection Does Not Exist) And the drive no longer appears in the list of mappable drive letters under Map a Network drive. My question is how do I delete this disconnected network drive so I can re-map it again with the correct URL.

:)

 

Windows 10 Drive Mapping showing Disconnected Network Drive

I have a NAS (WD My Cloud) on my home network and I have always added a drive on my networked computers using drive M as their Music drives. But recently My Network drive went down and I had to reinstall all the files on it's replacement drive. I gave
the new network drive4 the same IP address on the network and everything else (All the other drive mappings for my Documents Drive, my Downloads drive, my Pictures drive, etc. Nut my music drive keeps showing Disconnected Network Drive. But now I cannot delete
the drive mapping. It tells me Network drive does not exist. I have tried all of the suggestions from other threads including using Command prompt commands and everything else I have seen but it still shows up as a Disconnected Network drive. I can rename
the drive as Music again and I can always access the drive4 even when it is listed as Disconnected Netowork Drive but I cannot add any more files to it and I cannot manipulate any of the files on the drive. I can listen to the music files through most of my
players but I cannot edit any of the metadata on the files. How do I get my drive fully functional again?

 

Unable to disconnect from mapped network drive

I receive the following error when I try to disconnect from a self mapped network drive: "network connection does not exist"

The network drive icon appears with a bid red x and says it is disconnected, yet I can double click on it to enter the mapped folder. Doing this does not reconnect the folder, and remains disconnected. This causes problems because programs that pointed
to this path are unable to read the files. I am unable to remap this drive because the associated drive letter (E and mapping no longer shows up in the list.

I've tried all the typical suggestions including:

--I tried to do it via the command prompt with the net use delete command, but it can't be found in there.

--Tried to above with the actual network path instead of the drive letter, did not work

--Tried to delete the registry entries from:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

HKEY_USERS\. Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Mountpoint2\

None of these solutions worked. Though deleting the registry entries momentarily hid the disconnected drive, the drive letter was still not available for mapping. I tried to force the drive letter (E to map to my optical drive, which worryingly, pointed
back to the mapped network location on the NAS instead of to the optical drive.

How do I get rid of this? Reformatting the computer is not an option.

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.