I have a vi-Boot created W10 system that has "Enhanced Session mode" set. Yet when I attempt activate it, the "Enhanced session" is grayed out in the VIEW menu. Is this caused by something that vi-Boot causing ?
Any ideas would be appreciated.
Thanks
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* Enhanced session mode isn't available for generation 1 (unless Windows 10 Pro, Education, or Enterprise) virtual machines...
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).
Last edited by Bree; 25 Sep 2020 at 12:48.
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).
Bree - Its a HOME system based on UEFI/GPT.
This should work.
As I understand it, yes it should. You can check in Hyper-V Manager that it has indeed been created as a gen 2 VM. If so, then I can't see why enhanced session mode is not available. Maybe @Kari can help.
It seems that even for a gen. 2 machine, Pro is still required. I've just tested a viBoot VM of a uefi/gpt Home. This is actually from the same physical machine as my earlier screenshot, an initial install of Home (because it had a Home key in its bios) which was then upgraded to the Pro seen above. No enhanced session mode available for this gen. 2 Home VM.
...and simply upgrading that Home VM to Pro makes enhanced session mode available, showing that viBoot was not to blame.
Last edited by Bree; 25 Sep 2020 at 14:55.
Sorry to be the bearer of bad tidings.
What exactly did you want enhanced mode for? If it was for sound in the VM then you're out of luck. But if it was for transferring files then there are alternatives.
You could share a folder on the host and connect to it from the VM. For that you'd need to add a network adapter (which will also give the VM internet access, resulting in the VM checking for a digital license and finding that it's not activated). Using the Default Switch will let you access shares on the host only, or other VMs on the same host. For other PCs on the network you'd need to set up a virtual switch in Hyper-V Manager's Virtual Switch Manager.
If the file you want to access from the VM is an ISO, then add a DVD drive to the SCSI Controller.
For other types of files you can create a virtual .vhd drive using Hyper-V Manager > Actions > New > Hard disk... That can be mounted by the host and by the VM as a shared drive.
Yep - Home is basic only. Pro/Edu/Ent can be basic or enhanced.As I understand it, yes it should. You can check in Hyper-V Manager that it has indeed been created as a gen 2 VM. If so, then I can't see why enhanced session mode is not available. Maybe @Kari can help.
It seems that even for a gen. 2 machine, Pro is still required. I've just tested a viBoot VM of a uefi/gpt Home. This is actually from the same physical machine as my earlier screenshot, an initial install of Home (because it had a Home key in its bios) which was then upgraded to the Pro seen above. No enhanced session mode available for this gen. 2 Home VM.
...and simply upgrading that Home VM to Pro makes enhanced session mode available, showing that viBoot was not to blame.
Enhanced mode can only be used if the guest OS (i.e. one in VM) can act as an RDP server.
Linux distros like ubuntu can now used enhanced mode (via XRDP) but regrettably still no sound.
Hi there
Windows workstation edition can also use Enhanced mode
I'm not an expert in HYPER-V but I'm determined to have a play with it -- XRDP for Linux access to the desktop in VM's --i.e windowed desktop with windowed applications causes some problems in some newer distros due to the replacement of XORG / X11 by WAYLAND - the newer GUI desktop driver in some Linux systems. Access while using the RDP protocol from Windows actually connects to the Linux's vnc server (it's all installed seamlessly with kfrb - " KDE's Desktop sharing" app).
VMWare workstation can get sound from a Linux VM when using Krdc and the desktop sharing application kfrb -- you need to install KDE desktop on your Linux VM and possibly freerdp as well to get the combo to work.
I'll see if I can convert that VM to run on HYPER-V -- if that's too much bother I'll try installing a new one.
I'll post back later the results - the Linux VM I'll use will be ARCH LINUX with kde plasma desktop installed running with kernel 5.8.11-arch1-1. In theory the Wayland X-server should enable sound to work on the VM.
Will take me a bit of time to mess around with HYPER-V as its been a while since I used it last -- also I'm on W10 Pro workstation edition -- whether that makes a difference -- no idea though.
Gives me something to do while bars are shut !!
Cheers
jimbo
Hi folks
I just can't get the Linux desktop at all -- I think it's the XORG / X11/ WAYLAND problem.
I'll continue first on Windows with VMware to see if somehow I can get to Linux GUI -- SSH / Command line is no problem nor is file access (again via command line - SSH from Windows) but playing sound on a Linux desktop requires the GUI for the sound app AFAIK.
What I'm getting when I try and access a Linux desktop from a Windows system using RDP is : (note remote system so not on the Windows Host machine).
Drop down offers XORG, VNC etc -- then just a blue-greenish screen -- nothing.
So until I can fix that I'll postpone my HYPER-V testing.
If somebody can suggest a Linux distro where RDP to the desktop works from "Ordinary Windows" I.e not accessing via HYPER-V etc then I'll have a go with that - doesn't matter how old the Distro is.
Again - using ARCH Linux with kernel 5.8.11 (newish) -- as the Linux system to be accessed. I'm open to any distro where "standard access" works from Windows giving the full desktop.
Cheers
jimbo
Quote
