Windows Network Mapping Disk does not work

[Ainray]

My host is Debian Stretch, and have two guests are "win10" and "winxp" which suffer the same problem.

I cannot install software by double clicking it in the mapped network disk, although the mapping disk can be automatically mounted and accessed from guest in explorer.

I must copy the software from the mapped disk to guest "C" disk (Yes, it allows copy often, while "copy" maybe also do not work， then I must copy the software from the share folder in "\\vboxsvr" space)

Now i can install software in guest "C" disk.

I would like provide another bug (which maybe not the virtualbox, but i think it also consistent with the problem above). Everything can not index the mapped network disk, which can index the guest "C" disk.

All of these likely problems do throw mud at virtualbox.

Does anybody suffer from the same problem with me? How to get around with it . I cannot get any information about this.

[socratis]

All of these likely problems do throw mud at virtualbox.

Or at Windows? Because that's a known problem in the networked folders in Windows.

Explanation
When a user connects to a network share, Windows tries to connect with two sets of credentials. This fails due to the UAC control. It is so by design. For references and further reading on previous reports and the reasoning behind it (read especially the Microsoft links):

• https://www.google.gr/search?q=the+spec ... ualbox.org
• viewtopic.php?f=7&t=48570
• viewtopic.php?f=7&t=40036
• https://www.virtualbox.org/ticket/5732
• https://support.microsoft.com/en-us/kb/303308
• https://support.microsoft.com/en-us/kb/2019185

PS. I answered to your post before noticing that it's a duplicate. The duplicate post has been removed.