Winfsp x64 dll что это
Topic says it..following the gif on the main page, I get an "Error code: 0x800704b3". Do I need to reboot the windows machine after install? Thanks.
The text was updated successfully, but these errors were encountered:
What did other users do?
The poll result listed below shows what users chose to do with winfsp-x64.dll. 67% have voted for removal. Based on votes from 6 users.
NOTE: Please do not use this poll as the only source of input to determine what you will do with winfsp-x64.dll. Only 6 users has voted so far so it does not offer a high degree of confidence.
DigiAngel commented Sep 9, 2016
A reboot and repair had no effect..same issue. The only other things I can think of is that the remote SSH server requires a password, and that password has special characters. do I need to put the password in the connection stanza like "\sshfs\user:pass@server"? Thank you.
Преимущества
Стабильность
WinFsp очень стабилен. Нет известных сбоев режима ядра, и он не страдает утечками ресурсов или аналогичными проблемами. WinFsp обязан этой стабильностью своему дизайну и строгому режиму тестирования.
Comments
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
WinFsp — это набор программных компонентов для компьютеров Windows, который позволяет создавать файловые системы в пользовательском режиме. В этом смысле он похож на FUSE (файловая система в пользовательском пространстве), который предоставляет те же функции на UNIX-подобных компьютерах.
Лицензия
WinFsp доступен по лицензии GPLv3, за исключением Free/Libre и программного обеспечения с открытым исходным кодом. Также доступна коммерческая лицензия. Пожалуйста, свяжитесь с Биллом Зиссимопулосом для получения более подробной информации.
Have installed the WinFsp and SSHFS-Win (x64) on my x64 system.
Connecting using \SSHFS\user@machine fails.
If I try a CMD window (administrative mode), I can ssh into the machine.
ssh.exe ulf@narsil
works.
sshfs ulf@narsil
results in the error message:
cygfuse: initialization failed: winfsp-x64.dll not found
I can see that it is not happy about registry for HKLM\SOFTWARE\SSHFS-Win and
HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher\Services
I have tried installing the 32 bit version as well, and I get a little further since it
is no longer complaing about missing dll's, but sshfs still does not work.
echo WINFSP AND SSHFS-WIN INSTALLATION DIRECTORIES
reg query HKLM\SOFTWARE\WinFsp /reg:32
REG QUERY HKLM\SOFTWARE\WOW6432Node\SSHFS-Win /f InstallDir /t REG_SZ /c /e
echo reg query HKLM\SOFTWARE\SSHFS-Win /reg:32 FAILS
echo.
echo WINFSP NETWORK PROVIDER DLL AND SSHFS REGISTRATIONS
reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
reg query HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Np\NetworkProvider
reg query HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\WinFsp
echo reg query HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher\Services\sshfs FAILS
echo.
echo WINFSP FSD CONFIGURATION AND STATUS
sc query WinFsp
sc qc WinFsp
sc sdshow WinFsp
echo.
echo WINFSP.LAUNCHER CONFIGURATION AND STATUS
sc query WinFsp.Launcher
sc qc WinFsp.Launcher
sc sdshow WinFsp.Launcher
echo.
WINFSP AND SSHFS-WIN INSTALLATION DIRECTORIES
HKEY_LOCAL_MACHINE\SOFTWARE\WinFsp
InstallDir REG_SZ C:\Program Files (x86)\WinFsp\
billziss-gh commented Sep 9, 2016
The password special characters should not be an issue. Can you please let me know your OS version? Is it Windows 10? Has it had the anniversary update applied to it?
DigiAngel commented Sep 9, 2016 •
On 2016-09-09 13:15, Bill Zissimopoulos wrote:
Thanks. A final question: is your Win7 32-bit or 64-bit?
It would also be very helpful if you could run the following batch
file and let me know the output:@echo off
setlocal
echo WINFSP AND SSHFS-WIN INSTALLATION DIRECTORIES
reg query HKLM\SOFTWARE\WinFsp /reg:32
reg query HKLM\SOFTWARE\SSHFS-Win /reg:32
echo.echo WINFSP NETWORK PROVIDER DLL AND SSHFS REGISTRATIONS
reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
reg query
HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Np\NetworkProvider
reg query
HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\WinFsp
reg query
HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher\Services\sshfs
echo.echo WINFSP FSD CONFIGURATION AND STATUS
sc query WinFsp
sc qc WinFsp
sc sdshow WinFsp
echo.echo WINFSP.LAUNCHER CONFIGURATION AND STATUS
sc query WinFsp.Launcher
sc qc WinFsp.Launcher
sc sdshow WinFsp.Launcher
echo.echo OS INFORMATION
systeminfo
echo.
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Hashes [?]
Property | Value |
---|---|
MD5 | 7fea661f97d16d789a782684a5bb315c |
SHA256 | 199934722e2714785da8d35cc65d7cbd95daa4499fc41f4efaa79bd38ce21dc5 |
DigiAngel commented Sep 9, 2016
Blissfully no ;) This is Windows 7 Pro fully patched. Thank you.
How to Reproduce
Provide detailed information on how to reproduce the problem.
I installed earlier versions of the WinFsp and then SSHFS first. Deinstalled and rebooted.
Installed the versions below, and have not been able to get anything going.
C:\Program Files\SSHFS-Win\bin>sc query WinFsp
SERVICE_NAME: WinFsp
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Program Files\SSHFS-Win\bin>net use \memfs64\share
System error 67 has occurred.
WinFsp · Windows File System Proxy
WinFsp is a set of software components for Windows computers that allows the creation of user mode file systems. In this sense it is similar to FUSE (Filesystem in Userspace), which provides the same functionality on UNIX-like computers.
WinFsp is very stable. There are no known kernel mode crashes and it does not suffer from resource leaks or similar problems. WinFsp owes this stability to its Design and its rigorous Testing Regime.
WinFsp outperforms its competition and in many scenarios performs as well as NTFS. Read more about its Performance.
WinFsp strives for compatibility with NTFS and file system correctness. For the full details see the Compatibility document.
WinFsp has an easy to use but comprehensive API.
- Signed drivers provided on every release.
- Available under the GPLv3 license with a special exception for Free/Libre and Open Source Software.
The project source code is organized as follows:
Building and Running
In order to build WinFsp you will need the following:
To fully build WinFsp (including the installer) you must use tools\build.bat . By default it builds a Release build, but you can choose either the Debug or Release configuration by using the syntax:
If you build the driver yourself it will not be signed and Windows will refuse to load it unless you enable "testsigning". You can enable "testsigning" using the command bcdedit.exe -set testsigning on . For more information see this document.
WinFsp is designed to run on Windows 7 and above. It has been tested on the following platforms:
- Windows 7 Enterprise
- Windows 8 Pro
- Windows Server 2012
- Windows 10 Pro
- Windows Server 2016
- Windows 11 Pro
I am looking for help in the following areas:
- If you have a file system that runs on FUSE please consider porting it to WinFsp. WinFsp has a native API, but it also has a FUSE (high-level) API.
- If you are working with a language other than C/C++ (e.g. Delphi, Java, etc.) and you are interested in porting/wrapping WinFsp I would love to hear from you.
- There are a number of outstanding issues listed in the GitHub repository. Many of these require knowledge of Windows kernel-mode and an understanding of the internals of WinFsp so they are not for the faint of heart.
In all cases I can provide ideas and/or support.
Where to Discuss
If you wish to discuss WinFsp there are now two options:
WinFsp is available under the GPLv3 license with a special exception for Free/Libre and Open Source Software. A commercial license is also available. Please contact Bill Zissimopoulos for more details.
DigiAngel commented Sep 8, 2016
Should I give this a reboot?
Screenshots
Простота использования
WinFsp имеет простой в использовании, но всеобъемлющий API.
Links:
Sanitized file enclosed. 64 bit. I'll bet the state of STOPPED for
FILE_SYSTEM_DRIVER isn't helping ;) Thank you.
WINFSP AND SSHFS-WIN INSTALLATION DIRECTORIES
HKEY_LOCAL_MACHINE\SOFTWARE\WinFsp
InstallDir REG_SZ C:\Program Files (x86)\WinFsp\
HKEY_LOCAL_MACHINE\SOFTWARE\SSHFS-Win
InstallDir REG_SZ C:\Program Files (x86)\SSHFS-Win\
WINFSP NETWORK PROVIDER DLL AND SSHFS REGISTRATIONS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
ProviderOrder REG_SZ RDPNP,LanmanWorkstation,webclient,WinFsp.Np
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinFsp.Np\NetworkProvider
Name REG_SZ Windows File System Proxy
ProviderPath REG_SZ C:\Program Files (x86)\WinFsp\bin\winfsp-x64.dll
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\WinFsp
EventMessageFile REG_SZ C:\Program Files (x86)\WinFsp\bin\winfsp-x64.dll
TypesSupported REG_DWORD 0x7
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher\Services\sshfs
Executable REG_SZ C:\Program Files (x86)\SSHFS-Win\bin\sshfs-win.exe
CommandLine REG_SZ %1 %2
Security REG_SZ D:P(A;;RPWPLC;;;WD)
JobControl REG_DWORD 0x1
Credentials REG_DWORD 0x1
WINFSP FSD CONFIGURATION AND STATUS
SERVICE_NAME: WinFsp
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 1 STOPPED
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: WinFsp
TYPE : 2 FILE_SYSTEM_DRIVER
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : ??\C:\Program Files (x86)\WinFsp\bin\winfsp-x64.sys
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : WinFsp
DEPENDENCIES :
SERVICE_START_NAME :
WINFSP.LAUNCHER CONFIGURATION AND STATUS
SERVICE_NAME: WinFsp.Launcher
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: WinFsp.Launcher
TYPE : 10 WIN32_OWN_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 0 IGNORE
BINARY_PATH_NAME : "C:\Program Files (x86)\WinFsp\bin\launcher-x64.exe"
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : WinFsp.Launcher
DEPENDENCIES :
SERVICE_START_NAME : LocalSystem
Host Name: JLAY
OS Name: Microsoft Windows 7 Professional
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner:
Registered Organization:
Product ID: XXXXX-XXX-XXXXXXX-XXXXX
Original Install Date: 1/29/2014, 1:57:09 PM
System Boot Time: 9/8/2016, 4:59:02 PM
System Manufacturer: .
System Model:
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~3400 Mhz
BIOS Version: Dell Inc. A11, 9/16/2013
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 8,094 MB
Available Physical Memory: 3,920 MB
Virtual Memory: Max Size: 16,186 MB
Virtual Memory: Available: 10,606 MB
Virtual Memory: In Use: 5,580 MB
Page File Location(s): C:\pagefile.sys
Domain:
Logon Server:
Hotfix(s): 305 Hotfix(s) Installed.
[01]: KB2959936
[02]: KB2891638
[03]: KB2849697
[04]: KB2849696
[05]: KB2841134
[06]: KB2670838
[07]: KB2830477
[08]: KB2592687
[09]: KB958830
[10]: KB971033
[11]: KB2305420
[12]: KB2393802
[13]: KB2479943
[14]: KB2491683
[15]: KB2506014
[16]: KB2506212
[17]: KB2506928
[18]: KB2509553
[19]: KB2511455
[20]: KB2515325
[21]: KB2533552
[22]: KB2544893
[23]: KB2545698
[24]: KB2547666
[25]: KB2552343
[26]: KB2560656
[27]: KB2563227
[28]: KB2564958
[29]: KB2570947
[30]: KB2574819
[31]: KB2579686
[32]: KB2585542
[33]: KB2603229
[34]: KB2604115
[35]: KB2620704
[36]: KB2621440
[37]: KB2637518
[38]: KB2640148
[39]: KB2644615
[40]: KB2647753
[41]: KB2654428
[42]: KB2660075
[43]: KB2661254
[44]: KB2667402
[45]: KB2676562
[46]: KB2685811
[47]: KB2685813
[48]: KB2690533
[49]: KB2698365
[50]: KB2705219
[51]: KB2719857
[52]: KB2726535
[53]: KB2727528
[54]: KB2729094
[55]: KB2732059
[56]: KB2732487
[57]: KB2736422
[58]: KB2742599
[59]: KB2750841
[60]: KB2761217
[61]: KB2770660
[62]: KB2773072
[63]: KB2775511
[64]: KB2786081
[65]: KB2791765
[66]: KB2798162
[67]: KB2799926
[68]: KB2800095
[69]: KB2807986
[70]: KB2808679
[71]: KB2813170
[72]: KB2813347
[73]: KB2813430
[74]: KB2834140
[75]: KB2840631
[76]: KB2843630
[77]: KB2846960
[78]: KB2847077
[79]: KB2847927
[80]: KB2852386
[81]: KB2853952
[82]: KB2857650
[83]: KB2861698
[84]: KB2862152
[85]: KB2862330
[86]: KB2862335
[87]: KB2862973
[88]: KB2864202
[89]: KB2868038
[90]: KB2868116
[91]: KB2871997
[92]: KB2884256
[93]: KB2885698
[94]: KB2891804
[95]: KB2892074
[96]: KB2893294
[97]: KB2893519
[98]: KB2894844
[99]: KB2900986
[100]: KB2905454
[101]: KB2908783
[102]: KB2909210
[103]: KB2909921
[104]: KB2911501
[105]: KB2912390
[106]: KB2918077
[107]: KB2918614
[108]: KB2919469
[109]: KB2923545
[110]: KB2925418
[111]: KB2928562
[112]: KB2929437
[113]: KB2929733
[114]: KB2931356
[115]: KB2936068
[116]: KB2937610
[117]: KB2943357
[118]: KB2952664
[119]: KB2953522
[120]: KB2957189
[121]: KB2957689
[122]: KB2962872
[123]: KB2964358
[124]: KB2966583
[125]: KB2968294
[126]: KB2970228
[127]: KB2972100
[128]: KB2972211
[129]: KB2973112
[130]: KB2973201
[131]: KB2973351
[132]: KB2976627
[133]: KB2977292
[134]: KB2977629
[135]: KB2978120
[136]: KB2984972
[137]: KB2985461
[138]: KB2987107
[139]: KB2990214
[140]: KB2991963
[141]: KB2992611
[142]: KB2999226
[143]: KB3000483
[144]: KB3000988
[145]: KB3003057
[146]: KB3003743
[147]: KB3004361
[148]: KB3004375
[149]: KB3006121
[150]: KB3006137
[151]: KB3006625
[152]: KB3008627
[153]: KB3008923
[154]: KB3010788
[155]: KB3011780
[156]: KB3013410
[157]: KB3013531
[158]: KB3019215
[159]: KB3020369
[160]: KB3020370
[161]: KB3020388
[162]: KB3021674
[163]: KB3021917
[164]: KB3021952
[165]: KB3022345
[166]: KB3022777
[167]: KB3023215
[168]: KB3025390
[169]: KB3030377
[170]: KB3031432
[171]: KB3032359
[172]: KB3033889
[173]: KB3033929
[174]: KB3034196
[175]: KB3035126
[176]: KB3037574
[177]: KB3038314
[178]: KB3040272
[179]: KB3042058
[180]: KB3042553
[181]: KB3045685
[182]: KB3045999
[183]: KB3046017
[184]: KB3046269
[185]: KB3046480
[186]: KB3049563
[187]: KB3050265
[188]: KB3054476
[189]: KB3055642
[190]: KB3057154
[191]: KB3058515
[192]: KB3059317
[193]: KB3060716
[194]: KB3061518
[195]: KB3064209
[196]: KB3065822
[197]: KB3065987
[198]: KB3067505
[199]: KB3067903
[200]: KB3068708
[201]: KB3071756
[202]: KB3072305
[203]: KB3072630
[204]: KB3074543
[205]: KB3074886
[206]: KB3075226
[207]: KB3075249
[208]: KB3075516
[209]: KB3075851
[210]: KB3076949
[211]: KB3077715
[212]: KB3078071
[213]: KB3078601
[214]: KB3078667
[215]: KB3080079
[216]: KB3080149
[217]: KB3080446
[218]: KB3081320
[219]: KB3081954
[220]: KB3083324
[221]: KB3083710
[222]: KB3083992
[223]: KB3084135
[224]: KB3086255
[225]: KB3087038
[226]: KB3087985
[227]: KB3088195
[228]: KB3092601
[229]: KB3092627
[230]: KB3093513
[231]: KB3093983
[232]: KB3097966
[233]: KB3097989
[234]: KB3100773
[235]: KB3101246
[236]: KB3101722
[237]: KB3101746
[238]: KB3102429
[239]: KB3102810
[240]: KB3104002
[241]: KB3107998
[242]: KB3108371
[243]: KB3108381
[244]: KB3108664
[245]: KB3108670
[246]:
Network Card(s): 2 NIC(s) Installed.
[01]: Realtek PCIe GBE Family Controller
Connection Name: Local Area Connection
DHCP Enabled: Yes
DHCP Server:
IP address(es)
[01]:
[02]: VirtualBox Host-Only Ethernet Adapter
Connection Name: VirtualBox Host-Only Network
DHCP Enabled: No
IP address(es)
[01]: 169.254.78.53
[02]: fe80::a590:c346:273:4e35
winfsp-x64.dll is part of WinFsp and developed by Navimatics Corporation according to the winfsp-x64.dll version information.
winfsp-x64.dll's description is "Windows File System Proxy"
winfsp-x64.dll is usually located in the 'C:\Windows\system32\disko\' folder.
None of the anti-virus scanners at VirusTotal reports anything malicious about winfsp-x64.dll.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
Network
Vendor and version information [?]
The following is the available information on winfsp-x64.dll:
Property | Value |
---|---|
Product name | WinFsp |
Company name | Navimatics Corporation |
File description | Windows File System Proxy |
Internal name | winfsp.dll |
Original filename | winfsp.dll |
Legal copyright | 2015-2019 Bill Zissimopoulos |
Product version | 2019.1 |
File version | 1.4.19016.0eb84d6 |
Here's a screenshot of the file properties when displayed by Windows Explorer:
Product name | WinFsp |
Company name | Navimatics Corporation |
File description | Windows File System Proxy |
Internal name | winfsp.dll |
Original filename | winfsp.dll |
Legal copyright | 2015-2019 Bill Zissimopoulos |
Product version | 2019.1 |
File version | 1.4.19016.0eb84d6 |
ERROR: The system was unable to find the specified registry key or value.
Где обсудить
Если вы хотите обсудить WinFsp, теперь есть два варианта:
- Группа Google WinFsp
- Твиттер автора
Sandbox Report
The following information was gathered by executing the file inside Cuckoo Sandbox.
Сборка и запуск
Для сборки WinFsp вам потребуется следующее:
Для полной сборки WinFsp ( включая установщик) необходимо использовать tools build.bat . По умолчанию он создает сборку Release, но вы можете выбрать конфигурацию Debug или Release, используя синтаксис:
Если вы создадите драйвер самостоятельно, он не будет подписан, и Windows откажется загружать его, если вы не включите «тестовое подписание». Вы можете включить «подписание тестов» с помощью команды bcdedit.exe -set testsigning on . Для получения дополнительной информации см. Этот документ.
WinFsp разработан для работы в Windows 7 и выше.. Он был протестирован на следующих платформах:
- Windows 7 Enterprise
- Windows 8 Pro
- Windows Server 2012
- Windows 10 Pro
- Windows Server 2016
reg query HKLM\SOFTWARE\SSHFS-Win /reg:32 FAILS
WINFSP NETWORK PROVIDER DLL AND SSHFS REGISTRATIONS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
ProviderOrder REG_SZ WinFsp.Np,RDPNP,LanmanWorkstation,webclient,npnotes64,MfeEpePcNP,PnSson
(Default) REG_SZ
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinFsp.Np\NetworkProvider
Name REG_SZ Windows File System Proxy
ProviderPath REG_SZ C:\Program Files (x86)\WinFsp\bin\winfsp-x64.dll
DeviceName REG_SZ \Device\WinFsp.Mup
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\WinFsp
EventMessageFile REG_SZ C:\Program Files (x86)\WinFsp\bin\winfsp-x64.dll
TypesSupported REG_DWORD 0x7
Malware or legitimate?
If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.
And now some shameless self promotion ;)
Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/2008/2016/2019/Vista/7/8/8.1/10. Supports both 32- and 64-bit Windows.
Производительность
WinFsp превосходит своих конкурентов и во многих сценариях работает а также NTFS. Подробнее о его производительности.
billziss-gh commented Sep 9, 2016
Thanks. A final question: is your Win7 32-bit or 64-bit?
It would also be very helpful if you could run the following batch file and let me know the output:
billziss-gh commented Sep 8, 2016
A reboot should not be required, but please try it to make sure. If this turns out not to fix the problem try to also repair the installations.
Also let me know your OS version and if you have any special configuration.
VirusTotal report
None of the 69 anti-virus programs at VirusTotal detected the winfsp-x64.dll file.
Signatures
DigiAngel commented Sep 8, 2016
Should I give this a reboot?
reg query HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher\Services\sshfs FAILS
WINFSP FSD CONFIGURATION AND STATUS
SERVICE_NAME: WinFsp
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: WinFsp
TYPE : 2 FILE_SYSTEM_DRIVER
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : ??\C:\Program Files (x86)\WinFsp\bin\winfsp-x64.sys
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : WinFsp
DEPENDENCIES :
SERVICE_START_NAME :
WINFSP.LAUNCHER CONFIGURATION AND STATUS
SERVICE_NAME: WinFsp.Launcher
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: WinFsp.Launcher
TYPE : 10 WIN32_OWN_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 0 IGNORE
BINARY_PATH_NAME : "C:\Program Files (x86)\WinFsp\bin\launcher-x64.exe"
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : WinFsp.Launcher
DEPENDENCIES :
SERVICE_START_NAME : LocalSystem
Организация проекта
Исходный код проекта организован следующим образом:
Generic
Как помочь
Мне нужна помощь в следующих областях:
- Если у вас есть файловая система, работающая на FUSE, рассмотрите возможность переноса ее на WinFsp. WinFsp имеет собственный API, но он также имеет FUSE (высокоуровневый) API.
- Если вы работаете с языком, отличным от C/C ++ (например, Delphi, Java и т. Д.) И вы заинтересованы в переносе/упаковке WinFsp, я хотел бы услышать от вас.
- В репозитории GitHub перечислен ряд нерешенных проблем. Многие из них требуют знания режима ядра Windows и понимания внутреннего устройства WinFsp, поэтому они не для слабонервных.
Во всех случаях я могу предоставить идеи и/ или поддержка.
Summary
ERROR: The system was unable to find the specified registry key or value.
Digital signatures [?]
winfsp-x64.dll has a valid digital signature.
Совместимость
WinFsp стремится к совместимости с NTFS и правильности файловой системы. Для получения полной информации см. Документ о совместимости.
Другие преимущества
- Подписанные драйверы предоставляются в каждом выпуске.
- Доступны под лицензией GPLv3 со специальным исключением для Free/Libre и программного обеспечения с открытым исходным кодом.
What will you do with winfsp-x64.dll?
To help other users, please let us know what you will do with winfsp-x64.dll:
Summary
Successfully executed process in sandbox.
Читайте также: