WinFsb does not work for me on Win11
Bill Zissimopoulos
From your diag output it looks like the service is properly installed.
At the same time it shows that the WinFsp driver was never started and it is not clear why. Can you please do the following from the command line:
- Change into the WinFsp bin directory (e.g. C:\Program Files (x86)\WinFsp\bin)
- Run the command `memfs-x64.exe -m X:` and report the output.
Bill
--
You received this message because you are subscribed to the Google Groups "WinFsp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
winfsp+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/winfsp/0f3413e6-e96c-48df-8b35-75a2e1328749n%40googlegroups.com.
Moros Lantia
Hello Bill,
Do have the memfs-x64.exe i needed to install the Developer tools
as well (which are not installed by default)
Running: ".\memfs-x64.exe -m X:" gives
memfs -t -1 -n 1024 -s 16777216 -m X:
The service memfs has been started.
... and waits ...
diag.txt attached, Drivers seems to be started and memfs is provided ...
After this was done, also doing "net use Z: \\memfs64\test"
works ...
... rebooted ...
Now 'net use Z: \\memfs64\test' still works after reboot -> it seems adding 'Developer' has changed something in the system
Unfortunately sshfs still does not work, SSHFS-Win Manager shows:
--------------------------------------------------------------------------------
date: 2023-02-28T13:05:47.435Z
conn: {9aed73fa-f1a5-4791-be11-4b3233d31cdd} (PiTouch)
conntype: password-ask
cmd: "C:\Program Files\SSHFS-Win\bin\sshfs.exe" p...@192.168.2.110:/
D: -p22 -ovolname=PiTouch -odebug -ologlevel=debug1
-oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null
-oidmap=user -ouid=-1 -ogid=-1 -oumask=000 -ocreate_umask=000
-omax_readahead=1GB -oallow_other -olarge_read -okernel_cache
-ofollow_symlinks -oPreferredAuthentications=password
-opassword_stdin
{9aed73fa-f1a5-4791-be11-4b3233d31cdd} stderr: cygfuse:
initialization failed: winfsp-x64.dll not found
{9aed73fa-f1a5-4791-be11-4b3233d31cdd} exit: 1
Br, Moros
Moros Lantia
Hello again,
after replacing the winfsp-x64.dll file in 'C:\Program Files\SSHFS-Win\bin' with the one from 'C:\Program Files (x86)\WinFsp\bin' this works as well ...
If you want me to try something, let me know. Happy to help.
Br, Moros
Bill Zissimopoulos
The MEMFS file system is part of the “developer tools”. This explains why `net use` was not working earlier and it is working now after you installed the “developer tools”.
Regarding sshfs-win and SSHFS-Win Manager: this may be a problem with SSHFS-Win Manager as I have had some other reports about this problem. Does sshfs-win work on its own? Try mapping a network drive to \\sshfs\p...@192.168.2.110
Bill
1. Change into the WinFsp bin directory (e.g. C:\Program Files (x86)\WinFsp\bin)
2. Run the command `memfs-x64.exe -m X:` and report the output.
Bill Zissimopoulos
Interesting. There should not be a winfsp-x64.dll file in the C:\Program Files\SSHFS-Win\bin directory.
Bill
From: Moros Lantia <moros....@gmail.com>
Sent: Tuesday, February 28, 2023 1:18 PM
To: Bill Zissimopoulos <bill...@navimatics.com>; WinFsp <win...@googlegroups.com>
1. Change into the WinFsp bin directory (e.g. C:\Program Files (x86)\WinFsp\bin)
2. Run the command `memfs-x64.exe -m X:` and report the output.