Windows 10: Win10 Pro, Hyper-V VMs not responding after disconnect

Hi all, this is my first time posting here.


I have a slightly unusual way of using my Win10 Professional PC: I have built VMs for individual scenarios (personal computing, professional work, my daughter's PC, etc.) and I have the main PC and all VMs running constantly. I do little on the host PC itself, other than games and other things that require direct hardware access. I built this system in 2017, and it worked pretty much flawlessly for some time, until the latest version of Win10 came out. I dutifully upgraded my host and the VMs to the new version of Windows, and now I have a new problem that is definitely tied to the "upgrade":


I usually connect thru Remote Desktop to these VMs (yes, even if I am working from the host computer). If I reset a VM, I can log into it and work without any issues. However, if I disconnect from that VM and then later try to connect, it hangs (or it crashes) and I must reset it before I can again use it. I have tried reconnecting to the VMs using the Hyper-V connect session, and there I sometimes can see that it has crashed--I don't know if it is always crashing upon reconnect because sometimes it just seems to hang.


This is certainly an issue that is introduced with the latest version of Win10 Pro. I have researched on the Internet and I can't find anything directly addressing this--I assume because this is an unusual way to use Hyper-V at home.


Does anyone have any ideas? The system btw is a robust 6800K 6 core CPU with 64 GB RAM and plenty of SSD storage space. Again, it worked perfectly before the upgrade, and it still works perfectly as long as I do not disconnect.


Regards,

John U

:)

 

Hyper V VM not responding

I've built a Win 10 Pro pc consisting of i7 3770k with on-board 1gb graphics, 8gb ram, 1x SSD, 2 x hard drives.

I've created a VM under hyper v of the minimum specs required because that's all I need. The dos os I'm running in it is called spinrite which runs in 640k ram. The VM starts and runs perfectly but after 10 minutes the dos program becomes unresponsive to
keyboard inputs. The VM menus work ok, the internal machine doesn't, the software continues to run until completion. Can somebody help me understand why the VM doesn't respond to keyboard inputs? On the status bar bar it says keyboard inputs captured.

Regards

 

No audio in Hyper-V - Win10 VM on Win10


@Ix07: I agree. For example, When checking on Windows 10, the "Remote Desktop" section is not present under Control Panel > System > Remote nor is there a tsclient found as a Network device, even though the "Remote Desktop Services" is running.








On Win 10 Pro, the "Remote Desktop" section is visible and there is a tsclient Network device.

 

Unassign Hyper V VM with deleted User account

Hyper V is not assigned based on user accounts.

Hyper V is a server feature that allows you to create VMs but they are not assigned to users.

Can you post a screenshot of what you are referring to?

And then share on a cloud drive and post link here for me to look at?

Also what are the steps you are doing to "assign" the VM to another User?