XtremeMaC

I had the same issue. Contacted support and was told that they (Covecube) need to update the DrivePool virtual driver and have it re-sign by Microsoft before it can be used with the latest Insider Build. I have no idea how long it would take them. Hopefully soon.

Hello,
I'm on Fast Ring in Win10. Yesterday's update broke Drive Pool that's super crucial for me and few others that are not crucial.
I went the normal way, uninstalled, cleared appdata, cleared bunch of registry entries, uninstalled drivers as much as I can find along with Scanner. also uninstalled the Covecube drive under Hardware...
Yet still, I see the covecube as a drive and it won't let me add any drives to a new pool. How can I delete the so called existing pool that is no longer shown...
 
Surely not DrivePool's fault, but how can I fix this? Any ideas?


 
Yes, I know I can return to previous build, that's more headache, I'd rather try to fix the current one. Should have been as easy as re-install drivepool... looking for help

Endure,
 
When you install DrivePool and add your existing drives to it, DrivePool will see a pool size of 8TB (your total size across all drives added to the pool), but 4TB will be listed as "Other" (your existing files on the drives themselves).  As you move (not copy) your files from the drive(s) themselves into the pool drive, the files will be added to the pool itself, and the space will be reclaimed automatically to be used in the pool.
 
You can also do something called "seeding", which will speed up the process.  You don't have to "seed", it's an option:
 
http://wiki.covecube.com/StableBit_DrivePool_Q4142489
 
-Quinn