Earlier quoted context omitted.
That's okay -- I'm sure they fixed something like that issue! The WSL team has been crazy busy, and their work so far is super impressive. VirtualBox shared folders had their own problems. `npm` wants to create symlinks for commands provided by packages, but VirtualBox doesn't support symlinks by default on Windows shares. So you have to execute an arcane command to enable that feature -- every time you restart the c…
It is possible to create directory symlinks in Windows. It is called junctions [1] [1] https://en.wikipedia.org/wiki/NTFS_junction_point
[EDIT: Also, reading GP, it looks like their issue is something about VirtualBox support for symlinks, not Windows support for symlinks. Symlinks are enabled in Windows by default, so they'd only have to do something special if they were on a domain that disabled them in the group policy--but in that case, they wouldn't be able to turn them back on themselves on a reboot anyway.]