Please re-install patch v1.0.20 if you have this issue. It's up on the vault. I removed v.27 because this problem seems to affect lots of people so we think it indeed got introduced in some cases by the patch. We'll look into those cases more closely and fix them, and re-release the patch when it's more reliable and more QA'd (which is becoming increasingly more difficult so I'm not blaming anyone here
).
