In response to those who said the above did not answer the question, my entry sheds more light on the issue (I cannot provide comments). It looks like the answer will be for MS to fix this issue.