Edit is in the gear icon in the bottom left of your post.
The scripts in the Mango/bin directory may have been updated. You can compare versions of the script on our Github, if you like: https://github.com/infiniteautomation/ma-core-public/blob/2.7.x/Core/scripts/ma-start.bat . I believe at some point there was an issue with how the update was being performed on Windows.
I suspect a lot of the SQL problems we're having are a result of doing the upgrades so many times. And, you're restoring from a MySQL dump, yes? Those typically begin with a bunch of
DROP TABLE IF EXISTS `tableName`; statements, so it's not dropping the tables made by previous attempts at running because they're unknown at the time of the dump! I'll raise the idea of including the
DROP TABLE IF EXISTS in future versions, but it does seem like something else would have to have gone wrong and we shouldn't presume the table ought be purged. So, in addition to potentially circumventing upgrade 10 if it fails from a clean restore, you may need to
DROP TABLE templates;
DROP TABLE jsonData;
before running the upgrades. Consider also renaming the files in your Mango/classes/ directory, log4j.xml --> normal-log4j.xml, debug-log4j.xml --> log4j.xml to enable debug logging. If you are letting the script unzip the upgrade (if it isn't just unzipped by now), though, you may wish to place it in your Mango/overrides/properties directory as log4j.xml, and skip renaming it.