System error 67 or "cannot access" when trying to mount \\sshfs\something about sshfs-win

[SzieberthAdam]

Same here on Win 10, WinFsp 1.4.19049, SSHFS-Win 2.7.17334.

[Feriman22]

I had same issue, it solved after reboot my PC.

[wuyihung]

Same on Win 10 1909, WinFsp 2020.2 (1.8.20304), and SSHFS-Win 2021 (x64) (3.5.20357)

[billziss-gh]

I believe the share that you use should be \\sshfs\[email protected]\var\www\mydir. Notice the lack of a colon and the use of backslashes.

Presumably you want to access your system's /var directory. People have reported success in accessing root directories by using a double backslash: \\sshfs\[email protected]\\var\www\mydir

[omnichronous]

Unfortunately both of these also lead to the same errors.

One thing I noticed is that when I map the filesystem to a local folder with sshfs [email protected]:/var/www/mydir C:\mydir its subdirectories appear in C:\mydir, but when I try to open any of them I get this error:

[billziss-gh]

I can confirm that the problem described in the OP is a problem on Win7. Unfortunately I do not have a solution.

The problem appears to be that the launcher service (WinFsp.Launcher) is unable to launch the SSHFS-Win file system. This is because the CreateProcessW Windows API fails with ERROR_NO_SYSTEM_RESOURCES when launched with EXTENDED_STARTUPINFO_PRESENT. This special invocation of CreateProcess is used when launching a file system that requires credentials. Normal invocations of CreateProcess work.

This failure is specific to Windows 7 and does not happen on Win8+. This leads me to believe that it may be a Win7 bug and that we will need a workaround within WinFsp for this OS.

[omnichronous]

I appreciate you looking into this. Lucky for me my sysadmin set me up with Samba shares in the meantime.

[Shaddoh]

I am having the same issues on win 7 machines. Just chiming in so I am on the thread and get notified if you find a work around.

I have found this works but does not persist on boot

Open a command prompt.
cd C:\Program Files (x86)\SSHFS-Win\bin
set CYGFUSE=WinFsp
set PATH=C:\Program Files (x86)\SSHFS-Win\bin
sshfs.exe -f -o idmap=user user@server: z:
Gives a RSA authentification error, buit lets you say yes or no to connect.
After this it says service has started and you type in password.

[billziss-gh]

Commit winfsp/winfsp@b2e4746 should fix this.

This commit works around the CreateProcessW problem on Win7. Since this is an important problem that makes SSHFS-Win unusable for most on Win7, I am planning to release an update to WinFsp 2017.2 that will include this fix soon.

[billziss-gh]

The latest WinFsp release is out and should fix this problem. Please try it and let me know.

[abaheti95]

I am on a windows 10 device using latest version and I can ping the server but sshfs is not working. On the other hand I am able to connect using SFTP which is weird.

[aparico]

I had a similar problem too (Windows 10, winfsp-1.10.22006, sshfs-win-3.7.21011-x64).
I used this repo and another one and it worked!