Christopher (Drashna)

Well, I don't mean to minmize the issue, at all.... but this generally happens to only about 5-6 people (or at least, that's how many report it).   So, it's no a huge thing. 
That said, 
We've looked into this issue in the past, with little success Alex is planning a "deep dive" to look into this issue ( @Mick Mickle, I believe Alex mentioned that to you in the ticket, actually), and we've talked about this The new JSON format for the setting store (located in "C:\ProgramData\StableBit Scanner\Service\Store\Json") should be much more resiliant. 
in fact, I tested out copying the folder elsewhere, nuked the settings, and restored the JSON folder.  I did this on my production server, and can verify that it works.  So, if you backup the folder in question, you setting should be safe, from here on out.  

Well, I don't mean to minimize the issue, at all.... but this generally happens to a small group people (or at least, that's how many report it).   So it doesn't seem to be a wide spread issue.  Which ... means it's pretty rare, and ... that it's not as easy to track down. 
That said, 
We've looked into this issue in the past, with little success Alex is planning a "deep dive" to look into this issue ( @Mick Mickle, I believe Alex mentioned that to you in the ticket, actually), and we've talked about this The new JSON format for the setting store (located in "C:\ProgramData\StableBit Scanner\Service\Store\Json") should be much more resiliant. 
In fact, I tested out copying the folder elsewhere, nuked the settings, and restored the JSON folder.  I did this on my production server, and can verify that it works.  So, if you backup the folder in question, you setting should be safe, from here on out.

Check the Autostart tab of the Task-Manager. It should have an activated entry “StableBit DrivePool Notifications”.
If its status is deactivated, then you need to toggle it to activated.
If the entry is completely missing, you should repair the DrivePool installation or reinstall.
If the entry is there and active, but no process is running, then something is preventing it from running, most likely a virus protection software, or it’s crashing for some other reason. In that case you maybe find some details in the event logs or the virus protection logs.

So then, it's the StableBit DrivePool metadata that is duplicated then.  This ... is standard, and it's hard coded to x3 duplication, actually.
We don't store a lot of information in this folder. But reparse point info IS stored here (junctions, symblinks, etc).  So if you're using a lot of them on the pool, then that would by whey you're seeing this behavior.  And in this case, you don't want to mess with this folder. 

I used Z once, only to find that the printer with some media card slot wanted it itself or would not print at all. Same for some Blackberry devices caliming Z. So yeah, hi up but not Y and Z.
I use P, Q and R.

Sorry, I missed that.  It's been super hot here, and I don't deal well with the heat.  I'll try to make sure I'm better.
Also, I did pass this information on to Alex.  The NVMe 1.1 may or may not be the issue.  Eg, we may want/need to implement it as well, or it may be a red herring. 
As for the SATA based one, if you use the DirectIO Test tool, see if any of those actually get the SMART Attributes for the drive:
 

Which isn't a bad idea.  But personally, I don't like using Z, since ... that seems to be the go to for mapped network drives. 
But as long as it's further along in the alphabet, it should avoid this issue. 

It means the pool drive.  And yeah... how Windows handles disk/partition/volume stuff is confusing... at best. 
For this ... take ownership of the folder, change it's permissions, and delete it (on the pool). 
Then resolve the issue.  It should fix the issue, and shouldn't come back. 

I assign all my pool drive letters in reverse, starting at Z.  Seems to help avoid issues like this.

It's best to deactivate first.  
While, usually, you shouldn't need to deactivate in this circumstance, the reinstallation process can change some of the information that we use to identify the system.  So it's better to deactivate first, since that takes like 30 seconds.  Otherwise, if it doesn't activate on the new install, you'd need to activate the trial and then contact us. 

This is a Windows issue, actually.  It auto assigns the drive letter, and can bump the letter like this.  
 
The best recommendation here, unfortunately, is to assign a letter that is much further along in the alphabet (such as "P:\" for Pool, or "S:\" for Storage), as this should prevent it from being reassigned a letter. 

Sounds like you might need to rebuild the Windows thumbnail cache.  It's a good thing to do periodically even if you aren't having problems.  You didn't say what OS you are on, so I'm assuming it's W10.  Here are some instructions for doing both the thumbnail cache, and icon cache.
https://www.thewindowsclub.com/rebuild-icon-clear-thumbnail-cache-windows-10
 
Separately, I use a shell extension called Icaros, which gives Explorer better control and caching options for thumbnails (including indexing of specified folders).  If you've cleared your cache and Windows still isn't displaying them properly, you might give it a try.

This should be fixed in the release version. 

Windows Server Essentials DOES NOT require CALs.  It includes access for a number of systems/users built in.  Though that number depends on the specific OS version.   Unless you're going past that limit (25 or 50, IIRC) then you DO NOT need CALs.  Period. 
I think you're misunderstanding.  The 2 concurrent logins isn't for users accessing resources on the system, but for login sessions. Eg console login (mouse, keyboard, video) and Remote Desktop.   You have have all 25 users logged into their own systems, and accessing resources without any issues. 
That's some Grade A screw up. It's 1 system, 2 Processor sockets. 
https://docs.microsoft.com/en-us/windows-server-essentials/get-started/system-requirements
So please ignore whatever this says. It's wrong.  When in doubt, go to Microsoft
Welcome to Microsoft Server.
Joking aside, see above.    It's two users logging in, not a limit on accessing devices.  
Because I have 8 different machines all connecting to the server, over the domain.
Next time, put an @ symbol before my name. It tags me and lets me know. 
Eg @GDogTech or @Christopher (Drashna) 
 
That's the problem with buying retail. It's much more expensive.  OEM is better, but ... harder to get, and has other (licensing) issues.

I've updated the article to reflect this, so it shouldn't be an issue in the future.
 
 

I've decided that when my next server upgrade happens (in 1-2 months) I'm avoiding server versions due to pricing, in favor of W10 Pro.  Being a home-based small business IT professional and not truly needing a domain or it's features (just a large file/media server), it'll suit my purposes while being flexible at the same time.  And no need for Storage Spaces or ReFS means I'm not truly losing anything I need.
My personal opinion is that MS is losing out on a segment of the market with inadequate pricing models for home professionals.  I'd gladly pay 2x or even 3x the price of W10 pro for a suitable server version with limited CALs (or non-domain model).

Well, you can click the above link, for the response, but for ease: 
 
Basically, because of how the driver works, Windows itself is what doesn't register the activity, basically. 

Still happily running WHS2011. The only thing I am missing is that I would like to also have a desktop replacement as a VM so that I can work off of a very light laptop (which WSE does not offer either though). AFAIK, WHS2011 is still supported for security and will remain so until somewhere in 2021. I intend to go Windows Server Essentials (WSE) anytime before then. Might be tomorrow, may be 2021.
AFAIK, WSE 2016 is a lot like W10, GUI wise for sure. WSE2012 is much like Windows 8. But consider this: If you go 2012, you will face end-of-support earlier again. I'd go WSE 2016 and there are cheap versions out there if you look for it, albeit a bit shady (I had an issue with a similar Office license).
AFAIK, WSE has a dashboard and Scanner and DP will be visible in the dashboard. Having siad that, when I want to check DP, I choose the DP directly, not through the Dashboard.
My main issue with WSE 2016 (and the same goes for 2012) is that you actually need to know quite a bit more about it. For instance, all clients will join the Domain by default, unless you use a Registry hack. I don't even know what a Domain is, why I should want it and how it changes the user experience for my small group of IT-illiterate users. Then there is that WSE will establish itself as a DNS server. Should be fine if it is on 24/7, liek with me, but how do I look for online help if on a client if the DNS server is down? Things like that bug me. WHS2011 was/is simply very simple to use and if you want to you *can* make it more complicated.

Awesome, glad to hear it! 
For all of this: 
https://stablebit.com/Support/CloudDrive/Manual?Section=I/O Performance
The reason that my suggestion worked is that it's less threads grabbing much more data. That means a bit more latency (since it's waiting on more data, at once), but there is less overhead (HTTP, REST or other API calls, basically).  And the Prefetch Time Window is the ... window for the trigger to occur. You want smaller here, so that it only prefetches on larger, sequential reads. 
For the upload threshold, this stops uploads from happening if data is still being written.  This means that uploads should happen less often, but should get whole chunks of data, rather than uploading the same chunk (or parts of the same chunk) again and again, wasting API calls, basically.  So, this is an optimization, and should be fine at it's default. 

"ipconfig /flushdns" from a command line should work, as well. 

Yup, sounds about right.

You've posted a ticket about this and I've already replied. 
That said, it sounds like a balancer moved all of the data of of the drive.
And the most likely culprit would be the StableBit Scanner balancer, and maybe the Drive Space Equalizer balancers. 

You could do it with a combination of a VPN, Drivepool pool(s), and Clouddrive using file share(s).  Here's how I think it could work:
The VPN connects all computers on the same local net. Each computer has a Pool to hold data, and the Pool drive shared so the local net can access it. Clouddrive has multiple file shares setup, one to each computer connected via VPN and sharing a Pool. Each local Pool can have duplication enabled, ensuring each local Clouddrive folder is duplicated locally X times. The file shares in Clouddrive are added to a new Drivepool Pool, essentially combining all of the remote computer storage you provisioned into one large volume. Note:  this is just me brainstorming, though if I were attempting it I'd start with this type of scheme.  You only need two machines with Drivepool installed and a single copy of Clouddrive to pull it off.  Essentially wide-area-storage.

As for the pool itself, yes, it should be picked up automatically. 
If it's not, check Disk Management, and make sure that the drives aren't showing as "offline".
Also, on the system that is having issues, try resetting the settings, and see if that helps:
http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

I hadn't realized it was a different discount for products you do own, vs products you don't.  That's great to know.  More purchases incoming...!