Page 1 of 1

Mouse Cursor bugged in newest version of VBox

Posted: 15. Sep 2022, 21:08
by Jetras
My Host is a Lenovo Legion 7 running Windows 11 Home.

Everything was fine yesterday, today I upgraded to the latest version of VBox (6.1.38 I think it was) and I am now experiencing this exact problem from this old ticket: https://www.virtualbox.org/ticket/15665

I uninstalled VBox and reinstalled my original version, even erased the .VirtualBox folder in the user directory, and removed the everything except for the VHD files of my actual VMs, yet the problem is still present in my older version of VBox that was working yesterday.

Are there any other files that "hang out" after uninstalling that I need to remove? Does anyone know if there was any resolution to the old ticket #15665? I attempted the suggestions in that ticket to no avail.

I use these VMs as training tools to record processes, and I am not at a work stop until I can get this fixed.

Re: Mouse Cursor bugged in newest version of VBox

Posted: 15. Sep 2022, 22:50
by scottgus1
Please put 6.1.38 back on, make a new VM, install the OS you had before. Then restart the VM, try to see if the problem happens again.

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 Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Re: Mouse Cursor bugged in newest version of VBox

Posted: 16. Sep 2022, 16:43
by Jetras
I just realizes the Windows 11 Home had a major update that installed itself during this same time. So now I'm leaning towards the idea that the windows update is causing this and I might have to wait for the next patch from windows? I reverted back to 6.1.22 and it is still occurring, which is why I'm leaning towards a Windows 11 Home issue. Is anyone else experiencing this?

I have another machine that is on Windows 10 that is running 6.1.22 with no issues. I have not upgraded it to 6.1.38, but I will the moment I'm confident that this issue is caused by the new Windows 11 Home update.