Something is wrong in newer versions of Windows 10. And then recreating a new VM or importing the VM. It seems to be a bug in Microsoft VMBus implemented in the hypervisor.įinally I tried to uninstall the Hyper-V feature (in optional features of Windows 10), reboot, then reinstall it, reboot again. Visibly the services are running, but not detectable from the guest.

I tried to look in the Event Viewer, but I see no message there saying that some credential requests are rejected by Hyper-V or in any of its services. It was wrkling in the past in Windows 10, but no longer works since a major Windwos 10 image was applied to the host system.įor me this is a new bug in Hyper-V hypervisor: the extra services installed on it ARE running, but are not properly setup. In a Linux VM, I see that some credentials are not detected. The Enhanced session is still grayed (this is true independantly that I install it in Generation 2/UEFI boot, or Generation 1/BIOS boot, or if I enable or disable the secure boot boot mode for that VM). I am now having the same problem, in ALL kinds of VM (Generation 1 or 2 does not matter), including when starting a fresh Windows 10 guest from Windows 10.Īll the setting for Hyper-V server are enabled, as well as in the guest OS settings.Ĭreating a new VM on a new virtual disk also has the same problem.

Windows 7 switch user greyed out