Another session for your user is blocked notifying Local Session Manager for 0 minutes

Question

I have hyper-v VM running on my win-10 laptop. After some time, when I resume the VM after I was temporarily off, I get a message:

Another session for your user is blocked notifying Local Session Manager for 0 minutes so we are unable to log you in.

Do you want to force logoff that session to continue?

Why I'm getting this message? How do I continue in that session instead of forcing logoff?

Answer 1

Hi,

Thank you for your posting!

Based on your descriptions, I guess you may have multiple user accounts and the error message indicated that more than two sessions (user accounts) were trying to log in your VM at the same time, or different users logged into your VM successively. So I may need more information for your issue:

1) How did you log in to your VM, by Hyper-V Manager or by RDP?

From my experience, you can only make one console connection to a single VM at a time. I believe this was an option in Virtual Server but is now enforced for security reasons for recent versions. So you may need to tell me more detailed information about your login environment.

2) Is this the first time that you encounter this issue?

3) If you have multiple users, what exactly did you do before this problem occurred? For instance, every time you switch users, will the next user log in like this? Or every time the previous user logs out, the next user logs in and prompts this?

4) Can you click 'yes', close the session first and then try to restart your VM?

Thank you for your support!

Best regards
Joan

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The same problem was with me ,,, I created VM without login password,
But after creating a login password the problem was solved.

Answer 3

Hi,

Thank you for your reply!

Based on your descriptions, can you first go to event viewer>> Applications and Services Logs>> Microsoft>> Windows>> Hyper-V VMMS, to see if you have any other error messages or codes related to your issue. If not, then your issue may be concerned with your VM itself other than Hyper-V host.

Thank you for your patience!

Best regards
Joan

--------------------------------------------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Daniel, et al. It seems a "simple" answer to the Force logoff question may have been overlooked.

Could it be the software was "less sensitive" to whether the incoming connection (that's you) is Local [i.e. connecting to the VM on your Local Host] or Remotely [i.e. connecting in from another computer either on the Local network -or- across the Internet]?

Virtual Machines (VMs) once they have established a User profile for any given session WILL (I believe) work to maintain that "session" until commanded to logoff and 'end session' by the User.

Why the VM simply couldn't 'connect to' the already established session IS the big mystery! ~ Asking which "bit" such as a Cookie, local soft "token" or temporary O.S. Registry setting are what identifies YOU (your incoming session) from the previous 'connect' would have been my next question to ask?

So, it seems you asked a good question but that this "behavior" may have been entirely normal in nature, unless since the time you posted the question (in April 2021), you managed to identify and confirm another-choice [option, setting or preference] that caused the Force logoff message to stop happening?

I hope this reply helps a little bit. (If nothing else, it confirms the issue "lives on" still, from the time you asked it.)