Originally Posted by HarryT
It was. That was the v538 update they were talking about, which seems to have been released around mid Jan, although not publicised. The bug was fixed in the v538 build.
And yet I bought mine in mid december and it came with the v538 already installed, and of course it doesn't fix the problem. So I'm thinking that they were talking about this update.