That's correct, I never had this problem before the update the night before the 27th. It appeared when booting on the morning of the 27.