Okay ... I think it is clear now that this issue is present on multiple machines. Can we please stop the ongoing "same here"...