Problems with mapped drive

I have a mapped drive in Windows 10 that works when doing anything within the drive itself, viewing, editing, deleting etc. But when I try and copy to or from the mapped drive I get and error.



The mapped disk is on an old legacy box running XP that we are trying to move away from. When trying to copy a file first Windows 10 prompt for admin permission, then displays the copy dialog and then the error pops up.

The error message itself it very misleading stating the drive is unavailable when actually I can access it without any problem through Explorer.

I've tried disabling the UAC in Windows 10 but didn't help, also un-mapped and re-mapped the drive, booted but no luck.

Any help would be appreciated. Thanks

Tmckinsey said:

The mapped disk is on an old legacy box running XP that we are trying to move away from. When trying to copy a file first Windows 10 prompt for admin permission, then displays the copy dialog and then the error pops up.

If you primary goal is to copy data from one computer to another over the network then why not just give up from legacy home network?, because it is known to have issues even on 2 Windows 10 machines.

My recommendation is to use RDP because of stable connection, although I don't know what possible issues there could be.

I personally use this approach to backup data to another PC and is serving me well without issues.

Yes and it appears to accept the credentials without any issue.

The XP box is named XP07 which is the name used when mapping the disk and again when using Windows 10 Explorer everything is accessible within the mapped drive itself, only the coping of file to or from the drive fails. However when using Explorer to navigate down to Network & XP07, (not using the mapped drive letter) I'm able to copy files just fine.

if you want to continue troubleshooting this problem start with event viewer.

Following link may help to locate relevant events:
networking - Find events for connections to a shared drive in the Windows Event Log - Super User

You can share your findings here, maybe someone could have a hint.

If you want to make locating event faster and more reliable I recommend you to clear event log completely and soon after reproduce the problem then go ahead and see event log.

Following will help to clear logs in one shot:
Clear All Event Logs in Event Viewer in Windows

To open event viewer:
Windows key + R -> eventvwr.msc -> Enter

zebal - Unfortunately things get a little more involve then just copying files.

We are taking the approach of moving away from our legacy systems one step at a time, and through that process we are making sure everything works. This involves executing many different batch files to copy and rebuild a ton of code, installing / registering dll's and well it all gets rather involved.

The procedures to build / install the legacy systems are mostly automated through batch files and we've found many issues when trying to get them to work under Windows 10. We have had to modify the batch files as we discovery incompatibility issues between XP and Windows 10. So this is going to take some time with many different iterations of chasing bugs before we even reach a point where the legacy system can be tested on Windows 10.

- - - Updated - - -

zebal - Thanks, I'm going to do just that, clear the events and attempt the copy. It will be interesting to see if the log files have more detail information about what's going on.

hm, if you can't reproduce the issue by simple copying with mouse from one folder to mapped drive (no batch or script files) then you guys should revisit your commands.

example robocopy is known to have issues in specific cases, and like @Samuria said, permissions problems are very likely if you try to copy system files or files with restricted file system permissions.

Samuria - That's the first thing I thought but Explorer has no problem when copying files using the Networked file path of '\\XP07\...' it only has a problem when using the mapped path which is set to drive letter "G:" which is also pointed to '\\XP07\...'

So I don't understand, the drive in question is accessible in Windows 10 under two different formats / paths, the Network notation and the mapped notation, one works and the other doesn't. One would think that if one works the other should as well.

- - - Updated - - -

zebal - sorry for any confusion there, the copy fails using both Explorer and within Batch files.

What I was trying to explain is that Explorer fails when using the mapped path 'G:\\XP07\...' but works when using the network path of just '\\XP07\...'

Explorer fails when using the mapped path 'G:\\XP07\...' but works when using the network path of just '\\XP07\...'

I'm pretty much sure 'G:\\XP07\...' is not a valid syntax for a mapped location.

EDIT:
See here for more information:
https://docs.microsoft.com/en-us/win.../naming-a-file