Unable to copy from shared folder since Guest Add. 4.12.12

[Moracle]

I'have just installed the new VirtualBox 4.12.12 and the corresponding Windows 7 Guest Addition on my Virtual machine (Win 7 64 on host and on guest). But since this installation I am not able to copy files from the host shared folder to the guest. I always get the following message: "X:/ refers a location that is anavailable". ??? What is the problem ? I can browse the shared folder but not copy from it ! It was working fine prior to this upgrade.

[mpack]

"X:/" is not a valid Windows path. "X:\" would be valid, provided it exists. Does it? Note that ability to browse into a network folder does not prove that a drive letter mapping has been done correctly.

[Moracle]

"X:/" is not a valid Windows path. "X:\" would be valid, provided it exists. Does it? Note that ability to browse into a network folder does not prove that a drive letter mapping has been done correctly.

Oh I simply mistyped. I should have written X:\ of course.

Actually the Windows explorer displays the following explored path: "Computer > VMShared (\\vboxsrv) (F:)" where I can browse the shared folder content. But when I try to copy something...huh... I get the error message.

[mpack]

F: ? I thought the drive letter was X: ?

I think it's time you posted a picture of the error dialog. A PNG attachment should do nicely, not too big please.

[Moracle]

F: ? I thought the drive letter was X: ?

Do we really care the actual drive letter ?

I said "X:" as a litteral representing any drive letter.

Here is the error message window and the Windows Explorer window showing the source /dcu folder I tried to copy from the VMShared folder.

(The problem is the same if I try to copy a folder named differtly than "/dcu"... )

[noteirak]

Did you try to remove then readd the mapping? Possibly under another letter?

[Moracle]

?????

Do not ask me why but the fact is that today the VMshared drive is fully available !...

However I tried yesterday to reboot host and guest without solving the issue...

Maybe was it due to the USB key inserted yesterday and mapped as drive E:\

Today I didn't inserted it and the VMShared drive is no more mapped as F:\ but as E:\...

But I also got problems yesterday before inserting the USB key while the VMShared drive was E:\...

So, the mystery remains unsolved... But I'm now able to fully access my VMShared drive...

I remember having had the same problem the last time I upgraded my VirtualBox... I might have done something wrong...

Sorry for the disturbation.