@shawnblais, "known issue" doesn't necessarily mean "a fix has been found", nor even "the cause is known", merely that they observed the symptoms themselves at some point.
And "seems to affect everyone in different ways" is exactly when it's best to look for patterns in things like systems specs, patterns of use, and so forth.
It's also important to identify the distinct failure modes. So far I've seen at least three types of "freeze" failure reported, with only one of them being an actual freeze.
There's the one where it sits forever on the BlackBerry splash screen, though that's not a true freeze as the little Cylon progress indicator keeps moving. (Edit: or does it? I haven't seen it, and maybe just assumed it's not really a full freeze.)
There's the installer filesystem problem which I tied to allocating too small a virtual disk size.
And there's the real freeze which occurs after everything has booted successfully, when running an app. This one may be related to us changing focus back to VMware by clicking, with some reporting improvements by using Ctrl-G instead of a mouse click within the VM window.
And I'm not sure when Elena said it's a "known issue" which one of those she meant, or whether it was possibly even a fourth case. Do you? (Edit: it seems pretty clear from the first message in this thread that she meant the one we all see while running apps, not the "stuck at splash screen" issue. So even if they know what causes the freeze, they may not have reproduced "stuck at splash screen" themselves, nor know what causes it.)
