Bill Zissimopoulos

Make sure that your symlinks do not have any trailing slashes (i.e. point to `/foo` and not `/foo/`). There is a long-standing bug about this, that I will have fixed...

Unfortunately it is not possible to have symlinks that point to an alternative drive using SSHFS-Win. This is because of a conflict of how symlinks work on POSIX/FUSE vs Windows....

@wonx the problem is really on Windows. Windows needs to understand a symlink for many reasons (e.g. when you open a file via a symlink) and it does not understand...

@Chicken-Bones I am not sure what you are asking for.

How are you using SSHFS-Win exactly? It looks like you are mounting the file systems as directories rather than drives.

What I found surprising is that you have directories C·, D·, E·. These look suspiciously like the drives `C:`, `D:`, `E:`, with the colon (`:`) converted to a Unicode character...

@roa-nyx this may well have to do something with the path separator character. I recall there is an open issue in WinFsp about this.

The issue is actually in sshfs-win. See #126. I am going to make this into a WinFsp issue to make sure I look into it. EDIT: I have transferred the...

Please check whether you have any user mode crash dumps (usually found in `C:\Users\USER\AppData\Local`) or any Cygwin stack dumps (likely found in `\Program Files\SSHFS-Win`). Also try the latest [SSHFS-Win beta](https://github.com/billziss-gh/sshfs-win/releases),...

Curious that you do not have any dumps if the app crashes. See here for [collecting User-Mode Dumps](https://docs.microsoft.com/en-us/windows/desktop/wer/collecting-user-mode-dumps) on Windows. Cygwin also creates a "stackdump" file when a Cygwin app...