Having the same issues here. The proposed workaround (open the EXE via the folder structure) does work but is less than ideal. Have the devs or anyone yet explained why this error is occurring and when the fix will be made available?
Experiencing the same bug here with ticket #76724 - partly relieved that it isn't just me but I hope this gets resolved as I was one day short (19/20)...