VirtualBox 5.0.14
Host: Windows 8.1 Pro X64
Guest: Windows 10 Pro X64
I use a symbolic junction in a number of my VMs so they reference the same folder from their C: drives:
MKDIR /D C:\FolderName S:\FolderName
Where S: is mapped to a share on the host.
I have no problems with this when the guest is Windows 7 Ultimate X64. But when the guest is Windows 10 Pro X64 strange things happen.
If I right click on the folder (via the symbolic link) and create a .txt file and then try to rename it to a .csv file I get the warning about changing a file type and then a message that the file is too large for the destination file system.
I have exactly the same setup in a Windows 7 Ultimate x64 VM with no problems. What is going on?
I have confirmed that it is a VirtualBox problem. I tried the same thing from a real machine running Windows 10 Pro x64. I can change the file type and just get the warning about changing the file type but the file type is changed and I don't get the File Is Too Large error.
If anyone is running a Windows 10 Pro x64 VM on a Windows 8.1 Pro x64 host please try to reproduce the problem as follows:
In the Windows 10 Pro x64 VM map a drive (i.e. S) to a share on the host. Create a new folder (i.e. FolderName)
Open an administrative command window in C:\
Then issue: MKLINK /D C:\FolderName S:\FolderName
Close the command window
Open Explorer and double click on C:\FolderName
Right click in the folder and select New \ Text File. Change the file type from .txt to .csv
Let me know if you see the same File Too Large message.
Edit: Removed references to Access 2010
Edit: Add confirmation that it is a VirtualBox problem