I suspect this was fixed in a more recent build. See if you are still getting this with the latest release.