Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 10 Pro 21H2 build 19044.1466
       #1

    Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode


    Hi,

    I created a 32-bit Win10 Pro 21H2 Hyper-V VM on a 64-bit Win10 Pro 21H2 host, turned On Hyper-V Enhanced Session Mode as described in Turn On or Off Hyper-V Enhanced Session Mode in Windows 10, and started the Win10 Pro VM.

    The VM started in Enhanced Session Mode with Status Running but without a Login dialog and I was unable to connect to Win10 Pro VM.

    Then I switched the VM to Basic mode and the Login dialog appeared, I logged in with my MS account and Windows 10 started with internet access but without access to already configured host (local) resources and audio devoices installed.

    Screenshots are attached.

    Could someone help to resolve this issue?
    Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode Attached Files
      My Computer

  2. cereberus's Avatar
    Posts : 12,906
    Windows10
       #2

    suspenser said:
    Hi,

    I created a 32-bit Win10 Pro 21H2 Hyper-V VM on a 64-bit Win10 Pro 21H2 host, turned On Hyper-V Enhanced Session Mode as described in Turn On or Off Hyper-V Enhanced Session Mode in Windows 10, and started the Win10 Pro VM.

    The VM started in Enhanced Session Mode with Status Running but without a Login dialog and I was unable to connect to Win10 Pro VM.

    Then I switched the VM to Basic mode and the Login dialog appeared, I logged in with my MS account and Windows 10 started with internet access but without access to already configured host (local) resources and audio devoices installed.

    Screenshots are attached.

    Could someone help to resolve this issue?
    Login in basic mode, then disable Windows Hello from accounts menus. You will then be able to login in enhanced mode.
      My Computer


  3. Posts : 7
    Windows 10 Pro 21H2 build 19044.1466
    Thread Starter
       #3

    Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode


    cereberus said:
    Login in basic mode, then disable Windows Hello from accounts menus. You will then be able to login in enhanced mode.
    I disabled Windows Hello (changed to local account) and now Enhanced session mode works. Thank you very much, cereberus.

    Is this a MS's hidden feature, which MS did not (intentionally or by mistake) explain or at least I didn't find any explanation?

    Now, I have access to some host's resources, such as internal and external HDs, clipboard, but still NOT access to physical DVD drive, microphone, and web camera which I need for Skype and the like.

    Should I install a microphone and webcam driver software as I did on the host a while ago? But Windows 10 has or at least should have a generic drivers.
    Attached Thumbnails Attached Thumbnails Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode-camera-microphone-not-found.png   Win10 Pro VM freezes without Login Dialog in Enhanced Session Mode-redirected-drives-folders.png  
    Last edited by suspenser; 2 Weeks Ago at 19:34. Reason: Some screenshots attached
      My Computer

  4. cereberus's Avatar
    Posts : 12,906
    Windows10
       #4

    Re. devices, can't really say.
      My Computer

  5. jimbo45's Avatar
    Posts : 11,073
    Windows / Linux : Arch Linux
       #5

    suspenser said:
    I disabled Windows Hello (changed to local account) and now Enhanced session mode works. Thank you very much, cereberus.

    Is this a MS's hidden feature, which MS did not (intentionally or by mistake) explain or at least I didn't find any explanation?

    Now, I have access to some host's resources, such as internal and external HDs, clipboard, but still NOT access to physical DVD drive, microphone, and web camera which I need for Skype and the like.

    Should I install a microphone and webcam driver software as I did on the host a while ago? But Windows 10 has or at least should have a generic drivers.
    Hi there
    You CAN add these devices - but not "dynamically" as per VMWare or VBOX via "attach or connect device". You need to add them to the VM config BEFORE powering on the VM. Provided these are "generic USB" devices they should be OK -- I know it works for external USB drives and sticks -- not sure about webcams but if the generic USB driver can find the device I can't see why it won't work even if it needs another driver which you can presumably install on the Guest. You need to add them as USB devices (or for DVD's - as IDE or SCSI devices). If you can't add the USB device in the config file then --sorry no go.

    Note though physical disks then won't be available to the HOST as they have to be "Offline" to it. Provided your VM is operating in Bridged mode then sharing is possible over the network both FROM and TO the VM. If in NAT (default mode) then access is only possible FROM the VM . I'm not sure under NAT if the HOST can eve access the VM -- when using VM's I always use Bridged mode as it makes for much simpler networking -- even remote access over the Internet..

    Standard Network shares should be available if the user has sufficient privileges. Hdd's on the host system aren't treated as "Physical disks" for the VM. Physical disks have to be set up explicitly in the config of the VM.

    For sharing devices etc HYPER-V while has lots of advantages for all sorts of things isn't really designed for this purpose and you may well finf the free version of VMWare's vmplayer or Virtual Box more appropriate as these can dynamically attach devices.

    Remember though if you CREATE a VM on a fixed physical disk with VMWare (can't say about VBOX) wth the boot device on the fixed disk then the "USB arbitration service" gets it's knickers into a twist and you won't be able to attach devices dynamically either.

    Cheers
    jimbo
      My Computer

  6. cereberus's Avatar
    Posts : 12,906
    Windows10
       #6

    jimbo45 said:
    Hi there


    Note though physical disks then won't be available to the HOST as they have to be "Offline" to it. Provided your VM is operating in Bridged mode then sharing is possible over the network both FROM and TO the VM. If in NAT (default mode) then access is only possible FROM the VM . I'm not sure under NAT if the HOST can eve access the VM -- when using VM's I always use Bridged mode as it makes for much simpler networking -- even remote access over the Internet..

    jimbo
    Maybe I am misunderstanding you but you can attach online physical disks to a hyper-v vm using enhanced mode (vm installation needs to be able to act as an RDP server) via the tsclient interface.

    The only problem with this is that the tsclient interface is really slow and you struggle to get transfer rates over 10 MB/s, so is only ok for relatively small file transfers.

    If you connect to same drive using a network share, you get much higher speeds e.g. 100 MB/s.

    As an aside, if you use offline method to attach physical disks, you cannot attach host C drive, or use the offline disks. I never use this method, using enhanced mode or network shares instead.
      My Computer


  7. Posts : 7
    Windows 10 Pro 21H2 build 19044.1466
    Thread Starter
       #7

    jimbo45 said:
    Hi there
    You CAN add these devices - but not "dynamically" as per VMWare or VBOX via "attach or connect device". You need to add them to the VM config BEFORE powering on the VM. Provided these are "generic USB" devices they should be OK -- I know it works for external USB drives and sticks -- not sure about webcams but if the generic USB driver can find the device I can't see why it won't work even if it needs another driver which you can presumably install on the Guest. You need to add them as USB devices (or for DVD's - as IDE or SCSI devices). If you can't add the USB device in the config file then --sorry no go.

    Note though physical disks then won't be available to the HOST as they have to be "Offline" to it. Provided your VM is operating in Bridged mode then sharing is possible over the network both FROM and TO the VM. If in NAT (default mode) then access is only possible FROM the VM . I'm not sure under NAT if the HOST can eve access the VM -- when using VM's I always use Bridged mode as it makes for much simpler networking -- even remote access over the Internet..

    Standard Network shares should be available if the user has sufficient privileges. Hdd's on the host system aren't treated as "Physical disks" for the VM. Physical disks have to be set up explicitly in the config of the VM.

    For sharing devices etc HYPER-V while has lots of advantages for all sorts of things isn't really designed for this purpose and you may well finf the free version of VMWare's vmplayer or Virtual Box more appropriate as these can dynamically attach devices.

    Remember though if you CREATE a VM on a fixed physical disk with VMWare (can't say about VBOX) wth the boot device on the fixed disk then the "USB arbitration service" gets it's knickers into a twist and you won't be able to attach devices dynamically either.

    Cheers
    jimbo
    Hi, jimbo!

    Thank you for your detailed explanation, which goes beyond my knowledge and experience with VMs.

    The host PC has a physical DVD drive and built-in microphone and web camera which were NOT accessible by the Hyper-V VM with default connection settings as seen in the Skype screenshot above.
    So I changed the Remote audio recording settings to Record from this computer using VMConnect.exe DESKTOP-NKLFDG2 WIN10ProVM /edit in the Command Prompt window and the microphone (i.e. the input device) appeared.

    Unresolved issues still remain the missing physical DVD drive, the built-in web camera and other devices on the host, such as the Finger print reader, in the VM's Device manager.

    Next I'll try installing the driver software for the webcam which Skype uses, and, if it still doesn't work, go to VMWare or VirtualBox.

    Thank you again
    suspenser
      My Computer

  8. Bree's Avatar
    Posts : 22,807
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #8

    suspenser said:
    Is this a MS's hidden feature, which MS did not (intentionally or by mistake) explain or at least I didn't find any explanation?
    Kari explains it here:

    Kari said:
    The problem is, that Enhanced Mode in Hyper-V is based on Remote Desktop Protocol (RDP), basically exactly the same than a remote desktop connection. RDP requires a password sign-in, it does not accept PIN. As W11 OOBE / setup, when user uses an MS account, requires user to create a PIN, and enforces Windows Hello at sign-in by default, Hyper-V VM enhanced mode sign-in fails, only showing an empty screen. The system is awaiting a PIN as Windows Hello has disabled password sign-in. PIN is not allowed becase of the remote desktop protocol, system cannot show sign-in screen.
    Trying to install Windows 11 in Hyper-V problem | Windows 11 Forum
      My Computers

  9. cereberus's Avatar
    Posts : 12,906
    Windows10
       #9

    I had a (friendly) difference of opinion with @Kari, as I believe MS do not make it obvious that a PIN will create issues if you start oobe with an MS account, and I felt MS could avoid this by providing some kind of warning or prevent pin setup - the OS knows you are installing as a virtual machine (as it identifies virtual machine installations).

    However, the solution is easy enough to fix, once you know the reason. My point is the reason is not obvious - I even fell foul of it and had to google around a bit until I found the reason.

    In the end, MS created the issue by NOW insisting you have to enter a PIN if you decide to set up using MS account (which is also pretty aggressive in the oobe phase).

    Another solution is to simply use a local account, which you can do with Pro guest.

    You would not get issue with a Home guest as Home can only run in basic mode.
      My Computer

  10. jimbo45's Avatar
    Posts : 11,073
    Windows / Linux : Arch Linux
       #10

    cereberus said:
    I had a (friendly) difference of opinion with @Kari, as I believe MS do not make it obvious that a PIN will create issues if you start oobe with an MS account, and I felt MS could avoid this by providing some kind of warning or prevent pin setup - the OS knows you are installing as a virtual machine (as it identifies virtual machine installations).

    However, the solution is easy enough to fix, once you know the reason. My point is the reason is not obvious - I even fell foul of it and had to google around a bit until I found the reason.

    In the end, MS created the issue by NOW insisting you have to enter a PIN if you decide to set up using MS account (which is also pretty aggressive in the oobe phase).

    Another solution is to simply use a local account, which you can do with Pro guest.

    You would not get issue with a Home guest as Home can only run in basic mode.
    Hi there
    Slight mis-understanding regarding attaching physical online disks -- I meant if these disks were USB attached disks then that's where the problem arises. However using network connections is far better with a decent LAN than RDP especially with Wired connections or if you can use a real NIC rather than a paravirtulised Nic (especially if its wifi). You need bridged networking though to connect TO the VM rather than NAT.

    For the DVD try and add another IDE or SCSI controller to the VM config. Remember also you'll need some type of software for reading / writing / playing the disc.

    Cheers
    jimbo
      My Computer


 

  Related Discussions
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 22:11.
Find Us




Windows 10 Forums