27 August, 2010
36 Comments
1 category
When I use a Windows 7 x64 computer and start a Remote Desktop session to a machine running Windows 7 x64 with VMWare 7. De mouse pointer disappears in the VMWare guest running Windows XP, when over textboxes or texteditors.
I found the solution at: http://wiert.wordpress.com/2010/08/06/rdp-to-vmware-host-running-an-xp-guest-invisible-mouse-cursor-on-text-editors/
Solution
Change the mouse pointer scheme to "Windows Black (system scheme)"
Start > Control Panel > Mouse > Pointers > Windows Black (system scheme)
Tags: VMWare
Category: Uncategorized
You are genius, I have been going nuts trying to guess where the heck my mouse is on an XP VM running on Vista. This was a life saver.
Thanks alot m8, works perfect.
Thanks so much for posting this. It’s been driving me insane for so long!
Excellent. I was always struggling trying to find out where the mouse pointer was, but with this tip you’ve saved me some extra work.
Top tip. Thanks!
OMG, I thought it was my VM installation and was going nuts looking through all the settings. YOu’re a Genius!!!
You’re a Boss!!! I fought long against this damn problem ad you saved my life
ledgend!!
Solution
Change the mouse pointer scheme to “Windows Black (system scheme)”
Start > Control Panel > Mouse > Pointers > Windows Black (system scheme)
Tags: VMWare
ah, you should sell this to vmware. for a lot of money. Thank you!
Worked for me on windows RDP (mstsc) sessions too! Thank you.
Discovered this blog to be a solution to my problem on April 3, 2016. Tried VMware 10 and VMware 12 both had issues. Must be an implementation problem for the WinXP OS. Thank you for the solution!
This tip also worked well for Windows 2012 Server running under VirtualBox.
Many thanks.
Thanks for this, It fixed my problem with RDC from Windows 10 to Windows Server 2012.
This is bunny! Cheers!
Perfect solution, thanks.
Thanks !!! This has been bugging me for a long time on my RDP sessions and this solution works.
If you don’t like the way the “black” scheme looks (I don’t, the cursor is thick and dark in text editors), select Windows Standard (large) (system scheme) and it seems to work and give me a nicer-looking pointer.
Windows 2016 server still happening. Changed the setting and it fixed the problem.
Thank you so much!
Solved! Thank you very much!
My problem was that My mouse cursor was disappear in white place in the monitor . You solution rocks . Thanks a lot .
Nearly 10 years later, this hack is still necessary. Windows 10 host, Windows Server 2016 VM.
Thanks very much :))
awesome! this even works for VirtualBox accessed over VNC, with a Ubuntu host and Win10 guest. Thanks!
Wow Still works, 🙂 thanks
8 years and Microsoft has this issue, seems low priority .
My Issue was:
Platform: both side Windows 10,
With multiple monitor and on second monitor mouse disappears on Visual studio code editor.
Thanks!! the struggle is finally over 🙂
Works for HyperV too. Nice one
Again, thank you so much for posting this solution. It was driving me to distraction!
Thanks Roel,
This is very clever solution. However it works for me, but I am still wondering why that’s happening on remote desktop only. On the physical console the cursor inverts it color as long as I enter black field ..
But that’s fine – I can use git-bash now 😉
Thanks for sharing.
Wow! you are a boss! Worked on Hyper V W10
Oh Jesus thank you! This was pissing me off to no end with the mouse pointer just disappearing.
ErMahGerd! This worked beautifully and easily. My system is a Windows 7 VM, displayed on my Windows 10 PC.
So much rubbish in other forums (especially the VMWare site) talking about registry settings, hardware acceleration, and other nonsense. Your solution just works.
Thank you for the solution!
Dear Microsoft – why is this still a problem 8 years later, when remoting into Windows 10 from Windows 10, using RDC???
Good grief!. Had this happening when docked, external monitor has no issues, laptop monitor loses the cursor over any text in any app. This fixed it!
PERFECT. VirtualBox 6 on win10. Thank you !!!
Still going strong! Hyper-V with Windows 10, this fixed my issue. Saved me setting up a virtual box vm which would probably have the same issue. Cheers!