This is why user-to-user support is so problematic. If you’ve seen the error before and trust me, after seeing it every second day for months on end, you’ll know it when you see it, you’ll know that it’s not a simple config issue. Hence not adding links. Why? Because, if you’ve seen the error, you’ll know the issue. If not, you are highly unlikely to know about it, despite your years of IT experience. So, I asked if anyone had received a response from Apple, not for fault finding. Why? Because the problem persists with lots of people. The thread is then hijacked by well meaning individuals whom would like to help. I get that but I’ve spent hours with Apple’s technical support and I’m not about to transcribe the material here. Why? Because the number of people (yes, ‘lots of people’ as condescendingly quoted by Kurt) that this is happening to is increasing and this appears to be a hardware issue which could potentially amount to a defect issue. So, whilst I understand this may be fun for some, it isn’t for me. It’s incredibly frustrating to have this problem with a machine that’s only a year old. All I’m after here is whether anyone with the problem has received an answer from Apple. Simple. Why? Because it may be a defective product and depending on where you live, consumer protection laws are different.
