That's what's pissing me off the most: they haven't even acknowledged this problem yet, nor have they responded to any of the many threads reporting this 10102 error.