Windows 10: Mouse Cursor Looks Funky

I just noticed a few days ago that my mouse selection cursor looks funky. I dunno why it started to look this way, but it's really annoying. (It's really big and unintuitive)
Not only that, but it also looks funky when it's in "hand" state.
Thankfully, it still looks OK in normal state.
What should I do to fix that ?

Anyway, here's some screenshots.






:)

 

Windows 10: mouse cursor disappears sometimes and just stops other times - very, very aggravating!

Actually your problem is EXACTLY the same as mine. And, unfortunately, my solution was not permanent! It's back! I'm pretty sure it is a funky bit of software - probably in the mouse driver. When I forced an install with a new, non-Microsoft mouse,
the problem was fixed. Then I had a power outage which caused a 'blip' which, apparently, brought back the original Microsoft mouse driver. And now my 'disappearing' mouse cursor is back. Exactly the way you describe it. Annoying, to say the least. For
now, I just grin and bear it. About a 1in 3 chance that, when waking up from 'sleep' that my cursor will be 'invisible'.

 

Looking for a different color mouse cursor

Using the Mouse settings found in Control Panel —> All Control Panel Items —> Mouse, you can change the appearance of the cursor. You can use one of the preconfigured schemes (Modern, Black, Inverted) at four different sizes (small, medium, large, extra
large). As for preconfigured schemes, inverted extra large may be your best bet. However, you can design/download a custom cursor and import it into one of the themes to create your own.

 

Have you looked at your pointer setting? You can do that by going to Cortana and typing "mouse properties", select "Change your mouse settings", at the bottom of the page select "additional mouse options", and go to the "Pointers" tab. See what happens when you change the pointer there.

 

Of course I did. But look what happened during the night ... :\
Now even the normal mouse looks like that !

 

Had the same issue. I believe it's tied to the nvidia driver that gets installed on windows build 10240. Installing the a previous driver seems to solve the problem for me. This happened a few minutes ago too.

 

Thanks Enkakoo, This issue was bugging the heck out of me.

Excellent find, back revving the driver to 352.84 fixed the problem.

 

353.30 works fine too. (I was on 353.50)