Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Win11 update breakage #382

Open
dmolirl opened this issue Mar 18, 2023 · 2 comments
Open

Win11 update breakage #382

dmolirl opened this issue Mar 18, 2023 · 2 comments

Comments

@dmolirl
Copy link

dmolirl commented Mar 18, 2023

HI, I've been using sshfs-win for months now without problems to connect to a home Ubunto server. A recent Win 11 upgrade seems to have broken something.
UNC path is no longer working - I get a 0x800704b3 error
CMD line fails with:
sshfs.exe [email protected]:/home/user/Obsidian z:
0 [main] sshfs 842 dofork: child -1 - forked process 10680 died unexpectedly, retry 0, exit code 0xC0000142, errno 11
failed to fork: Resource temporarily unavailable
The remote Ubuntu server sshfs is working fine from other hosts.
My win11 desktop does not send a single tcp packet.
I've tried uninstalling and reinstalling different versions of sshfs and winfsp.
Windows 11 Education 22H2
Microsoft Windows [Version 10.0.22621.1413]

sshfs.exe -V
SSHFS version 3.7.1
FUSE library version 3.2

fsptool-x64.exe ver
2.0 (SxS=20230318T113411Z)

@Zirpoo
Copy link

Zirpoo commented Apr 12, 2023

Hey, just as a heads up I also made an issue regarding sshfs not working when upgrading to Windows 11 over an Ubuntu home server.
Altough it seems our problems are different, I found a temporary fix even if this tool doesn't work completely.
here -> #387

Maybe this could at least help you a little :)

@dmolirl
Copy link
Author

dmolirl commented Apr 12, 2023

Hi @Zirpoo ,
Thanks for your reply. In #387 where I see you have success changing your private key. It is different in my case.

sshfs was working with a private key for months until it suddently stopped working with the above error. When I do a wireshark capture, not one packet leaves my client so the problem is here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants