Thanks for your bug report. The way control+break works has been through quite a few changes over the years. Unfortunately, Windows does not allow a busy/non-responsive window to become active. This means that if a script is running that makes the mIRC window busy/non-responsive (a common occurrence for long running scripts), it can no longer detect control+breaks unless it does so globally.