Regarding Microsoft article Q176684: is there a workaround or patch available for this problem?