This is great news. 
It appears that @theoutside sent you a very recent build. I would be curious to see if others who are experiencing this problem can solve it by updating to the latest Service Release Candidate. I would appreciate hearing back from anyone who does this and finds it solves the problem (or not).