https://bugs.winehq.org/show_bug.cgi?id=50804
--- Comment #33 from Zebediah Figura z.figura12@gmail.com --- Do you know exactly what this application is trying to do with the symlink? I.e. it's explicitly reading the target, but what for, what is it trying to do with it?
The idea of hiding unix symlinks completely still makes me nervous. Like I said in bug 50586, it doesn't "definitely work in "all" situations", it breaks GetVolumePathName() which will now always report the symlink, and then subsequent calls to e.g. GetVolumeNameForVolumeMountPoint() will fail.
I don't know, maybe this doesn't affect anything; maybe we can try it in wine-staging for a while. But it feels easier to justify breaking the applications that are actually broken.
It would also be nice to have a way to actually create usable symlinks for "My Documents" etc. from shell32.