" … but I imagine the fix is going to be on your end. … "
I think you must have a vivid imagination. You might be right, but consider:
Many of the client systems that are complaining of this issue are newer, well equipped systems - most of them working previously.
They haven’t changed. What has changed? WoW has. This issue has been repeatedly reported by a significant number of individuals.
That your folks cannot reproduce the problem on you local clients is immaterial. There are more and wildly different configurations out there - you’ve seen a number of DXdiag posts that show what they are. You can’t discount that just because “your clients” aren’t affected.
You suggest that our client systems are mucking up the cache. Really?
These systems that were working fine before the code update are, all of a sudden, misbehaving? It just couldn’t be the new code, could it. Inconceivable!
Then, you suggest that our systems might not be up to your new minimum requirements - numbers that look really impressive. But, remember: most of these systems were working fine previously.
You’ve just raised the bar and discount these clients based on an arbitrary standard. Which means you can feel free to ignore the issue - “… don’t think it’s a bug …”
We did the troubleshooting. Most of us have determined that deleting the Cache folder will allow us some play time. But, it shouldn’t be a regular part of getting WoW to run. Besides, the problem comes back.
And, who is it that tells our clients what to do to rebuild the Cache folder? You do. You tell us what to put on our disk. After it’s re-created, you tell us how to update it.
Is it so unbelievable that this creation/update process is what’s broken?
It seems much more believable than every one of our systems are suddenly “broken”.
We think you need to look a little closer - a little closer to home.