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 winfsp-2.x.y.msi installer.
Some changes that may be 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 directoryC:\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 aswinfsp+<InstanceID>. This means that managing the driver using thesc.exeutility is no longer as easy. -
The
fsptoolutility has been updated with new commandslsdrv,load,unloadandver. Thelsdrv,loadandunloadcommands can be used to manage the driver from the command line. This is rarely necessary, but may be useful for troubleshooting purposes. -
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
This release introduces significant internal changes, including kernel mode changes to enable the driver to be unloaded. Although there are no known crashes or other problems of such severity, please do not use in production environments.