System Error 67 Windows 11 25h2

[SushiTee]

I'm using SSH-FS like this to mount the corresponding home directory.

\\sshfs.k\user@ip-address

It was working fine until last week I believe and it suddenly stopped working. I only get System error 67 when trying to add a network share like this:

net use L: \\sshfs.k\user@ip-address

I have old connections still in my explorer. They are not connected and when I try to connect them I get this error:

It says: Error reconnecting with M: .... Windows File System Proxy: The network does not exist or is not started. The connection was not restored.

Is there some service which must run and that I could check? I don't use any other proxies.

[KannaKG24]

I have the exact same issue, banging my head against a wall rn

[igud]

I get the same behavior. This have been working for years, until recently. I can't say for sure what changes occured when it stopped to work.

net use X: \\sshfs\user@ip-adress\folder
System error 67 has occurred.

The network name cannot be found.

Old mapping in Explorer

No network activity in wireshark when I tried to connect to the host.

Edition: Windows 11 Enterprise
Version: 25H2
OS build: 26200.7171

[konstantintuev]

For some reason the root sshfs works for me but not the sshfs.kr or sshfs.r.
At this point I just scheduled a task for manually running the service with the drive mounted:

1. Create ssh config for your sftp:

• code $env:USERPROFILE\.ssh\config
• config contents:

Host named-sshfs
   HostName host.name
   User root
   IdentityFile userdir\.ssh\id_ed25519
   IdentitiesOnly yes

2. Create a clean ps1 script:
   mount-sshfs.ps1 in the root of user directory

$ErrorActionPreference = "SilentlyContinue"

$sshfs  = "C:\Program Files\SSHFS-Win\bin\sshfs-win.exe"
$prefix = "\sshfs.kr\server@named-sshfs\"
$drive  = "Y:"

# If drive already exists, do nothing
if (Test-Path $drive) { exit 0 }

# Remove any stale mapping
cmd /c "net use $drive /delete /y" | Out-Null

# Start in background (no terminal held open)
Start-Process -FilePath $sshfs `
  -ArgumentList @("svc", $prefix, $drive) `
  -WindowStyle Hidden

3. Create a task:

sudo schtasks /Create /F /TN "Mount Named SSHFS" `
  /SC ONLOGON `
  /TR "powershell.exe -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -File userdir\mount-sshfs.ps1"

4. Test the task:

schtasks /Run /TN "Mount Named SSHFS"

5. Done - you should have a mounted SSHFS

[easpeagle]

Yeah... I'm hitting this exact same issue. It's not even trying to do anything on the network. This is bizarre.

[cytoph]

Same here, it's still a problem.

@konstantintuev I think I did everything like you described but still doesn't help.

[LiuMenglii]

Try putting the private key in the ~/.ssh directory. sshfs-win can't parse the IdentityFile option correctly.

[vico93]

Solution: #155 (comment)