CHANGES SINCE WINFSP 2022.2
This release is a major version change for WinFsp (from 1.x to 2.x). There are no backwards incompatible API changes in this release, but nevertheless enough things change that warrant a version change.
The major new feature of this release is that it allows uninstallation and reinstallation of WinFsp without reboot. Going forward installers named
winfsp-2.x.y.msi can be uninstalled and reinstalled without reboot. Furthermore a later version
winfsp-2.x.y.msi installer can be used to upgrade over an earlier version
winfsp-2.x.y.msi installer. However note that a
winfsp-2.x.y.msi installer cannot be used to upgrade over a legacy
winfsp-1.x.y.msi installer; you will still need to uninstall the old
winfsp-1.x.y.msi installer, potentially reboot and then install the new
Changes visible to file system developers are listed below:
WinFsp executable files are now installed by default in the directory
C:\Program Files (x86)\WinFsp\SxS\sxs.<InstanceID>\bin. The previous directory
C:\Program Files (x86)\WinFsp\binis now a junction that points to the above directory.
The WinFsp driver name is no longer
winfsp, but rather a name such as
winfsp+<InstanceID>. This means that managing the driver using the
sc.exeutility is no longer as easy.
fsptoolutility has been updated with new commands
unloadcommands can be used to manage the driver from the command line. This is rarely necessary, but may be useful for troubleshooting purposes.
Prior to this release the WinFsp driver would never unmount a file system volume unless the user mode file system requested the unmount. From this release onward it is possible for the WinFsp driver to unmount a file system volume, without a user mode file system request. This is to allow for the driver to be unloaded.
A new operation
DispatcherStoppedhas been added to
FSP_FILE_SYSTEM_INTERFACE, which is sent after the file system volume has been unmounted and the file system dispatcher has been stopped. This can happen because of a user mode file system request via
FspFileSystemStopDispatcheror because of driver unload. The
DispatcherStoppedoperation includes a
Normallyparameter, which is
TRUEfor normal file system shutdown via
Native file systems that use the
FspServiceinfrastructure can use the
FspFileSystemStopServiceIfNecessaryAPI to handle the
DispatcherStoppedoperation (see the MEMFS and NTPTFS samples). FUSE file systems get this functionality for free. .NET file systems that use the
Serviceclass infrastructure also get this functionality for free.
- There is now a winfsp.net nuget package at https://www.nuget.org/packages/winfsp.net
- The FUSE passthrough file systems have been updated to support long paths. This is also due to work by @zeho11.
In some rare circumstances WinFsp file systems could report duplicate directory entries. This problem has been fixed. (GitHub issue #475.)
The WinFsp symbols directory has been removed. If you are looking for WinFsp symbols you can find them at https://github.com/winfsp/winfsp.sym
BUILD HASHES (SHA256)