Olof Lagerkvist

> @Liryna also, see my suggested change instead of your fix, that guards against bad number returned by `bytesRead`. It is nice to have foot guards 😁 It is a...

> From MSDN it sounds like @LTRData is correct  > > E.g. a file system that serves files should always read the requested amount when possible. > > IMHO,...

> @LTRData that's why I propose there should be an option for an implementation to opt out of this behavior. E.g. a property on `IDokanOperations`, or another optional interface, or...

> And to prove my theory: https://github.com/dokan-dev/dokan-sshfs/blob/3577c47f92e6f67be80554a7b1a91a922e627495/DokanSSHFS/DokanOperations.cs#L518 yes, it appears to have this bug. No. That is not an issue. For regular files, .NET Stream reads and C library reads...

> > .NET Stream reads and C library reads always return the number of requested bytes > > This is never guaranteed, and maybe true right now on Windows, but...

> In fact, there's more down there: > > > The method is free to return fewer bytes than requested even if the end of the file stream has not...

> Hi, > I was able to rectify the issue, I had to manually delete the registry entry - HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dokan2 then reboot. Once that was complete I was able to...

> Hi LTRData, I did reboot after uninstall and before attempting to install 2.1.0.1000 but the issue persisted. The only way to resolve it was the steps I followed above,...

> Yes I rebooted and not just shut down Okay. Not sure what happened then. I have not seen that exact behavior during any tests. It usually just work after...

Yes if you have manually installed a driver somehow, or replaced the driver sys file with another file and then uninstalled the package, then the driver file with be left...