Hi All second time i experince this at work. A user tries to create a network drive but it fails saying the drive is allready in use bla bla bla.. system error 85.. I have tried the net use command with the /delete opton no luck... I have looked through regedit - no luck.. can't you remove any knowledge of a network drive windows 7 might have through Regedit? /Casper "If you never ask you may never learn"

Yes you can, although it would be best to troubleshoot as to why the drive is not properly disconnected. But if you want to remove it through regedit you can have a look at this value: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 And delete the key relating to the error, then restart the computer and you should be able to add the network drive. Let me know if that works for you.

1. I have met with this error message in previous versions of Windows http://support.microsoft.com/kb/308337 2. Try to use mapping with parameters: a. Use net use /persistent:noin the logon script. b. Add "net use * /d" command line in the top of the logon script so that the script will clean the all old mapping first. 3. Instead of mapping I use simple script that opens Windows Explorer (WE). I do what is needed, close the WE and the connection is "destroyed" without any trace: explorer.exe \\server\share\folder Regards Milos

Hi guys, Thanks for the answers... !! I currently explorering your suggestions and will return with what we find... Milos Puchta, Thats a very interresting way to "make" network drives.. Im talking about the explorer.exe \\server\share\folder thing. Are you using this yourself or do you have it implementet in a user enviroment? I very interestet in knowing how you implement this to your users if you do that. /Casper"If you never ask you may never learn"

Hi, Firstly, please let us know how your user mapped a drive. Secondly, based on my research this error message occurs if you map a network drive to the first available drive letter after the drive letters for the local volumes and CD-ROM drives. When you install a new device or volume, Mount Manager, which assigns drive letters to volumes, does not recognize the mapped network drive and assigns the next available drive letter to the new device or volume. This causes a collision with the existing mapped network drive. To prevent this issue from occurring, when you map a network drive, assign the highest available drive letter to the mapped network drive. You also can refer to System error 85 has occurred. The local device name is already in use (net use). Hope this helps. If a post solved your problem, click Mark as Answer on the post. If a post helped you, click "Vote As Helpful" on the left side of post.

Hi Jeramy, The user has found a new way of dealing with the problem by useing a different drive letter. In our case we tried to map the network drive using the CMD command "Net use Z: \\lalalal" It works if he uses another letter. That should answer you questions.. but since the user has found is own workaround the case has been closed... any suggestion would be appriciated but i don't know how well i can test it since i don't have a PC to test it anymore :) stupid company politiks.. thanks for you valid attemtps.."If you never ask you may never learn"