Microsoft confirmed the issue yesterday afternoon in the advisory EX1528992, and early this morning began rolling out a fix ...