Hi there,
So the crash on sync, not exactly sure what might be going on with that. I do note as @Adam Stanger pointed out that there are issues with folder/design names that contain special characters !@#$#% etc. That will be fixed in an upcoming release of Siteworks, as are some other fixes for non standard time formatting (e.g. Denmark formats dates in a unique way that previously caused issues). In general if you are seeing consistent crashes when doing a particular workflow that is repeatable, I would definitely encourage to get with your Sitech and put a support case together where the crash logs and data are sent in to Trimble support. That is the best channel for us to get crashes reported and also start a solution process. Also just as an aside, if you leave the "Send Diagnostic Data to Trimble" checkbox on, we do look at those logs and try to fix issues that are automatically reported around the world.
As for the "Siteworks is already running". I have seen this too, sometimes it's caused by relaunching Siteworks right after a crash, before the prior instance is killed by Windows. So waiting a few seconds before restarting Siteworks can alleviate this, and if it's being particularly stubborn, doing as @Matthew Pitt suggests by looking in the task manager and killing any Siteworks instances should get you back and running. And if you have the luxury of time, a fresh reboot, while not always necessary, can help just start fresh.
And as for the Text not appearing, that's going to be due to the way Siteworks handles multiline text and the different types of source software. If you have some particularly egregious examples of the text not showing up you can please work with your dealer to put in a support case, and then the development team can look into that.