F5F Stay Refreshed Software Operating Systems Issue with cursor on Acer Chromebook Spin 13

Issue with cursor on Acer Chromebook Spin 13

Issue with cursor on Acer Chromebook Spin 13

P
ProstaKFX
Member
97
01-29-2023, 06:01 PM
#1
I'm experiencing a consistent problem where the cursor appears in the top-left corner of the screen while typing or interacting with YouTube videos, regardless of whether I move the mouse or scroll. This happens across all operating systems and even when using different devices like USB mice or external monitors. The issue seems to be related to how the cursor behaves when navigating elements on the page or when typing. I've tried resetting Chrome settings, removing extensions, disabling PowerWashing, and even using a different OS version, but nothing resolves it. I've also tested in guest mode without success. It's unusual that this persists even with external hardware, suggesting a software-related problem. Anyone have encountered similar issues? Your insights would be really helpful.
P
ProstaKFX
01-29-2023, 06:01 PM #1

I'm experiencing a consistent problem where the cursor appears in the top-left corner of the screen while typing or interacting with YouTube videos, regardless of whether I move the mouse or scroll. This happens across all operating systems and even when using different devices like USB mice or external monitors. The issue seems to be related to how the cursor behaves when navigating elements on the page or when typing. I've tried resetting Chrome settings, removing extensions, disabling PowerWashing, and even using a different OS version, but nothing resolves it. I've also tested in guest mode without success. It's unusual that this persists even with external hardware, suggesting a software-related problem. Anyone have encountered similar issues? Your insights would be really helpful.

Z
ZombieBoss7
Member
77
02-15-2023, 03:50 PM
#2
Wipe your touchpad. It used to occur for me, but cleaning it resolved the issue
Z
ZombieBoss7
02-15-2023, 03:50 PM #2

Wipe your touchpad. It used to occur for me, but cleaning it resolved the issue