Releases: dokan-dev/dokany
v2.3.1.1000
This is a patch version.
The version has minor changes compared to v2.3.0.1000. Please see changelog for the exact changes and more details.
Thanks to all the contributors as always !!!
v2.3.0.1000
This is a minor version.
The installer will now prevent installation if the driver is already present. Several bug fixes address issues like memory leaks, crashes, and incorrect parameter handling In library. The most impactful change is the deletion semantics that now matches Microsoft expectations #883.
Library breaking change: DOKAN_FILE_INFO.DeleteOnClose
was renamed DOKAN_FILE_INFO.DeletePending
. Same expectation (remove the object) but is set when last handle on the object is being closed #883.
This version was also published on Chocolatey 🍫
Please see changelog for the other changes and more details.
Thanks to all the contributors as always !!! @uhonermann , @CookiePLMonster and others ...
v2.2.1.1000
This is a patch version.
It improves the uninstall experience since we switched to WiX version 5 (v2.2.0.1000). It also removes a flaky check in the kernel during create ( see #1253 for more context ).
This version was also published on Chocolatey 🍫
Please see changelog for the other changes and more details.
Thanks to all the contributors as always !!! @pomaroff, @ and others ...
v2.2.0.1000
This is a minor version.
This release focuses on keeping network drives isolated between users when browsing with UNC path ( #1235 ) and creating a MSI for ARM64 binaries. This MSI is also included in the DokanSetup.exe
bundle installer. Adding this platform required and was a good moment to migrate our install to WiX version 5 (we were on the no longer supported v3). This change should and as shown from my testing to be transparent.
This version was also published on Chocolatey 🍫
Please see changelog for the other changes and more details.
Thanks to all the contributors as always !!! @lostmsu, @LTRData and others ...
2.1.0.1000
This is a minor version.
Glad to be back! 😉
It has been more than a year since the last release which was due to the expiration of our Extended Validation Certificate used for signing the driver and releases.
Thanks to the 💰 contribution from Google and the endless 💪 support from Leosac (Check their great stuff!), we were able to acquire a new certificate valid for the next 3 years 🎉 🎈
Major changes:
- Microsoft has changed the rules of which type of drivers (primitive) can be signed through their platform. Therefore we had to adapt how dokan is installed. Please let us know if you have any install / uninstall issue.
- New library unmount API introduced by @LTRData.
- Few (rare) BSOD fixed.
Please see changelog for the other changes and more details.
Thanks to all the contributors as always !!! @LTRData, @ylgybbz, @uhonermann, @hkf7703, @FaerieLee ....
Hope you will all enjoy our first and last 2023 release, see you in 2024!
2.0.6.1000
This is a patch version.
If you are already using 2.0.5, there is no reason to update unless you are impacted by the delete notification during FileDispositionInformation
#1111.
Please see changelog for more details.
And again here is how to migrate an existing > 1.1.0 filesystem to 2.0.0 and note the rollback of the FindFilesWithPattern v1 behavior from 2.0.5.
Thanks to all the contributors as always !!! @onexzero, @KoltesDigital
2.0.5.1000
This is a patch version.
It includes a fix for Case Sensitive listing, UNCName not removed on unexpected casing, the possibility to override the read max size on FUSE and the rollback of the FindFilesWithPattern v1 behavior from 2.0.5.
Please see changelog for more details.
And again here is how to migrate an existing > 1.1.0 filesystem to 2.0.0 and note the rollback of the FindFilesWithPattern v1 behavior from 2.0.5.
Thanks to all the contributors as always !!! @KoltesDigital
2.0.4.1000
This is a patch version.
It focuses on clarifying the usage of FindFiles
and FindFilesWithPattern
with their changes in v2, removing UNCName
possible prefix on CreateFile
and few Kernel fixes.
Please see changelog for more details.
And again here is how to migrate an existing > 1.1.0 filesystem to 2.0.0.
Thanks to all the contributors as always !!! @ATRiiX @robert-j
2.0.3.2000
This is a patch version.
No new binaries were built for this version. They have only been repacked in a new installer that fixes the remaining conflict with the v1 one.
Please see changelog for more details.
And again here is how to migrate an existing > 1.1.0 filesystem to 2.0.0.
Thanks to all the contributors as always !!!
2.0.3.1000
This is a patch version.
The version focus on improving the read & write performances that in some cases were worse than v1. 2.0.3.1000 is now faster on all those scenarios by 10 to 42%. Otherwise few stability and installer fixes were added.
Please see changelog for more details.
And again here is how to migrate an existing > 1.1.0 filesystem to 2.0.0.
Thanks to all the contributors as always !!!