Sorry but 1.04.0a was not packaged correctly and as such the DB schema update would have probably failed.
In investigating this but I also found a bit of a pre-existing problem with the build process for the schema without drop tables. This would have perhaps affected users updating when new tables are created but they would have been fine from a second update onwards.
Both issues are now resolved and anyone running 1.04.0a as from an update should update to 1.04.1a.