This bug appears to have been fixed in the update that was made available this morning. I am no longer seeing the error.
