This problem just came to my attention last week (sorry... been busy). So, I asked around a bit to find out what was going on.
Apparently, one or more of the folks who got Mr. O'Brien's email to "WinDbgFb" was interested enough to follow-up on the problem. My sources tell me the problem is recognized, and that the fix is in progress. The fix apparently involves a ton of work. It's not merely a matter of grabbing the right symbols and publishing them.
In terms of a time-frame, no estimates have been released or even committed internally to the best of my knowledge. But the best guess by my sources was that we should see a fix hit the symbol server in the next week or two. I wouldn't be surprised if it took longer than that.
But the main message here is: People know about the problem, they understand the problem, and somebody's working on the problem.
I think we should all recognize that it's pretty cool that MSFT is fixing the problem, and not just saying "yeah, sorry... we'll fix that going forward." Especially given the amount of work the fix apparently requires.
Now you know what I know,