WinFsp 2017.2 B2

THIS IS A PRE-RELEASE

• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016.

CHANGES SINCE 2017.1

• New command line tool fsptool allows command line access to some WinFsp features.
• New GetDirInfoByName file system operation adds fast queries of directory info by file name rather than pattern [e.g. FindFirstFileW(L"foobar", FindData)]. Tests with fsbench showed that such queries are sped up by an order of magnitude when using GetDirInfoByName in MEMFS. Case-sensitive FUSE file systems get this optimization for free. The .NET layer also adds GetDirInfoByName.
• New FspFileSystemOperationProcessId API adds support for getting the originating process ID (PID) during Create, Open and Rename calls. FUSE file systems can now access fuse_context::pid. The .NET layer also adds GetOperationProcessId.
• Important GitHub issues fixed: #96, #97, #103, #107

WinFsp 2017.2 B1

THIS IS A PRE-RELEASE

• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016.

CHANGES SINCE 2017.1

• New command line tool fsptool allows command line access to some WinFsp features.
• New GetDirInfoByName file system operation adds fast queries of directory info by file name rather than pattern [e.g. FindFirstFileW("foobar", FindData)]. Tests with fsbench showed that such queries are sped up by an order of magnitude when using GetDirInfoByName in MEMFS.
• New FspFileSystemOperationProcessId API adds support for getting the originating process ID (PID) during Create, Open and Rename calls.

WinFsp 2017.1; issue #96

THIS IS A PRE-RELEASE

• This pre-release contains a fix for GitHub issue #96.
• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016.

WinFsp 2017.1

This release brings some major new components and improvements.

• A .NET layer that allows the creation of file systems in managed mode. This is contained in the new winfsp-msil.dll. The new .NET layer is being tested with the WinFsp test suites and Microsoft's ifstest.
• FUSE for Cygwin is now included with the installer.
• FUSE now has a -ovolname=VOLNAME parameter that allows setting the volume label. Thanks @SamKelly.
• A number of other FUSE improvements have been made (see issue #85).

NOTE: The included .NET layer requires .NET Framework v3.5 or higher to be installed (included by default in Windows 7 or higher). However the memfs-dotnet and passthrough-dotnet samples require .NET Framework v4.5 and will therefore not run on computers that do not have this framework installed!

NOTE: The C++ layer included in the v1.1 beta releases is not part of this release as it is still work in progress. It can be found in inc/winfsp/winfsp.hpp in the WinFsp source repository.

WinFsp 2017.1 B3

THIS IS A PRE-RELEASE

• The API is backwards compatible, but may not be forwards compatible. For example, API design flaws and bugs may be fixed in a forwards-incompatible manner.
• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016. Only final releases have signed drivers for all OS'es (including Server 2016).

NOTE: The current plan is for this prerelease to be the final beta before release of WinFsp 2017.1 (v1.1).

Changes from WinFsp 2017

• A .NET layer that allows the creation of file systems in managed mode. This is contained in the new winfsp-msil.dll. The new .NET layer is being tested with the WinFsp test suites and Microsoft's ifstest.
• A simple C++ layer can be found in inc/winfsp/winfsp.hpp. [NOTE: The current plan is for the C++ layer to not be included in the final WinFsp 2017.1 release, because it is not finalized yet. It will however be available in the source repository.]
• FUSE for Cygwin is now included with the installer.
• FUSE now has a -ovolname=VOLNAME parameter that allows setting the volume label. Thanks @SamKelly.

WinFsp 2017.1 B2

THIS IS A PRE-RELEASE

• The API is backwards compatible, but may not be forwards compatible. For example, API design flaws and bugs may be fixed in a forwards-incompatible manner.
• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016. Only final releases have signed drivers for all OS'es (including Server 2016).

Changes from WinFsp 2017

• A .NET layer that allows the creation of file systems in managed mode. This is contained in the new winfsp-msil.dll. The new .NET layer is being tested with the WinFsp test suites and Microsoft's ifstest.
• A simple C++ layer can be found in inc/winfsp/winfsp.hpp.
• FUSE for Cygwin is now included with the installer.
• FUSE now has a -ovolname=VOLNAME parameter that allows setting the volume label. Thanks @SamKelly.

WinFsp 2017.1 BETA

THIS IS A PRE-RELEASE

• The API is backwards compatible, but may not be forwards compatible. For example, API design flaws and bugs may be fixed in a forwards-incompatible manner.
• This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016. Only final releases have signed drivers for all OS'es (including Server 2016).

Changes from WinFsp 2017

• A .NET layer that allows the creation of file systems in managed mode. This is contained in the new winfsp-msil.dll.
• A simple C++ layer can be found in inc/winfsp/winfsp.hpp.
• FUSE for Cygwin is now included with the installer.
• FUSE now has a -ovolname=VOLNAME parameter that allows setting the volume label. Thanks @SamKelly.

WinFsp 2017

This is the WinFsp 2017 release! 🎉

• The API is now FROZEN. Breaking API changes will receive a major version update (2.0). Incremental API changes will receive a minor version update (1.x).
• Adds chocolatey package. Try choco install winfsp (note: pending approval from chocolatey.org).
• FUSE -d output now always goes to stderr. There is also a new -oDebugLog=FILE switch to specify a debug output file.
• FUSE now provides a default statfs implementation if a file system does not provide one.
• The WinFsp DLL now exports fuse_* symbols in addition to the fsp_fuse_* symbols. These symbols are for use with programs that use FFI technology such as jnr-fuse and fusepy ONLY. They are not supposed to be used by native C/C++ programs. Such programs are supposed to include the <fuse.h> headers.

WinFsp 2017 RC3

v1.0RC3

WinFsp 2017 RC3

WinFsp 2017 RC2

v1.0RC2

WinFsp 2017 RC2