Okay, lets try typing in this response again - the first time around after a whole paragraph I hit Post and the web site just threw it all away!
So, A couple months ago, after getting no response on the multiple forum threads where this issue was reported, I contacted customer support directly, and corresponded with a Thomas Bell several times, giving lots of details, what I was doing, and even several screencasts. Refer to CaseNo:17933792
He opened a Feature Enhancement request, FUS-85452, even though I kept trying to tell him it was a bug not a new feature - at that point he stopped replying to me completely.
More recently I happened to see your instructions for this workaround, only since I kept looking in the forum and kept trying to get a response. I never got any further feedback on the case or the feature request, though you make it sound like others have gotten the instructions and it worked for them. It worked initially here, but as I said it then reverted back to the broken situation.
I have repeatedly asked if it would help to send in log files, no reply. In addition, would it help for you to see what my cache folder has in it? Something obviously gets corrupt, or there is a path it doesnt like, something. Whatever this new version will be, if it is built on that same cache functionality it may well break it again. I am trying to help things, and at long last someone has at least responded - please go the rest of the way and find out what the real problem is and fix it.
Chris