Hello,
We have investigated the problem and it occurs because of the keyboard rate that causes the application to get stuck.
We will find a solution for changing the keyboard rate before the game starts and restore the keyboard rate when the game ends.
In the meanwhile, you can check your EXE export by changing the keyboard rate to something like that:
Here is an explanation for how to do it:
bltt.org/adjust-windows-keyboard-repeat-rate/
When you finish testing your game, restore the keyboard rate.
We hope to find a solution soon to do it automatically for the EXE version of export.
Regards,
Cyberix3D team