Hyper-V Connection Lost

Page 2 of 2 FirstFirst 12
  1. Kari's Avatar
    Posts : 15,622
    Windows 10 Pro
       #11

    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!
      My ComputerSystem Spec

  2.    #12

    Kari said: View Post
    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.
      My ComputerSystem Spec

  3. Kari's Avatar
    Posts : 15,622
    Windows 10 Pro
       #13

    Mystere said: View Post
    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.

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	880.5 KB 
ID:	92101

    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.
    Last edited by Kari; 25 Jul 2016 at 21:25.
      My ComputerSystem Spec

  4.    #14

    You aren't understanding what i'm saying Kari. I understand that Enhanced sessions are based on RDP, however the problem is something different. I am not saying that enhanced sessions aren't based on RDP. So please stop arguing that point.

    If you have a user that does not have a password, and you try to connect to the PC using that user, Remote Desktop does not allow you to log in. At all. You are blocked from logging in. This is a security feature to prevent PC's without accounts with no password from being exposed on the internet.

    On the other hand, when using an Enhanced VM session, you are in fact logged in (You actually get to the desktop) when you have a user without password. However, you are disconnected right away. This is why it is a different issue and the two are unrelated.

    I'm not sure how I can be any more clear on this. They are two fundamentally different behaviors. RDP does not allow remote connections without a password. Enhanced Mode Hyper-V client *DOES* allow the connection without a password, but then you are disconnected afterwards because of the way the client seems to try and reconnect the non-enhanced session.

    This second behavior is a bug. When you connect via an enhanced session, it should not try to reconnect with a non-enhanced session. Or, alternatively, it should not allow the enhanced session to log in at all. Either way, it's a bug.
      My ComputerSystem Spec

  5.    #15

    Old thread, I'm hoping somebody is still watching.
    I've just added Hyper-V to a Windows 10 Pro (1809) system, added a VM, told it to boot from Windows Server 2019 Standard install media (NOT scripted, so it WON'T have any password set up).
    I cannot for the life of me get past the "Video remoting disconnected" error.
    I've turned off Enhanced session mode both in the Hyper-V settings Enhanced Session Mode Policy (so, Allow Enhanced Session Mode is now UN-checked) and in the Use enhanced session mode setting (that, too, is UN-checked).
    And, still, in Hyper-V Manager, clicking to Connect to the machine opens the Virtual Machine Connection window, shows just the black screen behind, and nearly immediately gives the "Video remoting was disconnected" error.
    It feels like a Catch-22. Since I can never get to the machine to finish installing it and set a password, even withOUT Enhanced session mode, how do I, you know, get to the machine, finish installing it, and set a password?
    thanks!
      My ComputerSystem Spec

  6.    #16

    Can you just start the VM from the manager, double click on the picture of the screen and when it asks what resolution just close that pop-up. It will then start as console.

    I do this for VMs I use to connect to other servers using Cisco AnyConnect when the remote server will not accept connections initiated from remote desktop and this method makes it look like you are on console. Which you are I suppose.
      My ComputerSystem Spec

  7.    #17

    Click image for larger version. 

Name:	Win10 Hyper-V Manager Click on picture of screen maybe.jpg 
Views:	1 
Size:	172.1 KB 
ID:	222679
    lx07 said: View Post
    Can you just start the VM from the manager, double click on the picture of the screen and when it asks what resolution just close that pop-up. It will then start as console.

    I do this for VMs I use to connect to other servers using Cisco AnyConnect when the remote server will not accept connections initiated from remote desktop and this method makes it look like you are on console. Which you are I suppose.
    If I'm understanding correctly, this says I should be able to click where the red arrow is pointing in the attached screen image?

    That opens the same Virtual Machine Connection window, and gives the same "Connecting to {VM name}", "Video remoting was disconneted", "Could not connect to the virtual machine. Try to connect again. If the problem persists, contact your system administrator. Would you like to try connecting again?" messages as clicking on the "Connect..." button does. :-(

    Is there another place I should try clicking? thank you!
      My ComputerSystem Spec

  8.    #18

    Tried the Win 10 Hyper-V built-in "Windows 10 Dev environment", same


    Just to see if the content of the Hyper-V guest had something to do with this, I instantiated the built-in "Windows 10 Dev environment". It does the same stupid "Video remoting was disconnected".
    Why, oh why, Microsoft, do you do this to us? .. Develop and promise useful things (like the Windows Server 2012R2 Direct Access on which I wasted days a couple of years ago, and even in sets of brand new, absolutely default virtual machines, could never get it to work) and then foist sh*t quality, unsolved, ignored problems, etc, like this on us? WHY?!

    Any further suggestions on how to get access to these Hyper-V guests running in Windows 10 Pro Hyper-V, appreciated; thank you!
      My ComputerSystem Spec

  9.    #19

    p.s. Perhaps in this thread, certainly in some others, I've seen the suggested workaround of using RDP to connect to the Hyper-V guests, bypassing the Virtual Machine Connection application. However, in the Hyper-V Manager, for virtual guests for which I still need to install the O/S, there is no IP address displayed, and for the "Windows 10 Dev environment" stock Hyper-V guest offered by Microsoft that I instantiated just to have something that more likely would 'work', although I see an IP address, I cannot get an answer to PING, TRACERT, or MSTSC from that address, even if I turn off the Windows Firewall on the Hyper-V Host.
    So, how do connect to a Hyper-V guest OTHER than through the VMConnect application?
    thanks!
      My ComputerSystem Spec

  10.    #20

    I'm working with Microsoft support on this issue. I don't have a complete solution yet, but I do have a direction now:
    I have some Group Policy settings which increase security from the Microsoft defaults, such as minimum RDP certificate requirements, security channel signing, and others.

    The Microsoft support agent had me perform an interesting test: Create a whole new, completely default OrganizationalUnit (OU) in my Active Directory, set the "Block Inheritance" property on that new OU, and move my Hyper-V test server into that new OU; then GPUPDATE/FORCE on the test server.

    And, no Certificate mismatch (Hyper-V Manager insisting on using short names, certificates being FQDNs), no "Video remoting was disconnected" errors.

    This is of course not an acceptable solution, and I'm confident that, now that we know where to look, once we whittle down the specific GPOs bringing the Hyper-V insecurities to light, we will find that Hyper-V needs to be tightened up a bit. (Another thing entirely whether Microsoft will agree, of course).

    If someone finds specific GPOs which provoke either of these two problems (Certificate Mismatch due to shortname vs. FQDN, or Video remoting was disconnected; screenshots below), please let us all know!

    Click image for larger version. 

Name:	Hyper-V Certificate Mismatch short name vs FQDN error screenshot.jpg 
Views:	8 
Size:	57.8 KB 
ID:	224650
    Click image for larger version. 

Name:	Hyper-V Video remoting was disconnected error screenshot.jpg 
Views:	8 
Size:	56.6 KB 
ID:	224651

    regards,
    -Jay
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Solved Lost Home Network Connection in Network and Sharing
The upgrade from 8.1 went smoothly, the only problem so far is that I lost my Home Network connection and don't see how to re-connect. My Home Network consists of 3 computers, an ancient XP, a newer WIN7, an HP Printer and this one running...
Hi folks, I was apprehensive about Windows 10. I know this because the upgrade icon stated for a while now that it was ready to download and install - but I wasn't. I was quite content with my Windows 7 Ultimate 64-bit OS. Unfortunately,...
When I start my computer I can see at the Windows logo screen that the WiFi is connected to my hub but as soon as I log in it drops the connection and I have to connect manually by entering the "key" even though I have ticked the box that says...
I have a desktop PC with a Gigabyte X58 motherboard and Realtek audio and ethernet apps. The first thing that happened is the Realtek HD audio manager box kept coming up and I could not stop it. I deleted the audio app and it stop popping up, until...
Solved Hyper-V in Gaming
Hi, As anyone tried Hyper-V yet, as isn't it suppose to be an emulator so we can play old games like Silver etc...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:18.
Find Us