This issue has not been resolved by the update that you received today. The fix is projected to available March 5.
