Sorry for resurrecting such an old thread, but how can it be that this 'fix' from over 2 years ago still means the issue is recurring, this time 31st May/1st June. Surely there must be a patch out...