This used to be a pretty common bug, I think. The cursor is often drawn using a special "hardware mouse cursor" feature specifically designed to make a tiny bitmap move around the screen as efficiently as possible. It'd be easy for a driver to mess that up and cause the cursor -- and ONLY the cursor -- to look garbled.

You can see problems today like the mouse cursor not respecting Windows 10's night-shift color filter for the same reason.

On a thread yesterday I said that Windows' settings and lack of native keyboard remapping (without registry editing) were the most ridiculous things about it.

This pointer not respecting night-shift hits the trifecta hat trick. There's a registry fix, of course, but the first time I saw it, I thought "huh, that's weird". How did this get out without somebody on the release train thinking to themselves the exact same thing?

Cool, I never heard of that hardware mouse cursor feature! Makes sense to optimize that though as people will usually be updating the mouse position frequently