Exactly the same problem here...
it would be nice to hear from Parallels if the problem is actually being looked at and what release cycle a fix is expected in... i hate to use the f-word (as in the vmware ;) ) but before i switched to parallels i had a similar bug, reported it and a patch was...
