I realized that this problem was reported almost a month ago when I read this thread https://www.wilderssecurity.com/showthread.php?t=241025 and I bet they had a copy of sp2 before most others did. Surely they experienced the same bug on during their testing...its not a rare bug that only pops up for a few people. So they must of been working on a fix since the beginning of the month and its shameful they didn't blow the warning horn before sp2 was pushed out, instead they waited and pretended that the bug was a big surprise! If they haven't figured it out yet I don't think they are going too. I think they are stalling and they need to come clean and tell everyone that it can't be fixed without rewriting half the code.