Description of the need While working on https://github.com/backdrop/backdrop-issues/issues/3979 I realized that the updater throws exceptions at an early stage of the process, when there's nothing broken (yet).
This might be confusing for admins, especially Backdrop novices, because an exception usually means, something's broken really badly. And that's not the case at that early stage of updating (files got downloaded and extracted, the install itself is untouched).

Doesn't this look like this Backdrop install is broken? It isn't.
Proposed solution If nothing's actually broken, it might be better to abort the update and show a helpful message. Log detailed information, possibly with links to documentation. We also need to consider that updating happens in batches. The fact that one project fails, doesn't mean all of them fail. (But that needs some more recherche...)
Alternatives that have been considered Sticking with UpdaterExeptions.
Recent comments
I am considering migrating my drupal 7 website to backdrop. Hi @seamus, I would like to offer my professional services for migration to BackdropCMS. Please connect If...
drupal 7 to backdrop migration
Restore Newsletter Subscriptions from a Database Backup One of my websites was affected by the Simplenews issue, and there were many incorrectly disabled newsletter subscriptions of '...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
This is the report about the recently discovered bug: https://github.com/backdrop-contrib/simplenews/issues/83. First, how do you know if your site is affected? In other words: Are there...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled