VirtualBox 4.1.8 kills NTFS junctions?

[wmb]

I run a laptop with an SSD + HDD configuration, where my Windows user profile is symlinked from the SSD to the HDD via an NTFS junction point. I just installed 4.1.8 to test out the Windows 8 Beta, and when creating the first VM I received a "Path not found" error. From that point on, almost everything in my session is hosed (no links work, services are all asking me to sign in).

I did a system restore, but my profile was still broken (Windows logged me in with a "new" profile).

I noticed that my junction point was gone (the SSD now had a real folder with only the VirtualBox files).

When I deleted that profile on the SSD and recreated the junction, my machine is back to normal.

Is it expected that VBox should blow away junctions like this?

[Frank Mehnert]

Of course that is not expected behavior. VirtualBox does not delete any files, directories, links or junctions which it is not responsible for. Otherwise this would be a bug. But more information is required, for instance, the name of the junction point(s), source / destination. And from your description it looks like you are talking about the Windows host, is that correct?

[wmb]

Yes, the host is Windows 7 x64. The guest was supposed to be Windows 8 Beta x64, but it obviously didn't get that far.

My system is set up with an SSD as the system drive (C) and a HDD as an additional non-system drive (F). The link is created thus:

mklink /J C:\Users\me F:\Users\me

I've been running fine this way for many months. After trying to create the VM, the link was gone.

[aeichner]

Please reopen if this is still a problem with a recent VirtualBox release.