There was an article posted on CNET about Microsoft admitting that this was a problem of theirs, however the article also said that it was limited to the US Sprint Network and a "small subset" of users.
Here's another article:
http://www.wmexperts.com/microsoft-r...hones-affected
So they've acknowledged the problem and are working on it. So much for a quick and quiet fix...
If you're having problems why not just use the workaround? At least it takes care of it for now.