This is a known issue and we have already escalated this to our R&D. At the moment, we do not have any ETA for this to be fixed, but we added your request to our internal task associated with this and we will keep you posted on the status in the future. In the current implementation, this can't be worked around or fixed by changing any settings in the CloudBerry Drive configuration and the only way to resolve this is to restart the machine.