This just happened again after another system update, but there was no firmware update involved. So I think we can rule that out.