Ok. So at least we have a workaround. But now I'm afraid this happens for everyone for this update 440.100 --> 450.57. :-(