I was hoping they would have sorted it by now. It's been doing it for a least 2 software updates (the first being the one that should have resolved it I thought).
The reason I didn't think it affected a lot of machines is because when I've searched on the web, I've not found a similar problem. This is the first post I have seen which is the exact problem I have. Therefore, I thought it wasn't that common. However, I'm almost glad that it is common, as it might hopefully get resolved eventually !!
