Hi David,
Thanks for reporting the issue. For the 1.0 release, we upgraded the RocksDB library from 4.11.2 to 4.13.4 to get a few improvements. However, one drawback with 4.13.4 is that it seems when errors occur with RocksDB, the messages reported from the library are cryptic, to say the least.
You should have a rocksdbjni-4.13.4.jar in your GeoGig lib directory. Please back that file up (copy it someplace you can easily find it again and remove it from the GeoGig lib directory), and copy the above 4.11.2 Jar into the GeoGig lib directory. Once done, if you could retry your GeoGig clone on Windows and report back if you get any errors, and if so, the error logs similar to what you have reported here.
I don't think downgrading this library will fix the issue, but I am hoping that the error message you get out of the RocksDB library is more informative about what is happening when it fails. In the meantime, I'll add an issue to the GitHub page and see if I can reproduce the issue myself.
Many thanks,