none
Mapped drive will not disconnect

    Question

  • I have a computer running Windows 7 Enterprise with a network drive mapped to another commuter running Windows XP Professional. The C drive in the computer with XP went bad and the computer was replaced. However I cannot disconnect the mapped drive.

    If I try to disconnect it using the context menu option in Windows Explorer it brings up a dialog box that says, "This network connection does not exist," and does not disconnect it. I have also tried to disconnect it from the command line:

    C:\>net use Z: /delete
    The network connection could not be found.
    More help is available by typing NET HELPMSG 2250.
    
    C:\>net helpmsg 2250
    The network connection could not be found.
    
    C:\>

    This problem is very annoying. Please help.

    Tuesday, October 11, 2011 12:42 AM

Answers

All replies

  • In cmd windows, you can directly type command 'net use' to see the net connection.

    If the Z: doesn't existed in the list, 'the network connection could not be found' is normal.

    And you can directly define a new network location to Z:.

    Tuesday, October 11, 2011 7:45 AM
  • It still showed up in the list but would not let me disconnect it. However, it replaced it just fine. Thank you.

    • Proposed as answer by Kevin M. Covert Thursday, November 21, 2013 9:58 PM
    Tuesday, October 11, 2011 2:14 PM
  • once you replace you can delete the mapped drive now..
    Regards, h9ck3r.
    Tuesday, October 11, 2011 5:09 PM
  • I was experiencing a similar problem on my computer. The root of the issue is that the drives where initially mapped when explorer.exe was started. As you said, after "disconnecting" them they still appeared in My Computer but not "net use". Restarting explorer.exe at this point removed the drives from My Computer.
    • Proposed as answer by Skills Friday, July 06, 2012 9:44 PM
    Friday, April 13, 2012 1:23 PM
  • That's the ticket! KISS! (Keep It Simple Stupid) I remember this from my Novell instructor. I am definitely going to put this in my HOW TO's Thank you Robert Greer!
    • Edited by Skills Friday, July 06, 2012 9:46 PM
    Friday, July 06, 2012 9:44 PM
  • This worked for me as well. 

    Thanks Robert!

    Monday, July 23, 2012 8:07 PM
  • I've tried both solutions, I've tried remapping the drive (net use Z: \\myServer\myShare\), restarting explorer and the computer. It still shows the disconnected drive and I can't delete it. Anybody else have this issue? Thanks.

    Thursday, March 14, 2013 8:05 PM
  • I have a similar issue on Server 2012, but when net use is run it shows "There are no entries in the list." but shows in Windows Explorer. Restarting Server and explorer.exe does not change anything?!
    Tuesday, April 09, 2013 6:50 AM
  • I have a client running Windows 7 connected to SBS 2011 Essentials. Mapped drives to previous server persist as icons in Windows Explorer and can't be deleted even though I used net use to delete the drive letter mappings. I have been able to map new letters to the shared folders on the new server but can't get rid of the red X icons no matter what I try, including the suggestion to net use the same drive letter and then try and disconnect.

    Any suggestions would be appreciated!

    Thanks. 

    Michael

    Friday, April 26, 2013 5:01 PM
  • I tried all described above, but nothing worked. But somewhere I found that "Net Use /Persistent:yes" would set all current drives to persistent. I tried "Net Use /Persistent:no", booted and that one driveletter was gone at last. May be that will do the trick for you????

    Leo Koolsbergen

     
    • Proposed as answer by rbdsolutions Thursday, May 09, 2013 4:44 AM
    Thursday, May 02, 2013 6:52 AM
  • Microsoft: There are multiple bugs here, at least to the rest of the world.  Please correct them anyway. 

    -> If 'net use' reports no drives, neither should Explorer. 

    -> A refresh in Explorer should remove the disconnected drives, if 'net use x: /delete' alone doesn't do it -- but it should.

    -> The Explorer context menu 'Disconnect' should remove them also.

    Monday, July 15, 2013 5:20 PM
  • It seems by trial and error that the system has to be rebooted, logoff/on or Explorer killed in order to get the icon and drive from showing up on the computer list. This seems a bit illogical.

    A small kill explorer batchfile will fix the issue without logoff/on or reboot like:

    @echo off
    net use * /delete /y
    taskkill /f /IM explorer.exe
    explorer.exe

    Note: substitute your own net use [x]: /delete command for specific mapped drive letters

    • Proposed as answer by TonyVov Saturday, July 27, 2013 1:52 AM
    Saturday, July 27, 2013 1:51 AM
  • I have tried this but no luck - I still see Disconnected Network Drive (V:) in explorer. Also tried a restart and settings /persistent:No and Yes.

    Is there any place I can escalate this to Microsoft and not be charged Pro Support fee for?

    Sunday, July 28, 2013 10:32 PM
  • the batchfile worked great. 

    thanks


    Marcia Henry

    Friday, September 06, 2013 2:14 AM
  • Was having a similiar issue and this little batch file worked like a charm!

    Thanks

    Friday, October 04, 2013 3:25 PM
  • I have the same issue on Win 7. This drive is our home drive from AD.

    The one factor I see is that all other drive mappings show as "Microsoft Windows Network" whereas this one mapping shows as NFS network. Perhaps this has something to do with it.

    I can map the drive as letter Z and it works. It is mapped as drive P and will not allow me to access. System error 85.

    Status       Local     Remote                    Network

    -------------------------------------------------------------------------------
    OK           J:        \\t70nas301\home\jpanik   Microsoft Windows Network
    OK           N:        \\T01FAP01\ISDATA         Microsoft Windows Network
                    P:        \\t70nas301\home\JPANIK   NFS Network
    OK           Q:        \\T70NAS301\PUBLIC\PUBLIC Microsoft Windows Network
    OK           R:        \\T70NAS401\SHARED\SHARED Microsoft Windows Network
    OK           S:        \\T70NAS301\SHARED        Microsoft Windows Network
    OK           Z:        \\t70nas301\home\jpanik   Microsoft Windows Network
    The command completed successfully.

    Thursday, October 31, 2013 7:03 PM
  • ANSWER:
    In HKEY_CURRENT_USER\Network the key for the drive does nto exist.
    Exported one of the other keys for a drive mapping and edited the content to match that of my locked drive.

    [HKEY_CURRENT_USER\Network\P]
    "RemotePath"="\\\\t70nas301\\home\\jpanik"
    "UserName"=dword:00000000
    "ProviderName"="Microsoft Windows Network"
    "ProviderType"=dword:00020000
    "ConnectionType"=dword:00000001
    "DeferFlags"=dword:00000004

    add this to a REG file and merge the data.
    Once this is done, click the drive mapping and the error is that the drive is not available, you can now disconnect the mapping.

    • Proposed as answer by Jimm Panik Thursday, October 31, 2013 7:10 PM
    Thursday, October 31, 2013 7:10 PM
  • Just log-off or restart the system it will go off.
    Wednesday, November 06, 2013 1:17 PM
  • I have found that these "phantom" drive mappings can be removed by using a scheduled task:

    for example open an elevated CMD prompt and type the following:

    If you wish it to run at 13:00 (1:00 PM) and the drive letter to remove is "Z:"

    AT 13:00 NET USE Z: /DELETE /Y

    Open explorer and you will see the drive letter is now removed.


    DOS Vader

    Friday, December 06, 2013 9:14 PM
  • I have found that these "phantom" drive mappings can be removed by using a scheduled task:

    for example open an elevated CMD prompt and type the following:

    If you wish it to run at 13:00 (1:00 PM) and the drive letter to remove is "Z:"

    AT 13:00 NET USE Z: /DELETE /Y

    Open explorer and you will see the drive letter is now removed.


    DOS Vader

    Worked for me as the mapped drive was created using Task Scheduler with user System. Was unable to get rid of the share unless I umount it with a script just as I mounted it (nfs share). +1
    Monday, December 16, 2013 6:46 AM
  • it works! thanks a lot
    Monday, February 03, 2014 11:55 AM
  • The easiest way to fix this problem is to edit the regedit , it so simple.

    open regedit

    Go to HKEY_CURRENT_USER/Network

    Now remove the letter you want in this case X, and restart the computer. issue is fixed.


    Sunday, February 16, 2014 11:20 AM
  • There appear to be a multitude of people with the same issue and a multitude of solutions offered by others.  I tried just about all of them but to no avail, including all the registry changes, net use commands, rebooting, restarting Explorer etc etc.  In the end, the only solution that allowed me to actually disconnect my network drive and remove it from displaying in explorer was the following:  remove the offending PC from the network Domain (ie. join a workgroup), login as a local administrator, then you can disconnect the offending drives.  Then re-register the PC to your Domain as per normal and you will find that the offending drives are gone and you can re-establish your required network mappings.
    Wednesday, March 05, 2014 6:21 AM
  • Thanks DOS Vader - yours was the only method that worked for me. Possibly because in my case the drive letter was mapped to a NAS share?

    Tangata_Manu

    Friday, March 28, 2014 6:28 PM
  • Thanks!  Worked.
    Monday, April 14, 2014 3:04 PM
  • @echo off
    net use * /delete /y
    taskkill /f /IM explorer.exe
    explorer.exe

    Working fine for me, keep mind to run it like administrator

    Alejo

    Tuesday, June 03, 2014 12:54 PM
  • Brilliant, this helped me resolve the issue.
    Tuesday, June 17, 2014 1:45 PM
  • This is a serious bug in Windows Explorer, and I'm very much surprised that Microsoft failed to address it for so long:
    All workarounds posted here or else where basically work by killing Explorer, or worse still by rebooting Windows. This is ridiculous :-(

    This bug has been in all versions of Windows since at least Windows XP. For example, here's a 2006 post that reports exactly the symptoms I'm having today with Windows 8: http://www.pcreview.co.uk/forums/getting-rid-disconnected-network-drives-explorer-t2414089.html

    As 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 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!!!

    Mr Microsoft, how can we officially enter this bug in your bug tracking databases, and make sure that Windows Explorer gets fixed at last?
    (That means fixing the three symptoms of the problem reported by chiptech above, plus the fourth I report here.)
    (And please no more suggestions for workarounds. 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.)

    Jean-François

    Monday, July 07, 2014 10:30 AM