I can help you with the first issue, because I've been experiencing the very same behaviour since the 10.15.1 update. The workaround works (sorry for the unintended pun) as follows.
First, let Mac OS start the upgrade process as usual. Then, after the second reboot (that is, the one following...