2009-09-02, 03:49 PM
Just to update, Microsoft has applied an update for this problem. The resolution can either be auto applied or manually. View article 973879 in the Microsoft Support database for more information

