Hi Ahmad, thanks for reporting these issues.
The first issue is a problem with the .NET DPI support. I'll try to get a fix in for it, but as you can imagine it's not the highest of priorities.
The second appears to be a genuine bug, the button was accidentally disconnected from the code that handled it during the UI update! That will go into the 2.4.1 release soon, thanks!