Windows 10: Hyper-V Connection Lost

I am having trouble establishing a stable connection to a Windows 10 VM and the issue appears when I activate enhanced mode. The error message that I'm getting quite often is the following: "The connection was lost because another user connected to the virtual machine." There is no one else connected to it. After doing some research online, I discovered that others are also experiencing this issue. For what it's worth, Windows 8 is the host OS and one of the suggestions was to install the optional Windows update KB3071740, however that did not solve it. Has anyone found a workaround? It is frustrating not having the ability to run Windows 10 in enhanced mode in Hyper-V.

:)

 

Installed Latest Windows 10 Update this morning... Problems connecting to Network Share

This morning I upgraded my Windows 10 Pro to version 10.0.10586. This particular machine has 2 network cards and I run Hyper-V. After upgrading I lost all network connectivity. After some goofing around with Hyper-V I was able to set one NIC as the Hyper-V
switch and the other NIC for the host machine. All Hyper-V machines seem to be working okay.

The problem I have now is, though I have network connectivity, I cannot connect to any of my network share drives. Does anyone have any suggestions? I am at a loss.

 

Windows 10 guest virtual machine on a Surface Pro 4 using Hyper-V.

There is no such permit in the Windows 10 End User License Agreement. You will need to purchase an additional license to install in Hyper-V just like you would for a virtual machine.

Setup a Virtual Machine with Windows 10 Hyper-V - groovyPost

also

Share Your Network Connection with Hyper-V in ... - groovyPost

 

Do you have a password set for the user of the account in the Windows 10 VM? If you don't then it will keep disconnecting you.

I had this problem last week and I'm sorry I can't find the link with the reason but my connections (through both RDP and console) are much better after adding one. They still time out but don't disconnect any more.

 

I had similar problem, got solved once I set VM user password.

 

thx setting a password for the logon ID also solved the problem for me too

 

Just for posterity and future readers of this thread:

Hyper-V Enhanced Mode is based on RDP (Remote Desktop Protocol). Remote desktop connections by default, including Hyper-V Enhanced Mode connections only work with accounts that have a password set.

If and when you do not want to set a password for the user account needed to sign in to a Hyper-V vm, you can't use Enhanced mode and need to switch to basic Virtual Machine Connection view (in vm window, open the View menu and unselect Enhanced Mode):




Notice that when the password is set and Enhanced Mode used, you need to use password to sign in to your vm; You cannot sign in with PIN even when set. To sign in with PIN you have to exit the Enhanced Mode.

If you have multiple user accounts set up in your vm and you are signed in on an account with password in Enhanced Mode and you then switch user on that same vm to another account without a password, you need to stop Enhanced Mode and return to basic Virtual Machine Connection view. In other words, the Enhanced Mode can work with a user account on a vm but not work with another user account on that same vm depending on if the current sign-in account has a password set or not.

 

Same here, setting up password on the user solved the issue (silly issue if you ask me).
Thanks for the tip *Wink

 

I'm trying to use a Windows 10 VM to make a manual image via SCCM and SCCM requires that the account has no password set or it wont work! Madness! I've un-ticked Enhanced Mode on the View menu and all seems fine for now.

 

So it wont have disconnections without Enhanced mode?
Kari - your thoughts/ experiences?
Anyone else?

 

This is very clear and simple:

• Hyper-V Virtual Machine Connection normal mode
  
  • Can be used without issues (not disconnecting a running session) with a vm running any Windows desktop or server version as well as with any Linux version regardless of bit architecture
  • Sign in user account may but don't have to have a password set
    
• Hyper-V Virtual Machine Connection enhanced mode
  
  • Can be used without issues (not disconnecting a running session) with a vm running Windows 8 or later desktop version or Windows Server 2012 or later server version as well as CentOS 7 Linux or later and Red Hat Enterprise Linux versions
  • Enhanced Mode works with both bit versions of supported operating systems
  • Sign in user account must have a password set

 

Actually, Enhanced mode does in fact work without a password. As in, it allows you to enter Enhanced mode, and login (which RDP alone doesn't allow you to do).

The problem appears to be that the VM client tries to re-open the non-enhanced session at the same time, which if you don't have a password set causes it to re-log you into the non-enhanced console automatically. This causes your Enhanced session to be terminated again, since Windows only allows one login at a time.

It didn't used to do this, this was something that started happening in recent versions.

 

I repeat: Hyper-V enhanced mode requires Windows sign in account to have a password set. You can get it occasionally work a while with an account with no password, but it just keeps disconnecting.

Stubbornly trying to use it without a password is waste of time when the solution is so incredibly simple: set up a password!

 

Yes, but this is not the same issue as RDP without a password, which you stated in your original message.

RDP does not allow logging in if there is no password. The Enhanced mode problem seems to be a bug, they are two different issues.

 

Enhanced Mode IS fully based on RDP, build on it. Enhanced mode does not work with user account without password. It is not a bug, it has been like that as long as we've had Hyper-V in desktop versions of Windows.

Only difference in remote sign in process is that when Enhanced Mode is launched, there's already an existing connection from host to vm, system tries to use the sign-in info from that existing session to create RDP based remote desktop connection (a real no-difference remote desktop connection over vmbus) to remote host (virtual guest) waiting existing currently signed in user to enter the password.

User must be a local admin on guest OS (remote host), or belong to remote desktop users group. A standard user not in remote users group can in no circumstances use enhanced mode.




When a user without password has been added to remote desktop users group, sign in most often works for a while, then Hyper-V starts disconnecting it. I can simply not understand why it is so difficult to understand that it will work perfectly when password is set and you sign in with local admin account.

Notice that OOBE must be done to use enhanced mode; if you boot to Audit Mode with built-in admin credentials before initial admin user is created, enhanced mode will never work. It will come available after OOBE is finished, a local admin created and user has signed in first time.



It most definitely is not a bug.