winfsp/winfsp v1.4B2 on GitHub

THIS IS A PRE-RELEASE

This pre-release contains experimental FUSE 3.2 support. If you have a FUSE 3.2 file system I would love to hear your feedback.
This pre-release contains fundamental changes in how FUSE loops (fuse_loop and fuse_loop_mt) are run. If you are running a FUSE file system and you experience differences in behavior with prior versions of WinFsp, please open an issue to discuss.
- NOTE: Turns out that the new FUSE loops broke fuse_daemonize. This problem has been fixed in commit bef5ba7, which will be included in the next beta.
This pre-release includes signed drivers for Windows 7, 8, 10, but not Server 2016.

FUSE3 API (version 3.2) is now available. The FUSE2 API (version 2.8) also remains supported.
New Control file system operation allows sending custom control codes to the file system using the Windows DeviceIoControl API. FUSE ioctl is also supported.
FlushAndPurgeOnCleanup has now been added to the .NET API. (GitHub PR #176; thanks @FrKaram.)
New sample file system "airfs" contributed by @JohnOberschelp. Airfs is an in-memory file system like Memfs on which it is based on; it has received substantial improvements in how the file name space is maintained and has been modified to use modern C++ techniques by John.
New sample file system "passthrough-fuse3" passes all operations to an underlying file system. This file system is built using the FUSE3 API. It builds and runs on both Windows and Cygwin.
The FUSE layer now supports multiple file systems within a single process. This is a long standing problem that has been fixed. (GitHub issue #135.)