Hi! For months I have been suffering from not being able to launch Unity Hub versions 2.1.3 and up, along with Unity Editor versions 2019.2 and up on my MacBook Air, 2013. They just crash at startup. For a temporarily solution, I managed to downgrade to Hub version 1.6.1, which still works fine even on MacOS Catalina. But even with that, the latest Unity version I am able to run is 2019.1.14. But now I think I have finally figured out the reason causing this; the lack of proper hardware serial number on my MacBook. After I upgraded my ssd some time ago, the serial number present for example in the "about my mac" menu went missing, "Unavailable". And I don't believe I can do anything about that, sadly. Luckily almost none of the applications actually even require the serial num, so up until now, it had caused me no trouble. Until Unity Hub 2.1.3 / Unity Editor 2019.2. From the crash reports, I have found the line which explains the crash: "2 .com.unity3d.unityhub.kS13hK 0x000000010f32561c systeminfo::GetDeviceSerialNumber() + 99" I believe, that in my case, the GetDeviceSerialNumber() function yields null, which causes the startup to crash I found other instances of this same crash on these forums, for example: https://forum.unity.com/threads/2019-2-5f1-editor-won-t-start.746279/ and https://forum.unity.com/threads/unity-hub-not-opening-on-mac.523544/ (the same exact problem, at the end of the first page, has even screenshots to demonstrate what we mean by "serial number" etc.) I have no idea why you guys at Unity have chosen to start checking device serial numbers now outta nowhere. But could you PLEASE add a null check or something else there to let use latest versions of your products without crashing. I hope this gets fixed asap!!! Thanks in advance if/when the fix arrives, for both the hub and the editor!