Bill Zissimopoulos

FYI @CFSworks

Thanks for the report. The `diag.bat` output shows that the WinFsp driver cannot be started which is rather weird. The relevant output is: ``` SERVICE_NAME: WinFsp TYPE : 2 FILE_SYSTEM_DRIVER...

I believe I have heard Malwarebytes causing problems for WinFsp before, although I cannot remember the specifics.

@haovic do you also have Malwarebytes installed?

This is currently disabled for FUSE file systems. Native file systems can support WSL1 if they so choose. The reason is that there is a mismatch of how WSL1 encodes...

@r2evans which file system are you using? Is it FUSE based?

@r2evans unfortunately I can only help with file systems that ship with WinFsp. Bitvise's file system may simply not enable WSL support (I do not know). Non-FUSE WinFsp file systems...

If this fails with MEMFS then this is certainly a WinFsp problem. MEMFS works (or used to work) with WSL1, but perhaps this is no longer the case with WSL2....

Does this work when mapping the drive directly from Explorer using the syntax `\\sshfs\USER@SERVER` and not using SSHFS-Win Manager?

If I understand your scenario correctly, you are trying to create a relative symbolic link that points outside the file system. I believe that this is not allowed on Windows,...