Open roman-orekhov opened 3 years ago
Awesome - was banging my head on this for a while and this fixed it. It was weird because even reinstalling (which briefly flashed a message about starting the service) didn't do it. Manually starting the service fixed the issue though.
I've had good success (last 4-5 restarts) with WinFsp.Launcher in delayed start. I haven't had to manually start the service since doing that.
Cool, I'll have to try that. I did notice today that after (probably) a suspend I had lost connectivity to my drive but the service was still running. But I think this is due to the fact I need 2 factor auth to connect. Restarting the service triggered a push notification via Duo that I was able to approve and regain access.
This fixed it for me too! Thank you for sharing! 😄
I've had good success (last 4-5 restarts) with WinFsp.Launcher in delayed start. I haven't had to manually start the service since doing that.
This seemed to help me too, thanks.
So I installed sshfs-win-3.7.21011-x64.msi and winfsp-1.9.21096.msi according to README.md. I was able to mount a drive via Windows Explorer, access it however I wanted. Then I needed to reboot PC, install some NVIDIA drivers, etc. After the reboot I couldn't access the drive anymore. I ran Network diagnostic (Microsoft helper) and it couldn't find "sshfs.r". I thought some service wasn't working. So I went to services, and saw WinFsp.Launcher service was set to Automatic, but wasn't running. I ran it manually and then I was able to access my remote drive again.
I think this deserves to be either fixed or documented.