Windows 10 Home and sshfs

[David Christensen]

On 4/23/25 23:50, Mark Geisert via Cygwin wrote:
> If you haven't tried running sshfs from an elevated shell, try that.
> Other than this, no further ideas yet.
> 
> ..mark


Thank you for the follow-up.


My previous posts appear to be incomplete because I was logging in via 
SSH from Debian GNU/Linux.


If I login as an Administrative user "admin" at the Windows 10 Home 
console and run Cygwin64 Terminal normally (without privilege escalation):

2025-04-24 14:22:17 admin@dq67sw ~
$ strace sshfs dpchrist@samba:/var/local/samba/dpchrist /samba/dpchrist
--- Process 9496 created
--- Process 9496 loaded C:\Windows\System32\ntdll.dll at 00007ffd99b10000
--- Process 9496 loaded C:\Windows\System32\kernel32.dll at 00007ffd97e60000
--- Process 9496 loaded C:\Windows\System32\KernelBase.dll at 
00007ffd973e0000
--- Process 9496 thread 9504 created
--- Process 9496 thread 9508 created
--- Process 9496 thread 9512 created
--- Process 9496 loaded C:\cygwin64\bin\cygwin1.dll at 00007ffd8cb10000
--- Process 9496 loaded C:\cygwin64\bin\cygfuse-3.2.dll at 000000044e0a0000
--- Process 9496 loaded C:\cygwin64\bin\cygglib-2.0-0.dll at 
0000000507860000
--- Process 9496 loaded C:\cygwin64\bin\cygiconv-2.dll at 00000003ff660000
--- Process 9496 loaded C:\cygwin64\bin\cygintl-8.dll at 00000005ee2d0000
--- Process 9496 loaded C:\cygwin64\bin\cyggcc_s-seh-1.dll at 
000000050caa0000
--- Process 9496 loaded C:\cygwin64\bin\cygpcre2-8-0.dll at 0000000453a70000


The terminal command pauses and a pop-up dialog window is displayed. 
This pop-up dialog window was not visible from Debian over SSH in my 
previous posts:

sshfs.exe - Entry Point Not Found

The procedure entry point cygfuse_report could not be located in the
dynamic link library C:\cygwin64\bin\sshfs.exe.


After a timeout, the following two lines appear in the terminal:

--- Process 9496 thread 9508 exited with status 0x0
--- Process 9496 thread 9504 exited with status 0x0


After clicking "OK" in the dialog, the dialog closes and the terminal 
command finishes:

--- Process 9496, exception c0000139 at 0000000000000000
--- Process 9496 thread 9512 exited with status 0xc0000139
--- Process 9496 exited with status 0xc0000139


2025-04-24 14:25:18 admin@dq67sw ~
$


The above sequence is reproducible both without privilege escalation and 
with privilege escalation ("Run as administrator").


David