If S4T is updated with TBs built-in update mechanism, it might be possible that it is restarted too fast (especially on TB2). Too fast, because if Spamato is still running when TB tries to delete the old S4T version, it might fail as S4T is still running (it takes some time to shut down) and the JAR files are still in use (at least on Windows).
To prevent this, we could try to copy the JAR files to the user's spamato profile directory and start S4T from there.