Windows 10: [OS Build: 17763.3650] Windows VM does not boot when EIM enhanced interrupt mode is "on"

Windows VM does not boot when EIM enhanced interrupt mode is "on" on OS Build: 17763.3650 <iommu model='intel'> <driver intremap='on' eim='on'/> </iommu>On the same build, If I just turn to "off", it boots. <iommu model='intel'> <driver intremap='on' eim='off'/> </iommu>On OS Build 17763.1, I don't see the issue though i.e it boots even with eim = 'on'Anyone else have observed this issue? or hints on ways to debug this?

:)

 

Issues enabling Enhanced Session on 10 Pro VM

Hello guys!

This is my first post here, so go easy on me

I have been racking my brain, and have done search after search on how to solve my issue, but I have come to no suitable solution as of yet. I've seen that folks have been able to solve the problem, but no description as to what they did to solve it. It's almost like it just magically starts working I've had no such luck as of this writing.

Here is the problem:

I am attempting to install Windows 10 Pro x64 build 14393 on a Hyper-V Host which is running the same OS.

I have created the VM with no issues and installed with no issues. I can not for the life of me find out why I can not enable the features of enhanced session to be able to connect external drives, USB sticks, enable audio and enhanced graphics, etc.

So far the steps I have taken include:

1) VM created as Generation 2
2) Verified "Allow enhanced session mode" is checked in Hyper-V Enhanced Session Mode Policy server settings
3) Verified "Use enhanced session mode" is checked in Hyper-V Enhanced Session Mode user settings
4) Verified all integration services are checked under the VM settings
5) Verified Remote Desktop Services service is running on VM

Perhaps there is something I am missing? At this point, when I connect to the VM there is no ability to connect to local resources. Additionally, the "Enhanced session" option under the View menu on the VM is greyed out.

Any assistance in getting this resolved would be greatly appreciated!

 

Windows Hello PIN preventing use of Hyper-VM VM in enhanced mode

Hi there
I think if you "Disconnect" from the Internet while installing the VM -- install is then done via a local account - you can then set "Login options".

Then you can switch to an Ms account after connecting again to the net. Then try changing to Use PIN and see what happens.

I haven't tested this in HYPER-V but I don't think the Logon method should change just because you are on a VM.

If Wrong just ignore -- I usually always try everything in "Local account mode" first before attempting signing in with Ms account and other "non standard" options. Might also depend on the Windows build you are using for the VM (not the HOST). I've found build 331 seems the one with the least problems -- 330 forget it !!! 329 --Haven't tried.

Cheers
jimbo

 

Enhanced Session Mode question

Is the image you are using in viBoot an image of a W10 Home system or W10 Pro? Was the image of a Legacy bios/MBR machine or a UEFI/GPT one? The availability (or otherwise) of enhanced session mode depends on which you have used.

Testing this, for my Legacy/MBR images viBoot creates a Generation 1 machine, for a UEFI/GPT image it's Generation 2. For a Generation 1 VM enhanced session mode is not available for W10 Home as the guest OS, it's available if the guest OS is W10 Pro.

Turn On or Off Hyper-V Enhanced Session Mode in Windows 10


It makes no difference whether the VM was created by the Hyper-V manager or by viBoot. It's the combination of machine generation and guest OS that determines if enhanced session mode is available. Here's an example of a viBoot VM where it is (Gen. 2, W10 Pro).