Microsoft has addressed the issue now with the release of the August 2011 Security updates.

More details can be found in the original article, which has now been updated with a resolution.