Sorry for the double reply. Check this video, around 8:45 - someone managed to reproduce the issue, under different conditions, with the update in question. There’s also a second problematic update.