Hi Darryl, this bug is fixed in the last internal build. Please check it out and us know how it goes.
What are the other variations of this Known Issue? If so, what are the other workaround Telerik have been advising user to do? Note: I am the one who filed the ticket that started this thread: http://www.telerik.com/account/support-tickets/view-ticket.aspx?threadid=856190