DrivePool is not working - CoveFS not found?

[Sergey Klepov]

Heard many good things about DrivePool, decided to test it. Have downloaded the latest stable build available on main downloads page for win10 x64 (2.2.2.934). Installed it, started drivepool - received an error "Background service failed to start, please restart". Restarted windows several times, restarted windows service of drivepool several times - didn't help. Checked logs of service - what I see there is

DrivePool.Service.exe    Information    0    [BitLocker] BitLocker monitoring started    2018-08-08 20:19:46Z    1169533024
DrivePool.Service.exe    Information    0    [Main] StableBit DrivePool 2.2.2.934    2018-08-08 20:20:50Z    34181655
DrivePool.Service.exe    Information    0    [Main] Microsoft Windows NT 10.0.17134.0    2018-08-08 20:20:50Z    34198889
DrivePool.Service.exe    Error    0    [Main] Unable to start StableBit DrivePool service, CoveFS was not found. Exception of type 'DrivePoolService.Pool.CoveFsDriver.FsControl+#APh' was thrown.    2018-08-08 20:20:50Z    34246849
 

Emm, of course I don't have CoveFS on first clean install. How to make that thing work?

[Jaga]

Sounds like a bad install.  I'd suggest uninstalling Drivepool, making sure you're logged in with an admin-level account in Windows, temporarily disabling your Anti-virus, cleaning out your temp files with something like CCleaner, re-downloading the latest DrivePool package, and then trying a re-install (right-click the download, choose Run as administrator). 

[Christopher (Drashna)]

What @Jaga said, actually. 

And "coveFS" is the driver for the pool, so it's a critical component, actually. 

 

And it may be worth doing this: http://wiki.covecube.com/StableBit_DrivePool_Q3017479

And then reinstall the software. 

If you continue to have issues, then open a ticket at https://stablebit.com/contact 
and run the StableBit Troubleshooter: http://wiki.covecube.com/StableBit_Troubleshooter

[Sergey Klepov]

Actually it did help, thanks.

Not sure what, but I have a suspicion that I forgot to run installer with admin privileges 

[Christopher (Drashna)]

The installer should prompt for elevation automatically, actually.  So that shouldn't matter. 

If this happened right after a major version update to Windows 10, that may be why.  Sometimes those updates nuke stuff they shouldn't.  It's not common, but it happens often enough...

[Sergey Klepov]

Yes, that makes sense, but don't remember any big update from microsoft being installed after 10th and there was no update for drive pool also.

Anyway issue was resolved, thanks

[Christopher (Drashna)]

Odd then.  If it happens again, let us know.