Windows 10: Diff between Hyper-V Home and Pro guest logins using PIN?

Although both Windows 10 Home and Pro support use of a PIN for login on devices, that does not appear to be the case when using Hyper-V virtual machines.

I have three W10 Home x64 virtual machines and five W10 Pro x64 virtual machines spread across two hosts.

I use PINs to log in to all three of the W10 Home vms, but the option to use a PIN is not even present in any of the five W10 Pro virtual machines.

Is a PIN incompatible with remote desktop connections or something that Pro supports and Home doesn't?

What gives?

:)

 

Hyper-V on Windows Home Edition?

In my "Services (Local)", the following are listed:

Hyper-V Data Exchange Service

Hyper-V Guest Service Interface

Hyper-V Guest Shutdown Service

Hyper-V Heartbeat Service

Hyper-V Remote Desktop Virtualization Service

Hyper-V Time Synchronization Service

Hyper-V VM Session Service

Hyper-V Volume Shadow Copy Requestor

Since Hyper V isn't supposed to be on Windows 10 Home, I'm wondering what's going on and why it is in my Services. Are there any other services which would appear in Windows 10 Pro, Enterprise or Education that shouldn't appear in Windows 10 Home Services?

Thanks!

 

Unable to uninstall hyper-v in windows 10

Please try to follow this step,

Remove all hyper-v network out and use the same steps as Kalpana Shankarappa told.

You can find how to remove the hyper-v networks from this link, http://www.altaro.com/hyper-v/troubleshooting-hyper-v-guest-os-installations/

 

I just happened to have installed a Hyper-V instance of Win10 Pro CU and was given the option to create a pin (which I declined), so it seems to be offered on Hyper-v.

 

Please see if you have an option for a PIN in Accounts/Login Options. The option remains in Home but not in Pro on my Hyper-V instances of Pro.

 

Of course PIN is working on Hyper-V guests running any edition of Windows 10 in normal mode. However, PIN sign-in is not available in Enhanced Session Mode (ESM) which is based on Remote Desktop Protocol (RDP) which requires a password sign-in disabling PIN.

When you run a a guest VM and click Connect when ESM prompt is shown you will be connected to VM using ESM:





If you decide to save connection settings, EMS will be be default connection to that VM and this prompt will no longer be shown but instead you will always be connected using ESM:








Now when VM is connected in ESM, PIN will be disabled and sign in screen does not even show the Sign-in options link under the password field:




(Click screenshots to enlarge.)

In ESM you cannot set / remove / change PIN because it is completely disabled, therefore PIN options are not even shown in Settings:





Simply unselecting ESM from View menu enables PIN again, Sign-in options link again visible:





And PIN, once again enabled, will be shown in Settings:





Enhanced Session Mode is available on all guests running any edition of Windows 8 or later when guest is a Generation 2 virtual machine, and in Windows 8 / 8.1 PRO and Enterprise as well as Windows 10 PRO, Education and Enterprise editions on Generation 1 virtual machines.

Short: judging by your original post I think your Home edition guests are Generation 1 virtual machines and therefore the ESM connection prompt is not shown as Generation 1 VM running Home edition does not support it. Because ESM is supported by PRO guests regardless of their generation, you will be connected using ESM thus having yourself selected to disable PIN login.

To connect in normal mode just close the EMS prompt when it's shown. If you want to you can completely disable EMS in Hyper-V settings:

 

Thanks for the great reply! By the way, the Home guests are Generation 2. ESM is disabled for Home guests. IIRC, Home doesn't have RDP.

 

You rock. Thanks!