yeah, that's a pretty well known bug. no one's figured out a fix yet, but using the "classic" windows logon is a good work around.