when i updated to v7.06 beta i got this error, and my fix fixed it.

Note: you should avoid using the method I used here, and rather use ScanMessage. Changing the windows procedures prevents all the default things like keystrokes from being detected unless you code them yourself. See my post on ScanMessage in Lite-C Scripting/Win API with Lite-C pure mode