@XCP-ng-JustGreat thanks for the info. I have tried following your instructions for a test Windows 10 VM I have and unfortunately it has not helped the issue at all. I will note however that I haven't had a chance to update XCP-ng for a few months now, so I won't be running the latest version.

One 'issue' I have with your theory is that, in my case at least, it's the USB controller that's bombing, which is causing the mouse to stop working. I expect if USB pass-through was being used, this would also stop working for the same reason.

@DevilDan this isn't related to the mouse problem, so you are far better to create a new forum post for help with your issue.

@dinhngtu well arguably it’s one level up from that as it’s the USB controller that’s getting stopped by Windows, so I’d suggest the issue is the virtual YSB controller.

I have done some further testing on this (I have setup a test VM).

What I have learnt:

• The issue occurs irrespective of if the Management Tools/Drivers are installed or not.
• The issue occurs with both Xen Orchestra and XO Lite.
• When the issue occurs, device manager shows that the USB controller is stopped. Uninstalling the device and having Windows reinstall it (scan for hardware changes) is sufficient to get the mouse working again.

For what it's worth, my setup is:

• XCP-ng 8.3.0
• XO from sources, master, commit fd9c9
• Windows Server 2012 R2
• XCP-ng Windows Management Agent v8.2.200

I seem to notice the mouse pointer disappearing when moving away from the console window and then coming back (e.g. moving mouse out of the console, changing tab or something like that). Often when I come back, the mouse pointer is nowhere to be seen and I can't get it back.

Just adding a 'me too' to this one - I'm also having this issue (new XCP-ng/XO user). It's very frustrating and seems to be isolated to Windows VMs.