Hi, I will look into this thanks for reporting it. Did you try to launch L2.exe (even though there are errors)?

EDIT: I can confirm that the bug has been fixed now. Thanks for the report!