virtualbox.org

I run windows 10 1903, new computer just a week old. Install VB 6.0.12 as this was the version on old. All guests are window OS, win 7 Ultimate 32bit, Windows 10 1803 pro 64bit, win 10 pro 1903 64bit. Noticed that when I enabled mouse integration I ge t a second cursor elsewhere on the guest that is a black line. It follows mouse movement but is not the actual working cursor which is normal pointer cursor. If I turn off mouse integration the second black cursor goes away. I need to use mouse integration for some reason if I mouse over a editor window or other text box cursor disappears, not useful when writing code. Now the real annoyance is visual confusion with the two cursors.

I now run a XPS 15 7590 with I7 6 core Processor and 32 gig ram. I run External monitors, 2 of them, driven through TB16 docking port. Also tested using HDMI port on Laptop, no Docking station same results.

I also had this issue with the SurfaceBook 1 (I7 Dual core 16 Gig Ram) Same Win 10 1903 host and same guests, running multiple monitors. The surface book is having hardware issues and is now wiped as it's going back the MS hopefully for repair.

Either case if I run the Guest on the main screen I do not see any issues. Then again the Guest displays with such small output I can't see much.

I've tried removing and re-installing Guest additions (GA), same issue.
I've upgraded to VB 6.0.14, Upgraded GA, same issue.
Un-Installed GA and rebooted guest, Installed GA no change.

I tried to get a screen shot but cursor(s) did not capture.

Thought I'd update this a bit as I've done a bit more testing/debugging.

So when I start a guest OS without mouse integration enabled I do not see a black bar, I call it a ghost cursor, in the guest that follows mouse movement but somewhere else in the window. If I place the guest window on the Main Monitor I do not see the Ghost cursor.

Perhaps it is because the main monitor is a laptop monitor with a resolution of 3840 x 2160 and the ghost image is too small for me to see. Where as the other monitors are 1920 x 1080.

Also on the note of monitors the Management Console when I switch(move) it to the lower res monitors display in such a way that I must re-size the window. This includes the settings window for the guests when I need to adjust them.

I too am having this ghost pointer issue on the non-primary screen. It tracks pointer movement but not exactly. Photo can't be attached due to 128kb file limit size on this site.

Well of course MS updated Windows 10, now on 1909, same issue persists. It gets a bit annoying when trying to get work done, the Black (Ghost) cursor tends to show better in Editors the the usual I bar cursor. I've been brushing up on my "foul Language" these days..... #!@# wrong cursor again......

Just in case this is related to the issue I was having here:viewtopic.php?f=6&t=96595 where there's an issue in 6.1 silently failing to install the mouse drivers...

Open device manager in the guest and follow these steps to check:

• 1. Open the Microsoft PS/2 Mouse properties
  2. Click the Driver Details button on the Driver tab
  3. Look for VBoxMouse.sys in the list of drivers

If VBoxMouse.sys isn't listed, and only if it isn't listed, open the VirtualBox Guest Additions disc in the guest and follow these steps to fix:

• 4. Navigate to the NT3x folder
  5. Right-click VBoxMouse.inf and select Install from the context menu

Then restart the guest machine and try again.

Yes this is all there driver version is 6.1.2.135662

Well I figured I'd try... I was really hoping it would've been that easy for you. Sorry and good luck.

I've checked all of my guest OS's and they are all running the same driver. Also I have 1 Guest OS of Windows 7 Ultimate, the rest are windows 10 Professional latest version 1909.

So based on the general testing the same issue exists in all guests. Black "Ghost" cursor tracking near by in the Guest OS when enabled Mouse Integration which is required in order to see a mouse cursor in Editors such as notepad, Notepad++, and Visual Studio while in full screen mode where Guest is displayed on secondary monitors. This has been the case ever since my Host OS has been windows 10. Issue seen in VM versions 5.x and 6.x. I've tested in two brand new Laptops the first being MS SurfaceBook 1, the second Dell XPS 15 7590 both with secondary monitor(s). I've tested with monitor plugged into Laptop directly as well as through Docking stations, same results. I have fully removed VM from the host and re-installed, no difference. Someone in an earlier post on this commented that multiple monitors and docking stations are not the norm, my testing of a monitor direct to the Laptop I feel negates it's the docking station as contributing to this. I feel it's something in the Host OS (win 10 professional) and how it handles secondary monitors.

I use VM to isolate development work from main system as a safety step. I don't have 8 hours to rebuild the laptop because I tried something that trashes the OS. Easier to snap shot the Guest and then revert it. Allows me to work on other things while waiting for the guest to reset.

SmithersTheOracle wrote:Just in case this is related to the issue I was having here:viewtopic.php?f=6&t=96595 where there's an issue in 6.1 silently failing to install the mouse drivers...

Open device manager in the guest and follow these steps to check:

• 1. Open the Microsoft PS/2 Mouse properties
  2. Click the Driver Details button on the Driver tab
  3. Look for VBoxMouse.sys in the list of drivers

VBoxMouse.sys-Device Manager.png

If VBoxMouse.sys isn't listed, and only if it isn't listed, open the VirtualBox Guest Additions disc in the guest and follow these steps to fix:

• 4. Navigate to the NT3x folder
  5. Right-click VBoxMouse.inf and select Install from the context menu

VBoxMouse.sys-Install.png

Then restart the guest machine and try again.

Thanks for the suggestion but Windows is my Host not my Guest. Hopefully VirtualBox will find a solution.

So I've done a bit of digging and testing last nite on this. Again my Host is win 10 pro fully updated with all patches, guest is also win 10 Pro fully patched. Guest OS is in full screen mode and displayed on secondary monitor. Vbox is version 6.1.2 r135662 (Qt5.6.2)

I see a black bar above the pointer cursor during boot up of guest OS. Once OS is up I no longer see the black bar. Open Notepad, no cursor present when in the main edit area of the application. I then enabled Mouse Integration. I now can see the Cursor in the notepad window but I also see the black bar ghost cursor else where on the guest screen.

I was using the VBoxVGA Graphics controller. Noticing this is no longer the recommended controller I uninstalled Guest additions. Rebooted Guest and logged into guest. Then shut down guest. I switched Graphic controller to VBoxSVGA. Started guest VM and then installed Guest Additions. Same results. Confirmed the Mouse driver as mentioned in previous replies is installed.

Verified the Ghost is not present when guest is displayed on the Main monitor of the laptop. Also verified that Mouse cursor is present in the Notepad Main window as expected. Main monitor is very high resolution and everything is extremely small. Also noticed the mouse movement, with or without, mouse integration enabled is slow as compared to Host screen mouse movement.

Oh and thanks to the Dev team for fixing the crashes I had experienced when I had previously been using the VBoxSVGA driver under 6.0 of VBox. I had been reluctant to stop using VBoxVGA because of the constant crashes i had been having. But to further the testing here I bit the bullet and switched the controller.

WOW!!!!.... Talk about a fluke. OK decided I wanted a different color Cursor as this issue is really bugging me too often I'm chasing the wrong pointer as my eys catch the black bar. Well I changed the cursor on the host OS (Win10), once again ghost cursor and in/out of mouse integration befuddles me. BUT IT FIXED the problem. the new red cursor on the host show and works well across all monitors and through VMs without Mouse Integration enabled. It works like it should with a minor problem the "ghost" cursor in the VM Guest is still there but now is aligned to where the cursor is not a distance away.

Hope this assists dev team in coding a better fix that removes the Ghost.