This problem is fixed in .69 build. We actually uploaded 2.5.69.0 build two times today. The first one had this bug, then after we spotted it, the bug was fixed and with in 10 minutes we re-uploaded the build. Probably you downloaded the first one. The build available for download have this problem fixed.