Answer

Microsoft is working to resolve this in future releases. Please refer to the Microsoft KB article 2026022 (http://support.microsoft.com/kb/2026022) .