+- Hasleo Software Forums (https://www.easyuefi.com/forums)
+-- Forum: Hasleo Software (formerly called EasyUEFI Development Team) (https://www.easyuefi.com/forums/forum-1.html)
+--- Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software) (https://www.easyuefi.com/forums/forum-10.html)
+--- Thread: dokany issues and other apps (/thread-4820.html)
dokany issues and other apps - JayDee - 03-30-2026
As someone that likes to experiment I'm exploring the use of
cppcryptfs (an encryption file/folder app)
This app needs dokany as used by HBS.
I certainly don't want to mess up my great installation of HBS
but I'm unavailable to do an install of an updated dokany
to work with cppcryptfs since the installation identifies
the driver as already installed.
I know this is not strictly an HBS issue but if anyone has some ideas
I would appreciate it.
JayDee
RE: dokany issues and other apps - al3x - 03-30-2026
It seems that the version installed by HBS is an older one (v2.1.0 vs. newest v2.3.1).
What you can do, I tried this myself, is to uninstall the driver currently installed by HBS:
- Open a cmd prompt with admin rights
- Put in sc stop dokan2, then sc delete dokan2
- After that a Windows restart is needed for the driver to be fully unloaded
Now you will be able to install DokanSetup.exe with the latest version. This will also recreate your Dokan driver in Windows.
cppcryptfs.exe should be working now because you have installed the latest Dokan driver.
HBS also still works as far as I can tell. HBS only needs this driver for image mounting. And this feature fully worked in my tests. Also, reinstalling HBS and rebooting Windows had no effect on the current installed Dokan driver, cppcryptfs.exe still worked after that.
@admin: In fact: HBS also worked when uninstalling Dokan completely. Even after using the commands above to fully unload the driver and after a Windows restart, HBS still had no problem to mount images. Could it be that the installation of the Dokan driver is not needed for HBS to work properly because of the driver files already being present in the installation directory of HBS? Maybe this driver installation step could be left out during HBS installation then? Maybe worth a look
