This bug was confirmed by Microsoft after we opened a "Severity A" issue on it. The original response from the support guy was : "oh my god!" :) because this kind of bugs are really easy to track down in a superficial QA testing. Eventually the support guys couldn't help us and...