It looks like you're new here. If you want to get involved, click one of these buttons!
In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
Since upgrading to 18.104.22.16845, I have been experiencing a recurring issue that seems to be triggered by a problem with DrivePool. After writing a Word document for a period of time, I eventually encounter a problem where Word stops responding when I save the document apparently because the DrivePool is suddenly inaccessible. The document is actually saved (I can open it with the changes I have made being there after a reboot), but Word is frozen in the saving process, and I cannot even kill the Winword.exe process. Have had the same experience when trying to read a file from the DrivePool at other times.
The DrivePool Service says it is still running in Services.msc, but Windows Explorer also stops responding when I try to access my pooled drives once Word has stopped responding. The only way I have found to recover is to completely reboot the system, which causes DrivePool to report almost nothing is duplicated in the Dashboard and to run a lengthy duplication.Then things work normally for awhile until the problem recurs with either reading or writing.
I have submitted a support inquiry. Is anyone else experiencing anything like this?