Mouse issues on Windows 10 guest

[ingbs2001]

Goog morning,
I have encountered problems with the mouse with the new version 6.1.40
Host Linux Ubuntu 20.04.5 LTS
Guest Windows 10 Pro 21H1 build 19043.2130

The mouse works fine with only display 1 active,
mouse unusable if display 2 is enabled and mouse integration is enabled.
For example, on the desktop, for a mouse position it appears to use two positions: a preview of the last icon on the left on mouse movement, and other icon selected under the mouse pointer.
The icon under the mouse pointer position (or other item, such as menu item) is clickable.
In other circumstances, as moving a window, it is very difficult to work with mouse.

[Creideiki]

I can confirm this.

VirtualBox 6.1.40
Two Screens
Host: Ubuntu 22.04.1 LTS
Guest: Windows 10 21H2
VBoxSVGA, USB-Multitouch-Tablet (dito with USB-Tablet)

The mouse pointer itself is working smoothly, but the position seen by the guest OS is jumping left and right erratically. If you e.g. move a window it jumps left and right.

It is nearly not possible to work with the system.

[td2022]

Host: Ubuntu 22.04.1 LTS
Guest: Windows 10 Pro 64-bit (10.0, Build 19044)
VB: 6.1.40 r154048
VBoxSVGA displaying on 2 HD monitors

I'm seeing the same behaviour. Disabling the second screen solves it for now.

[mzenyk]

The same problem. Host system Debian bullseye, guest system Windows 10

[denk]

I have the same issue!

Host: Arch Linux (fully updated)
Guest: Windows 10 Pro 64-bit (fully updated)
VB: 6.1.40 r154048
VBoxSVGA displaying on 2 monitors

Edit: The same happens with VirtualBox 7.0.2

[argetlam]

I have the same issue.

Disabling the second monitor does not completely fix the problem for me. But it does get better.
When the second monitor is disabled, double clicks still happen from time to time, even though I
only click once. This makes it impossible to select text, for example.

Host: Debian 11 (fully updated)
Guest: Windows 10 Pro 64-bit (21H2, Build 19044.2130)
VB: 6.1.40 r154048
VBoxSVGA displaying on 2 WQHD monitors

[bitflip]

Same here

Host: Ubuntu 22.04 LTS, fully updated
Guest: Windows 10 Pro 64-bit 21H2 build 19044.2130
VB: 6.1.40 r154048 (Qt5.15.3)
VBoxSVGA displaying on 2 monitors

[scottgus1]

OP & all me-too-ers: a vbox.log while this problem is happening is needed to get a fix.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab.

[VMBroken1111]

Made a account as I have had help from here in the past and wanted to pay it forward.

I had the same issue, didnt end up looking too deep into this, but seemingly a issue with nvidia driver on linux.

A work around that effectively sorted the issue for is setting pointer to PS/2

[Creideiki]

Host: Ubuntu 22.04.1 LTS
Guest: Windows 10 Home 21H2
VB: 6.1.40
VBoxSVGA displaying on 2 HD monitors
amdgpu drivers
Pointer Device: USB tablet or USB multitouch tablet (with PS/2 it works normally)

The mouse pointer is jumping erratically left and right. It is nearly impossible to work atm.

The logfile was created with starting Windows, opening an moving a firefox window, closing it, then Windows shutdown.

[Creideiki]

Thank you for the tip with PS/2. That works indeed.

[mpack]

(mod edit by Scottgus1: Creideiki made a new topic on this subject per a request from me, but it was better to have it posted here. The former topic was locked by Mpack, and I have merged that topic here.)

Locking topic as the same question was asked and answered here: viewtopic.php?f=1&t=107377&p=526547#p526547.

[tr00th]

+1 on the PS/2 workaround

[Creideiki]

Each me-too should be put in their own topic, in case their problem is really not the same.

Hmmm... I created a new topic with the log file, but the topic got locked by mpack referring to this topic... should we create a new topic or should we add to this one?

[scottgus1]

I created a new topic with the log file, but the topic got locked

Thanks for making the new topic, Creideiki. With the new version out, and me being a new moderator, Mpack has been working out the details with me on efficient support for the devs to see what is going on. I'll move your other post into this topic.