No VNC Remote to access Windows VM

[Guinness9005]

Hello!

 

I'm new to this and have been searching all afternoon.  I have set up my Windows 10 VM and have it running, but when I click on the running VM I get no option for VNC Remote to access.  Is there another application I need to install to access?  I'm sure this is something simple I am missing

 

[Squid]

Since you said it's running, presumably you're using video card passthru at which point, VNC becomes unavailable.  If you still need to access the VM without looking at it's attached monitor, you'd want to use RDP instead

[Guinness9005]

Thanks! @Squid  That fixed that issue and now I do see the VNC Remote when I unselect GPU Passthrough.  I am now stuck at another place. On the NoVNC client it get's stuck here and will not progress, even when I follow the commands of pressing "ESC" or any key.  Thoughts?

 

[Squid]

AFAIK, the most common solution is to ensure that you're using a freshing downloaded ISO from M$ (and have selected that ISO for the install media in the VM template)

[Guinness9005]

Thanks @Squid  It's a fresh ISO from MS today.  Thanks for replying, I will keep digging, let me know if you think of anything else!

[testdasi]

That screen is the UEFI command line which means it can't detect a boot device.

You just need to type exit to return to the familiar UEFI (BIOS-like) interface then look for the boot manager in the various menus and then pick the device you want to boot with.

• If you just started installing Windows, it would be the optical drive (CD or DVD or something like that). Although usually it should boot directly to the iso regardless.
• If you are mid-way through installing Windows then you need to pick the HDD device. An easier way to do it is to shutdown, remove the iso from the VM template and start again. It should not need the iso as everything was copied to the HDD.

[Guinness9005]

Figured it out Thank you!   

[bugsysiegals]

Glad you figured it out but would have been nice if you'd elaborated for the rest of us ... I've the same issue using port 5901 and not sure what you did...