[laumars]

There is a Windows-native SSHFS client[1]. I have it installed on a Win10 VM so can confirm it "works" albeit I haven't needed to use it for anything so cannot confirm how well it works.

[1] https://github.com/Foreveryone-cz/win-sshfs I think is the currently maintained version but you're welcome to confirm that independently.

[noen]

I helped resurrect this to support Windows 10 a year or so ago. It works, but because of its reliance on Dokany (a FUSE-like usermode file system library), there are a lot of ways it still doesn't work perfectly.

It was a lifesaver for me when I was doing development on embedded Linux devices (Pi/Edison et al). But if you're not tied to remote hardware, WSL is an infinitely better, faster, much more reliable dev process.

The biggest issue I ran into with win-sshfs was its tendency to bodge git repo status if you maintained the repo on the mapped folder.

[Rondom]

What do you mean by "bodge git repo status"? One thing I noticed is that, git gets confused if you clone under Linux and then try to access it via win-sshfs from Windows. The other way it works fine, i.e. clone from Windows, then other actions work fine on both sides.

[NelsonMinar]

Any idea if filesystems mounted with that SSHFS client are now visible under WSL? They weren't in the original WSL release and I'm guessing aren't under the recent Creators Update release. But maybe they are with this new DrvFs?

[noen]

Yes, they should be. They are (under the covers) mounted as network shares, so they should now appear with DrvFs.

[abhirag]

Yes SSHFS support would be great, till then WinSCP(https://winscp.net/eng/download.php) helps reduce my troubles a bit.