The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    K501U - ASUS Touchpad issues

    Discussion in 'Asus' started by hi-tech.redneck, Jun 9, 2017.

  1. hi-tech.redneck

    hi-tech.redneck Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    I purchased a K501UW-AB78 notebook from Newegg about a month ago. It's great, other than the touchpad, which is not:
    - The right click button does not right click about 75% of the time (left clicks instead, even if I right click on the most extreme right part of it)
    - Two finger scrolling is erratic.... sometimes it's slow, other times it's blazing fast... No intertial scrolling functionality setting in driver, and Windows scrolling setting is set to the default 3.
    - When the CPU is working hard, touchpad is not responsive - the cursor stutters across the screen and is uncontrollable

    I reinstalled the touchpad driver, and tried several older versions as well as other Asus touchpad drivers for other models. Same issue no matter what (although some other models' drivers have more functionality than this one)

    Wondering if anyone has any similar issues and if so any other suggestions other than throwing it off a cliff lol. It's frustrating. Yes I have a mouse but I use it on the go a lot and a mouse is not an option. Asus Tech Support, of course, suggested reinstalling the driver, which I did.

    THANKS!
     
  2. Support.2@XOTIC PC

    Support.2@XOTIC PC Company Representative

    Reputations:
    486
    Messages:
    3,148
    Likes Received:
    3,490
    Trophy Points:
    331
    This seems like an issue with the key itself, does this issue still occur with the default Windows driver installed?