VRDE mouse accuracy issue

[SmithersTheOracle]

I had a question for anyone that has tried connecting to VRDE on a VM recently. I noticed that when I connect, my mouse is all over the place (not where my actual mouse is). Is anyone else seeing the same problem? Maybe it's because I'm on Windows 7 or because I'm on VB6.1? Also, the VM is running headless in case that matters.

[scottgus1]

I am running an XP guest on a Windows 10 host using 6.1.2. The guest is started headless and I am remoting in using Virtualbox's RDP server. I am using the Microsoft RDP client on both the Windows 10 host and another Windows 10 and Windows 7 PCs on the host's LAN. All three RDP sessions have right-on-the-spot mouse movements.

I have seen guests not have correct mouse positioning due to not using the default Virtualbox mouse setting (System, motherboard, pointing device). Some guests don't have correct mouse position because they don't have Guest Additions installed.

In your previous post on this subject you mention you're making a PowerShell module for Virtualbox. Does this mouse mispositioning hapopen only when launching via the PowerShell module, or also when manually starting a typical MS RDP session?

[SmithersTheOracle]

One guest is Windows Server 2016 Core and the other guest is Windows 10 1709. Both have additions installed. I haven't modified either of their mouse settings. I've reverted my host mouse settings to default, but that didn't affect anything. The module simply launches remote desktop on the host computer and connects it to the guest machine's VRDE server, but all the same I've opened the connection directly without using PowerShell and I get the same result. Unfortunately, none of my other VMs have a GUI, but I've already verified this issue on 2 guest machines so I would imagine the results wouldn't differ. Thank you for trying it though. You've helped me narrow it down to an issue with my host computer. I just didn't want to keep the Connect-VirtualBoxVMVRDEServer function in my module if there was a known issue with VRDE, but since there isn't, I'll keep it there and troubleshoot my host machine.

[fth0]

Check if the mouse filter driver VBoxMouse.sys is installed inside the Windows guest OS. AFAIK, there have been problems (in the VirtualBox 6.1.0 Guest Additions?) that the driver wasn't installed.

[SmithersTheOracle]

As a matter of fact, I'm using 6.1 and the same version guest additions. Also, you are correct in that VBoxMouse.sys isn't installed. I'll do that and report back.

[SmithersTheOracle]

That 100% fixed it for the Win10 VM! But when I tried to on the 2016 Core machine I got the error in the following screenshot. Looks like the driver doesn't want to work for 2016 core?

2016 Core mouse driver install failure

VirtualBox_2016 Core_25_01_2020_20_14_17.png (40.04 KiB) Viewed 1637 times

[SmithersTheOracle]

Quick update: I disabled signed driver enforcement and modified the inf so I could test it. Installed with pnputil fine. Restarted it. Still seems like it didn't install. The class GUID on server 2016 core might be different. Unfortunately, not sure how to find the device class without device manager. Also noticed the inf doesn't have anything for IA64 - but I'm not sure if that's a thing.

Still, thank you both very much. Already made my Win10 VM 10 times better than before.