Weirdness with Unity HUB and Expired Unity Licences

Hey, I've been using Unity Hub for a couple weeks now and its a great product. But I've run into one kind of obscure snag that hopefully you can find a solution for. My company recently had its licences revoked because we hit our annual renewal (or had some kind of other problem that necessitated revoking all our licences and issuing new ones to all of us). If you try to open a project through Unity HUB when your licence isn't currently active you get some kind of weird behaviours. This may only apply to copies of Unity you installed through the normal download process and then added to Unity HUB. All the copies of Unity I've been using were installed in this way as I had them installed on my computer before I installed Unity HUB and didn't want to reinstall them for what seemed like no reason.

When you click on on of the project entries Unity HUB opens up the editor as per normal. Once the Editor is open however it immediately starts a reimport of your project to set it back to a standalone Platform (I'd guess if your project was a standalone project it wouldn't do anything, but mine is an Android one). Once this process finishes it brings up a window which asks you to reactivate your licence. The window has a warning near the top of it that indicates that you will need to log in first before you can submit the licence key and the next button on the bottom is greyed out (presumably because you are not logged in).
If you try to click on the login button at the top of the window however nothing happens. The only thing you can do from here is to quit the editor.

If you open up Unity directly (not opening up a project directly but instead just opening the editor by itself). Then you will be taken to the same activate unity flow but now the login button works correctly.

Once you have activated Unity you can go to the Unity Editor project selection window (launcher window that comes up first if you open the Unity Editor directly without specifically opening a project) and open your project and everything is good to go, except that your project has been switched to targeting Stand Alone and you have to switch it back to whatever target you actually want.

I've observed this problem in Unity 5.6.3 and 2017.1.2. I'm guessing the issue lies in the Unity Editor rather than Unity HUB (Hub just makes this pre-existing issue much easier to stumble upon).

Hopefully, you can modify hub to be able to detect if an installed copy of Unity isn't currently activated and either activate it with the credentials you put into HUB itself, or at least open Unity without your project in this case so that the activation flow works correctly. As well I'm sure in future versions of Unity you will make the interaction between HUB and the Editor even smoother. But some of us are stuck with having to interact with older versions of Unity here and there to work with older projects now and again so it would be appreciated if you could fix this for both newer and older versions of the editor.

Overall HUB is a great addition though, thanks for making it!