Thanks for the notice.  I'll change the ShowLoginAndAuthUser() method to prevent the session from locking automatically.

By runtime only, do you mean by just double clicking on the exe in explorer? If yes, then it is reproducible that way, i.e. the session times out, leaving two login forms.



I'm running Win2K sp4.



The workaround is to pause and resume session monitoring around the login call.

No.  Can you reproduce this through run-time only?  I have never seen this and we have had our QA people ALL over this lately and has come out of QA with a clean bill of health .  The only thing I can think of is that the VSHOST may have launched it as well or the F11 key was hit just milliseconds before it was going to time out (which is probably unlikely).

I was about to test something, so I started the app, then got called away. When I returned, there where two login forms to sign into. I'm thinking that the session timed out, so first I had to unlock the session, then I had to login (which was the only form open when it timed out). Is this the way it is supposed to act?