Windows 10: 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.

 

Impossible to remove a persistent network drive mapping when logged on disconnected

Initial situation (tested with Windows 10, 8.1, 7 and XP):

• Create a persistent (!) network drive mapping (a.k.a. "Reconnect at logon") using the integrated/official "Map Network Drive" dialog .
• Now physically disconnect from the network folder (unplug the cable or shut down the target system)
• Log off and on again. A balloon message will tell "Could not reconnect all network drives", but the drive will still be visible in the Explorer (with a red cross). The balloon message is the best indication that you've reproduced the steps correctly.
  

At this point I'd like to remove that network drive using my software.

There are multiple ways to do this.

- Probably the easiest way to reproduce it is by command line: net use X: /delete

- API: WNetCancelConnection2 or WNetDisconnectDialog1

- Disconnect dialog: Explorer main menu > Tools > Disconnect network drive (7/XP) or the submenu "Disconnect network drive" (10/8.1) while no drive is selected when the click is performed

and a couple of others.

All of them result in the problem that the drive letter icon remains in the Explorer although the network drive has been disconnected.

Some details that indicate that this is a bug and not feature:

- Although the drive letter icon is shown in the Explorer it's not visible in any other software and not accessible through Windows API

- The drive letter can be used for a new network drive connection. If done so, the new path is mapped to it, but the old name/path remains in the Explorer.

- The drive letter can be used to be assigned to a local drive in the Disk Management dialog. For example after changing the drive letter of a DVD drive to the disconnected network drive letter the drive is still shown as a network drive in the Explorer
but leads to the content of the DVD drive.

To solve this problem at this point the user has either to log off and on again or kill explorer.exe and run it again. This shows that it's some kind of orphaned drive in some internal Explorer cache or object list that is not removed correctly.

There is one way to remove the drive correctly in the first place:

Right-click on the drive and choose "Disconnect". This works flawlessly! The network drive is disconnected and immediately removed. Notice: this only works if done in the first place. If the drive has already been disconnected using one of the other methods,
this option will only show "This network connection does not exist."

I've discussed this problem with many experts already and there doesn't seem to be a workaround for this. At the moment if you want to programmatically disconnect a persistent network drive that wasn't available during logon you'll end up with an orphaned
drive.

This applies to all Windows versions from XP to 10, x64 and x86. (older versions not tested)

Is there any chance this could be solved by patching Windows?

 

Removed mapped drive no longer showing in drive list for a new mapped drive.

I had a mapped network drive that was showing as disconnected and I tried the CMD (Admin) command mountvol /r which removed the mapped drive but now the drive that was causing the trouble no longer shows up in the list if drives I can mount. How do I get
this drive back?