[Looking for Charlie's main web site?]

How to disable the Asus NumberPad, embedded within touchpad on some modern laptops

Do you have a modern Asus laptop with the NumberPad (orNumPad) feature (a virtual numeric keypad embedded within the touchpad)? You may know there's a button to enable/disable it on demand, but do you find find it coming on when you brush that by mistake? Are you annoyed that you can't find how to "permanently" disable it?

In this post, I discuss ways to try to do it. There are various ones. Removing the numberpad driver (NOT the touchpad's driver) from Windows Device Manager seemed at first the best way, but it proved to be temporary. Others later proposed various ways to try to remove it permanently, but those don't seem to work, either.

TLDR; See below for how to do that if you may prefer to cut to the chase, but interested readers may want to understand a few things first, like what I mean by the Numberpad feature, and the problem that may prompt folks to seek how to disable it, as well as other solutions that I found had been proposed (even before I wrote this post) but also did not work. Then I conclude with what has, for me (so far).

About the Feature

First, let's talk about the NumPad feature itself, for context.

The feature is found on many modern Asus laptops whose keyboard lacks a full numeric keypad on the right. (I have it on a ZenBook, but I've read of it existing on VivoBook, ExpertBook, StudioBook, and even ROG Strix and perhaps Tuf models--though I also have one each of those and they do NOT have it.) See the image provided here.

It's a "virtual" numeric keypad within your touchpad that can be enabled optionally with a button in the top right of the touchpad. Asus calls the feature "NumberPad". You can learn more about it at the Asus web site FAQ on the feature.

How to enable/disable it on-demand

It's designed so that you can use it when you want, and then disable it. You simply tap the icon (a virtual button) on the top right of the touchpad to enable/disable the display of the Numberpad. When you enable it, the numeric keyboard lights up within the touchpad, which is helpful for those who need to do numerical data entry, etc.

Note that even when the numpad is enabled, you can still use the touchpad for typical mouse movements and tapping, which is especially clever. But some folks find the touchpad mouse movements to NOT be as good an experience as when this feature is DISABLED.

Again, to disable the numberpad, you simply long-press the same image/virtual button, and the numberpad no longer appears.

The problem of accidentally enabling it

The problem is that it's very easy to brush that button to enable it. Granted, to turn it off, you just have to long-press the button. But it gets annoying if you find it happening often.

The annoyance is that there doesn't seem any feature built-in to the hardware or any Asus software to disable the feature.

Trying to disable the Asus Numberpad "permanently"

Perhaps like me you don't really need a numeric keyboard at all, and so you may prefer to just disable the Numberpad permanently. (Perhaps you bought the machine not for that feature but for other features of the machine.)

As I searched the web (and the Asus site) for any explanation of how to permanently disable it, I found various suggestions (see below.) But none worked well for me, or didn't work permanently.

And when I first wrote this post, I shared my first attempted solution which I THOUGHT would be permanent...

My first attempt: remove it from Device Manager

Here's what I shared here first: using Windows Device Manager to remove the feature. I thought it was the best solution, but it turned out that on a Windows update the feature was restored.

I leave that manual approach here for posterity, but most folk will want to try a more permanent fix, below (and which doesn't require you make these manual Device Manager changes).

Of course, anytime you manipulate any system features you are taking a risk. I am simply sharing what had worked at first for me. I cannot accept any responsibility for your taking the following actions

Here are the steps I shared originally (though, again, these did not ultimately prove to remain enabled, so see the solution I am preferring for now, below). I merely offer these for posterity/tracking the evolution of this effort:

  1. In the searchbox on the TaskBar, type device manager, and then select it from the Windows menu
  2. In the device manager interface, select Keyboards , then ASUS Number Pad
  3. Right-click that (as I point to with the second, red arrow), and choose "uninstall device"
    Don't worry that doing this will disable the entire touchpad. That is a separate "device" (see "Human Interface Devices" within Device Manager and its "ASUS Precision Touchpad" (as I note in the screenshot, with the first, green arrow). We will NOT remove that.
  4. A popup will appear, and you will WANT to check the option "Delete the driver software for this device", otherwise the removal will last only until a restart of the machine

You may notice that I put the words "permanently" in quotes in first the section title and other references above. That's because even as I wrote this post originally (in Dec 2020), I feared that even though deleting the driver this way would indeed cause the feature to be removed then and even after a reboot of my laptop, it was possible that some future Windows, ASUS, or bios update may add the feature back.

And sure enough, days after I posted this, I DID find that the numberpad had indeed re-enabled itself (the button "worked" again and it appeared in device manager). I updated the post here and kept looking for still-more "permanent" ways to keep it uninstalled. And others shared ideas in comments below, some of which worked but again only temporarily.

After that, I share what seems to be working best for me.

"Solutions" that are NOT solutions

Even before writing this post, as I went seeking a solution I found many resources on the web where others wanting to disable this feature went looking and asking about how to do it. Before anyone reading this post may want to propose these other various "solutions", I want to clarify here first ones that definitely do NOT solve the problem:

  • First, many folks trying to "help" point out how (as I discuss above) you can "just click the button on the top right of the keyboard", but the issue is that that's not permanent
    • Again, some of us just want to disable it permanently, never needing a numeric keypad (or perhaps having an external one or external keyboard)
  • Next, many folks trying to "help" confuse the discussion with instead another feature available in some other keyboards: an embedded numeric keypad WITHIN THE MAIN KEYBOARD (such as discussed here) or perhaps even the numeric keypad on the right of many keyboards
    • And of course those sort of numeric keyboards can be disabled by clicking the numlock key (or perhaps fn-numlock)
    • But the Asus laptops with this NumberPad discussed here (embedded in the touchpad) do not HAVE such a numlock at all, so that's not the solution
  • Then some point out how of course one can disable the entire touchpad, such as with a hotkey on the keyboard like f6 or fn-f6
    • But again that's not the "solution" to disabling the Numberpad feature, as someone may STILL want to use the touchpad otherwise

A third-party solution that might suit some readers

Some folks had helpfully point out (elsewhere and in comments below) how an autohotkey script could disable the numlock key on any keyboard (and perhaps even an internal "virtual" one as this Numberpad might be considered).

See such third-party tools as autohotkey, powertoys, sharpkeys, and more (including some others mentioned in comments below).

Such a solution may well work for you, but some readers (myself included) may not want to bother with installing or relying on such software, especially if only for this one problem--and perhaps all the more if the solution I offer below (relying on no installation of any software) may suffice for them.

And if you read along with the many (many) comments that others have offered, they proposed still other solutions. None really worked well for me (even trying PowerToys and Sharpkeys), to "prevent" the key from working.

Actually, one suggestion did almost work, and it led me to what is for now my preferred solution, coming up just after this last one.

What *almost* worked for me: a scheduled task to remove the numpad driver on startup

Commenter "Forrest Fump" shared below what may seem a cumbersome solution, of creating a Windows scheduled task. He set it to run "on startup", but a problem I found is that often the driver was re-enabled EVEN AFTER STARTUP, so this "worked" but was a hassle to "run again" One would typically open the Task Scheduler, find the task, and manually "run" it. If you're interested to consider what he offered (which takes just a few steps to implement), see his comment below.

[Update: On June 17, commenter Phillippe Petit shared that he had gotten things working by setting up the task not ONLY on "on startup" but also on login, unlock, and nightly. That's worked well for him, and it may suit others who want to try that. BTW, for those old enough to recognize his name, I have no idea if he may be THAT Phillippe Petit! :-) He gained infamy for walking a tight-rope between the World Trade Center towers in 1974.]

What's finally worked for me: a shortcut to remove the numpad driver, on startup or on-demand

Instead of relying on that scheduled task approach from the helpful comment from Forrest (which seemed not to really work on startup as expected, and was a little challenging to run on-demand, both of which I discussed in a follow-up comment), I realized that we could just instead create a Windows shortcut executing the very command Forrest offered in that scheduled task.

Then we could put that shortcut in the Windows folders that a) hold programs to execute on startup, and then also b) that hold programs that could be executed easily from the Windows "Start" menu.

So those are a couple of different steps: create the shortcut (confirming it works), and then place it where it can be easily used.

Creating the shortcut

So first, how to create the shortcut? I realize some readers may never have created a Windows shortcut. You can do it easily from Windows File Explore. (Click the Windows Start menu in the bottom left, type the word explorer, and open "File Explorer".)

Now, change that to point to any folder you can write into (like for example your Windows "documents" folder). Then click the Home menu, then choose "new item", then "shortcut".

That will offer two prompts, the first being: "Type the location of the item".

In that field, enter the key information from Forrest's comment below. He shows how to find the identifier for the numberpad device driver, and then he uses a command to "remove" that. What I'm saying is to use that same command and info, but put it in a shortcut instead, in that "location" field.

In my case, the value I entered was:

%windir%\System32\pnputil.exe /remove-device "HID\ASUE140A&COL04\4&15DD5162&0&0003"

(Don't worry about the %windir% value. Windows will sort out that value for you.)

As for that value in quotes, you need to make sure you get the right value for you, per the couple of steps in Forrest's comment. here's his key first step. Read his comment for a bit more context:

"1) Get the instance id of the device: Devices Manager -> Keyboards -> [right click on device] -> Properties -> Details -> Device Instance Path. You can right-click to copy that "path" (more like an ID) to the clipboard."

Then the shortcut creation process will ask you to simply give a name the shortcut. I just called mine, "disable numpad".

That will create the shortcut, in the folder you started in (I had proposed your Windows "documents" folder, above.)

One last thing: for the command to actually work, the shortcut must "run as administrator". To do that, right-click on the shortcut, choose "properties", and from the "shortcut" tab you will be on, choose the "Advanced" button, then choose "Run as administrator". Then click "ok" and "ok". (If you are not able to choose the "Run as administrator", it could be that your user account is configured in a way that this cannot be done. In that case, this "final option" I am describing will not work for you.)

Next we should check to make sure it works. First, enable the number pad (so it lights up on your mousepad). Then, since you're in the folder where you created the shortcut, just double-click on it. If it works, the number pad should turn off. If it does not, double check your steps above.

Where to put the shortcut?

Finally, while you could certainly just go to your documents folder and run that shortcut whenever you wanted to, that won't help disable the numberpad on startup, and in case the numberpad gets re-enabled after startup, running the shortcut from that folder takes a few steps.

So first, as for putting the shortcut somewhere that it will get executed upon each Windows startup, I found that I could put it in this folder:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

If you try to go there and find you cannot, it may be a permissions issue. Take off the right-most folder name and see if you can then get into the folder. At some point, you may get a Windows prompt asking you to confirm that you should be given access to that folder. (Windows has some built-in protections that hides even your own folders from you.) After accepting that prompt, you should then be able to enter the rest of the folders I've listed above by double-clicking on each. Then finally, you can copy (or cut) and paste the shortcut from your documents folder into this Startup folder.

That will cause Windows to execute that shortcut on each restart.

Then second, if you want to be able to easily execute the shortcut from the Windows menu, copy the shortcut into the Programs folder right above the Startup one above. Now, you should find that when you click the Windows Start menu, and start typing the shortcut name (the word "disable", without quotes, in my case), then Windows should show it as something you can now just click on. (If you don't see it right away, it may take a minute for Windows to properly detect and register the fact that you placed that shortcut in that folder.)

As for why Windows doesn't present names of files that are in that Startup folder, one level down, I can't explain. But it did not for me (Windows 10, Version 20H2. But don't worry if you may not yet have updated to that recent Windows version, as I write. The steps I discuss here have worked with Windows for years.)

If you do somehow still struggle, write a comment below and I or others here will try to help.


I hope that you find that this solution above works for you, as it has for me.

But it sure would be nice if Asus would just offer us a simple means to disable it, or to swap the behavior so that it takes a LONG-press to enable it and then a quick one to disable it. From the number of people annoyed by this feature, either option would seem a great future improvement.

Finally, a Linux user may wonder why I am showing only the solution for Windows. My understanding is that the Asus Numberpad feature is only available on Windows devices. If it ever is offered for Linux, the same concept (of removing the device from the OS) would apply.

If you have another idea or feedback, please comment below.

For more content like this from Charlie Arehart: Need more help with problems?
  • If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
  • See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed
This tweak worked like a charm. I bought a VivoBook a few weeks ago and the number pad would turn on and often not turn off even after pressing the virtual button numerous times, and rebooting. It made typing a nuisance. Even if Windows updates reinstalls the drivers you have saved me a lot of trouble.
# Posted By Robert Borgen | 1/24/21 6:25 PM
Sweet. Glad to help. Hope we may learn of a permanent way to disable it.
# Posted By Charlie Arehart | 1/24/21 6:29 PM
Thanks for your work on this - gave me hope! As you say, removing the driver only works for a few days... But one of the comments you made about the other methods that don't work gave me an idea. Microsoft has this free app called Powertoys which I use (sits in the tray). In it is a 'keyboard manager' which can re-map keys. I normally use this to re-map the Caps Lock key (which I find screws me up about as often as the Asus keypad!) to the ordinary Shift key. So I thought I'd tap the virtual button on the track pad as if it were a key. And it comes up with NumLock! So I remapped it to Shift and, yes, the virtual button is disabled.
If you have PowerToys enabled on boot it remembers the remapping.
It's also easy to undo if you want to use the keypad some time...
# Posted By rmzetti | 1/28/21 3:49 AM
Thanks, rmzetti. And yep, that was the last point I'd made, where others had used options for that (remapping the numlock) that seemed a bit more convoluted (personal opinion).

But I'll give the power toys a shot, as others may want to. Anything more permanent will be such a relief.
# Posted By Charlie Arehart | 1/28/21 7:49 AM
Sweet, that has worked (so far, at least). I will say that some may find the powertoys install a little heavyweight, but it's worth it for the relief.

FWIW, I tried also to use other approaches to disable numlock (setting a certain regkey to 0), but it did not disable that numpad like the powertoys did. Again, thanks.

Still open to other ideas any readers may have.
# Posted By Charlie Arehart | 1/28/21 10:40 PM
What I really want to disable is the calculator gesture. I bring up that thing all the time just from resting my hands on the keyboard. The PowerToys remap doesn't work on it. Any ideas appreciated.
# Posted By lynn | 2/2/21 6:59 PM
Lynn, are you referring to something different from the embedded number pad in the trackpad? If so, what "gesture" causes it, and what comes up upon that gesture? Just trying to assess how close that is to what I'm describing.

And have you considered all the options here, in the post and I comments?
# Posted By Charlie Arehart | 2/2/21 7:06 PM
I bought a VivoBook a few weeks ago and I do not know if it is a defect in the laptop or it is normal even though I do not use the laptop Numberpad activates itself and turns on and off without interruption.
# Posted By Gent | 2/3/21 6:59 PM
You mean like it's just blinking of and off? That would be terrible. Try removing the driver, like I said. See why happens.
# Posted By Charlie Arehart | 2/3/21 7:02 PM
Thanks for the fix! I recently purchased a ROG Strix G15 and this was one of the many issues making me regret blowing thousands on this piece of ****

Next up: disabling the RGB during sleep/standby and stopping the screen from pressing the power key every time I close the **** thing :"(
# Posted By Dr. A. Seuss | 2/14/21 2:10 AM
Hi Charlie, thanks for trying to figure this out. I use my Zenbook primarily to write and so find this an incredibly annoying bug - the numpad is very bright and if I don't disable it, it will flash in my several times a day, breaking my flow and concentration. I also got as far as deleting and uninstalling the driver only discover with despair that the damn thing returns everytime I restart my machine. As a result I currently go to the device manager every single day to uninstall it, which is a monumentally inefficient use of my time. It's enough to make me warn everyone considering a Zenbook to choose something else! If you do find a permanent solution, I'll be absolutely delighted - it seems crazy that Asus have made it impossible to just turn the thing permanently off. Good luck!
# Posted By Toby Hill | 2/15/21 11:59 AM
Thank you so much. This has been driving me 'round the twist for months and slowing down my work. So grateful!
# Posted By TS | 2/20/21 3:20 AM
To the last 3 commenters...

TS, glad to have helped.

Toby, try using a free key mapper, as suggested by others like I'd noted in the post (which I'd hoped to avoid, but could not). I will update the post to say I've since tried first power toys, then my favorite (and more targeted tool), sharpkeys. With it, I easily mapped the numlock key to act like a shift key instead. That leads to the numpad "button" on the keypad merely beeping when pressed, but having no other effect. And since the tool runs at startup, it's indeed permanent. And oh, what a relief it is! Google sharpkeys to find it and info on using it.

Finally, Dr Seuss: hit the Windows key and type power. You will see windows features for controlling things like whether the display (rgb) goes to sleep and whether hitting the power button does that or not. Let us know how that goes.
# Posted By Charlie Arehart | 2/20/21 5:55 AM
To Dr Seuss: on rereading your comment, I realize now your problems may be different from what I assumed. I suspect I won't have any good suggestion for those troubles. Sorry.
# Posted By Charlie Arehart | 2/20/21 6:04 AM
Ended up creating small project to disable NumPad https://github.com/n... .. does basically same as PowerToys but is 7kb only :)
# Posted By noxo | 2/23/21 11:33 AM
Wonderful, Noxo. Thanks, for both the code and the news, as well as the shout out in the repo.
# Posted By Charlie Arehart | 2/24/21 6:33 PM
Hi...i have a asus vivobook s14 s433jq that number pad turn on and turn off accidently And disrupts the performance of the touchpad .Does anyone have this problem? Is there a solution?
# Posted By Ali | 2/28/21 12:54 PM
Is yours like the one I show in the picture above? If so, several solutions are offered in my post and comments here.
# Posted By Charlie Arehart | 2/28/21 12:56 PM
Yes, it looks like this, but using these solutions, the number pad will not turn on, but the touchpad will still have problems. Of course, this happens sometimes and not always
# Posted By Ali | 3/1/21 1:10 PM
Your problem sounds unique. To be clear, no one else here has reported a problem with their touchad, once they had disabled the number pad using any of the solutions.
# Posted By Charlie Arehart | 3/1/21 9:43 PM
I installed PowerToys and it seems that it keeps this nasty NumPad functionality disabled. It´s a good integration idea, but Asus should fix it with a key solely to get it activated. My daughter was becoming desperate...
Thanks a lot for your perfect description on the solution.
# Posted By sims | 3/12/21 2:56 PM
This is very strange. I saw a similar problem on reddit where your page was suggested. However, the number pad still turns on and off, disrupting the touchpad, causing it to lag and jump. I also put the reddit link below, which had the same problem as mine. https://www.reddit.c...
# Posted By Ali | 3/14/21 3:48 PM
[See Forrest's corrected comment below.]
# Posted By forrest gump | 3/17/21 7:04 PM
Good Idea. Thanks for sharing it. With all these ideas, people should be able to find SOME solution that works for them. :-)
# Posted By Charlie Arehart | 3/17/21 7:16 PM
I'm sorry, there was a mistake and something missing in my previous post but I cannot find a way to edit it so I'm reposting with corrections (you can delete the previous post).

Thanks for the post.
For me the SharpKeys solution didn't work on an Asus E410M laptop (it didn't had any effect after key remapping and restart).

However I've manage to find a permanent solution that does work based on your original non-permanent suggestion to uninstall the device.
It entails simply creating a task that runs at startup as admin and uninstall the device from the command line. These are the steps:

1) Get the instance id of the device: Devices Manager -> Keyboards -> [right click on "ASUS Number Pad"] -> Properties -> Details -> Device Instance Path. You can right-click to copy that "path" (more like an ID) to the clipboard.

2) Create a new task (make sure to use the instance id from stage 1 where it says <instance_id_from_stage_1>):
Task Scheduler -> Create Task (not "Create Basic Task"):
a) On the General tab:
aa) Name [ fill ]
ab) Run whether user is logged on or not [ check ]
ac) Do not store password ... [ check ]
ad) Run with highest privileges [ check ]
ae) Configure for [ Windows 10 ]
b) On the Triggers tab -> New... -> Begin the task [ At startup ]
c) On the Actions tab -> New... -> Program/script [ %windir%\System32\pnputil.exe /remove-device "<instance_id_from_stage_1>" ]
d) On the Conditions tab -> Start the task only if the computer is on AC power [uncheck]

I hope it's understandable.
# Posted By forrest gump | 3/17/21 7:37 PM
Thanks for that update. I have edited your previous comment, pointing to the newer one.
# Posted By Charlie Arehart | 3/17/21 7:43 PM
I am experiencing the same problem on my Vivo S14
# Posted By Clint | 3/18/21 5:48 AM
Clint, which problem? That discussed in my post? Or something reported in one of the comments? If the latter, which one? And what you mean in reporting it?

Or are you simply identifying another laptop model that has the numpad? If so, did you try any of the many solutions offered here and in the comments?
# Posted By Charlie Arehart | 3/18/21 7:34 AM
Forrest, I have to say that your suggestion here on Mar 17 2021 seems to be the best solution for me so far.

For those who had not noticed it, he shows the steps to create a Windows scheduled task to remove the numpad driver on each restart. That solves the problem of my first proposal (removing the driver, which would just return on a Windows update.)

And though I had had good luck at first with the Sharpkeys approach, it proved not to work out well in the long-run (like my attempt with the Powertoys suggested by rmzetti).

(I have to say I never tried Noxo's free script on github--see his comment on Feb 23 2021--as it involves building code via MS Visual Studio. It may well suit other readers. And if somehow Forrest's solution doesn't work out long-term, I may have to give Noxo's a go.)

I have updated the blog post to point to Forrest's as my current preferred approach. And Forrest, I tweaked your comment just a bit to make a couple of minute clarifications that may help those who don't often create new Windows Scheduled Tasks. Again, thanks for the steps, which I fully credit you for!
# Posted By Charlie Arehart | 3/28/21 8:51 PM
I had a few issues with forrest gump's solution, where if I plugged in any USB device, the numpad driver would also re-install. The solution was setting the scheduled task to trigger on event Log - Microsoft-Windows-Kernel-PnP/Device Configuration, Source: Kernel-Pnp, Event ID: 400, as that's one of the events that is triggered whenever the numpad driver is configured/started. I would still like a solution where the driver is disabled permanently, so that my windows wouldn't have to reinstall/delete the driver every time I plug an USB, but it works for now.
# Posted By Anonymous | 4/3/21 5:30 PM
Ah, good point. Thanks for sharing both the problem and a solution. And agree on wishing Asus would save us from all this messing about.
# Posted By Charlie Arehart | 4/4/21 6:11 AM
Just to add a point of clarification about Forrest Gump's helpful suggestion of a Windows Scheduled Task (run at startup), I found over time that somehow something RE-ENABLED the bloody numpad EVEN AFTER a startup. Wow, it's like the Terminator...it "absolutely will not stop". But like Sarah Connor, we're not giving up.

Here's the thing: in this case, you can just run the task again, manually. (That might be obvious to some, but others might not be so familiar with Windows scheduled tasks.)

First, click the numpad button if it's on, to turn it off (because once we do the next step, that feature will be disabled.)

Then open the Windows Scheduler (click the Windows key in the bottom left corner and type the word scheduler to find Task Scheduler). Then in the UI that opens, select the "task scheduler library" on the top left, then in the list of tasks find the one you created (per Forrest's comment).

Right-click it and choose "run". That will do its thing instantly (to remove the device driver, again as discussed in Forrest's comment), right then and there, and your .

Frustrating that we should have to this (on top of the initial removal), but at least it works.

(And if you may find you have dozens of tasks in the Windows Scheduler and can't find or remember what you called it, sort by "next run time". This task won't have one, so should appear in a group of such tasks at the top of the list.)

To summarize: my initial blog post suggested a way to remove the device driver...but over time (perhaps multiple Windows restarts, perhaps due to updates), something would re-enable it. Forrest's suggestion went a step further, and ensured that ON EACH STARTUP the device driver would be removed.

Then my comment here is pointing out that whatever re-enables it can seemingly do it AFTER you have started up Windows (and AFTER Forrest's scheduled task has run on startup). Maybe it's that some Windows (or ASUS) updates are of a sort that can cause this driver to be re-enabled but without requiring a Windows restart. In that case, running the task will solve it.

Finally, perhaps someone (Forrest?) will do some digging and find that there is a way to trigger a task ON THE RE-ENABLING of the driver. Again, just shocking that we have to work so hard to "terminate" it, but we're nearly there.

Hoping instead ASUS will come out with an option to let us disable the feature once and for all.
# Posted By Charlie Arehart | 4/9/21 10:35 AM
As a follow-up, I have found that the above-mentioned scheduled task is NOT running at startup, like it's supposed to. But again the task can be run manually if ever the numpad is re-enabled.

Also, I will add that I found it does NOT matter if you have first "turned the numpad off" by pressing the button, before you run the task to disable it. (I was afraid that would leave it on and unable to be turned off.) Instead, running the task really does remove AND disable the numpad, again at least until something later re-enables it. Grr.

It may be that the best solution/compromise is to instead create a Windows shortcut which performs the action that Forrest listed in his scheduled task suggestion, and then that shortcut could be stored in the Windows Startup directory. I don't have time now to write that up completely, for those not familiar, but I leave it as a tip for those who understand what I'm getting at.
# Posted By Charlie Arehart | 4/24/21 8:21 PM
>Lynn, are you referring to something different from the embedded number pad in the trackpad?

Hi Charlie -- I'm referring to the calculator shortcut in the top left of the trackpad. I don't know if it's on all models but it's on mine:

Every time my left thumb brushes over the trackpad, the stupid calculator activates. I've mitigated this somewhat by putting a thin strip of cotton on it, covered by a piece of black tape, but it's the ugliest thing ever. I'd love to disable the calculator shortcut permanently.

(I remembered to subscribe this time so I'll respond sooner!)
# Posted By Lynn | 5/8/21 2:44 PM
I am using a simpler solution. Go into Device Manager>Keyboards>Asus NumberPAd. Select "Update Driver", then "Browse My Computer for Drivers", then "Let me pick from a list of available drivers".

Then what I am doing is purposely choosing an INCOMPATIBLE driver. This effectively disable the number pad but the device remains and is not installed. You can choose:
- HID Keyboard device (the device appears working in Device Manager but the number pad is effectively disabled)
- Deselect "show compatible hardware", choose any other driver. The device will then be highlighted as not working if you prefer.
# Posted By Ivan | 5/11/21 9:03 PM
Sweet, Ivan. Will give it a try. Thanks.

Lynne, I'm afraid I just don't know. Sorry.
# Posted By Charlie Arehart | 5/11/21 11:57 PM
Thank you so much for this post and follow-ups, Charlie. I really appreciate it! Of course, many additional thanks to both 'Forrest Gump' ['Run, Forrest, Run!!!' -said with all due respect: I love you and your wonderful movie] and Ivan. Charlie: might I suggest that you link to Ivan's comment right after you link to Forrest's?

I just did Ivan's method and so far it works wonderfully (have not restarted my laptop yet, so hopefully still holds after that...I suspect it will... thanks again SO much, Ivan.) Just to add a note for others to be totally explicit: after 'HID Keyboard device': click 'Driver' tab to get that 'Update Driver...' I selected 'Toshiba' because I have a dear memory that is related to a previous Toshiba laptop (which I will tell below.)

Firstly, I have to give an open note to the geniuses at Asus: this is my first Asus (and am very tech savvy incl a 10-key expert): I have been very impressed so far (a few months in) except for this exceptionally stupid and incompetent 'feature'. If you are going to attempt to reinvent the wheel and then RELEASE it, you really want to make it square shaped (the wheel, to be explicit)?? Outside of the continual idiot-crook-aholes in Belleview (to say nothing of the prick, deceased, utter-crook-sociopath founder from Cupertino and those now similarily carrying on his wonderful legacy or the 'do nothing but harm' dheads --yeah, slim pickings for tech corp America), you are a bunch of geniuses, eh? It really wants to make me never buy an Asus again, just to treat you accordingly. Others: there is a trillion dollar opportunity to simply (really aint that expensive; oh, and no credit to whom cannot make a mass linux devel..) start with a mobile OS then easily config it to laptops and biz machines. (Relatively --as opposed us to saving lives in the ICUs): e.a.s.y.

My toshiba great memory, which I've never told/written to anyone: this was about ?2005-ish??--one of earliest laptops-- or so and I had a bright copper-ish covered laptop--it was gorgeous and 17" so really stood out..great computer too. RIP Toshiba laptops. I was working in a corner of this tiny little library (on a backpacking/camping trip) in the mountains of Colorado. This girl about 7 or 8 kept sheepishly walking by me and looking at me and shyly smiling (the cover was facing outward towards her view.) I kept on looking up to see if she was still looking and she was, kept on passing by; it was kind of awkward like that feeling if I am wondering if my fly is open or something. Finally, she came up to me and said, "I really like your laptop...' It was soooo freaking adorable. This cover was really stunningly beautiful. I haven't used it in decade++, yet I think I still have it down in my basement. I haven't seen it since then, yet I can still picture it in my mind's eye--it was truly gorgeous. These many years later (and I would do it in a second now, yet, regretfully, didn't think to do so then) I am sorry that I just didn't stand up, unplug it, and give it to her (this was an area that was not $ rich, yet stunningly rich in nature... yet I bet she would have cherished it even way more than I did.) I don't know if I communicated this properly, yet it was so wonderfully fantastic. Incidentally, all these years later which would make it so easy for manufacturers to do (esp for a couple of colors like a great blue and this copper, plus pink* --all at the same price, def no crooked 'pink tax'*... *this is very real, very crooked: check it out.) Crooks quote: 'Pink it and shrink it'. *more free hints for tech biz. Dear little girl: it is many amazing kiddos and babies such as you which made me return to school for nursing after a successful career; you and yours'-equivalent profoundly inspire me every shift. (Incidentally, I'm a straight dude, who also loves life now working in the NICU... preemies are amazing, incredible badasses.)

Please forgive me, I won't check this site again (relates to the length of the post), yet remain grateful to you Charlie for providing this wonderful knowledge and platform. God speed!
# Posted By J | 5/19/21 4:26 PM
Actually, Charlie, I will go look in my basement and see if I still have it and then email you a pic (in the next few weeks), if so.

Aint life grand?? Especially, post-Covid vaccs?? Hal.le.lu.yah.!!
# Posted By J | 5/19/21 4:42 PM
Fyi all: restarted, still holds; again, I bet it will continue to do so (others wondering: should still if drivers update since the driver is incompatible.)

A million more thanks, Ivan!
# Posted By J | 5/19/21 4:59 PM
Argg, looks like I (we ;) -tho def w/my permission) must have rid that laptop in the last ~6 months-- I'm awfully tidy and have a lot of space yet finally decided to rid some past few areas during these quarantines --one of the few benefits from these tragic (and mostly preventable) times. Also, btw, this was not some super-high-end laptop, yet thinking that the cover was more 'metallic' finish. Again, fantastic looking.
# Posted By J | 5/19/21 6:55 PM
i don't get it. I read the whole article. Where is the solution that works? It's all stuff about what doesn't work. How do I do an autotask or whatever?
# Posted By Tom | 6/1/21 11:01 PM
Tom, let me address your disdain first with a brief explanation of how the article started then has evolved--as we as a group seek to find a solution. Then I will conclude with the current best solution working for me, which I will update the post to clarify.

To be clear, the post was written originally presenting what I thought WAS a working solution--and it did work for a while, as a more sophisticated solution than many simpler ones if seen offered. (I also listed those, so people wouldn't be tempted to propose them as "solutions".)

Unfortunately, in time, even what I proposed proved no longer to work, as something unexpectedly reverted things. It's as if somehow Asus (or Microsoft) have implemented something that thwarts every such attempt to permanently disable this feature.

As such, the post still stood as a confirmation of that challenge for other interested folks (and a plea to Asus, if they found it, to more easily solve this.)

Then over time folks offered still more possible solutions as comments, but none have proved to work *permanently*. Sadly, my current conclusion is that there seems to be NOTHING currently we can be do that will indeed *permanently* disable the feature.

But good news (to some) is that I can share a solution that for now seems to work best for me. It's a variation of what was offered by Forrest, who proposed a command to run as a Windows scheduled task at startup. Sadly, that did not help to PERMANENTLY remove it as again
the driver would somehow get reinstalled by Asus or MS after startup. Running the task manually was possible but clumsy.

So, instead, I have taken that command he had offered and I set up a Windows "shortcut" that runs it. Then I put a copy of that first into the Windows folder which allows me to run it from the Windows menu (so I can easily call it any time), then I also put a copy of that shortcut in the folder which causes it to run on startup (as an alternative to the scheduled task, which I frankly don't think really was running at startup--and I've found other posts indicating that problem, having nothing to do with this driver of course.)

I will revise the post to detail these latest steps, if they may help anyone. Until then, perhaps this comment will suffice to get you going.

It's a frustrating situation, for sure. And I hope you see better now how this post has been a reflection of the experience dealing with it. Still, I agree that I need to revise the post (as I've done before) to provide at the top solution that doesn't require people to read through the comments, unless they want to.
# Posted By Charlie Arehart | 6/2/21 8:37 AM
I want to add also (for the sake of completeness) that I had indeed tried Ivan's suggestion on 5/11/21 (at https://www.carehart...), for updating the driver to purposely point to an incompatible one. Sadly, over time I found that Windows or Asus changed that to be the "right" one (theirs, the one causing us all this trouble).

So that's when I finally resorted to the solution that works for me of creating a "shortcut" (see my last comment). And I have updated the blog post to more clearly specify that, for future readers.
# Posted By charlie arehart | 6/2/21 2:35 PM
This is the closest I've gotten to finding a solution, however, I want to call back to what Lynn said above and clarify as I have the same problem. Pressing the Numpad button at the top will turn on and off the Numpad and the solution posted here fixes this issue. However, if you swipe over the button from left to right, the Numpad will turn on but also the calculator is opened. Using your solution successfully stops the Numpad from activating, but the calculator will still be opened and it is extremely easy to accidentally perform the gesture and open the calculator. I understand that this post doesn't address the calculator and you may not have any insight, but I figured I'd ask. Either way, this page has been extremely useful, I'm just frustrated that Asus has not given us the option to do this in the settings.
# Posted By John | 6/10/21 4:04 PM
Hi, John. That's interesting. I'd never hit it, but I did just cause it. As you note, you have to click that top left corner of the mousepad, then swipe away. I just have never done that, so it's not as annoying for me (little consolation for you, I realize).

I don't see any device driver that could be removed, like we did above with the numberpad, so I don't know if it can be disabled. I also looked at the Windows mouse config UI, and though there are various things that can be configured, swiping on that is not listed (as it's an Asus feature).

But I will say that as far closing it when it opens, I found I could just repeat the gesture (swipe from the top left corner again), which is not too bad, since you are swiping anyway. (This is at least a BIT different from the numpad key--and perhaps less annoying, as that can be hit by mistake while typing, and one has to take their keys off the keyboard to tap it again to disable it.)

Finally, someone might want to note that like any Windows app that calculator can be closed "easily enough" with alt-f4 (or adding the fn key for those who have not swapped its behavior). But I realize that if you have your hands on the mousepad and do that swipe by mistake, it's equally annoying as the numpad to then have to go to the keyboard to undue that swipe. :-)

But you've registered your concern, and perhaps someone else in the future may chime in with some better solution for you. It's great to see a community rally around a problem and solutions. :-)

And yes, the BEST thing would be for ASUS to come up with an update that let us disable these things entirely if we wanted to.
# Posted By Charlie Arehart | 6/10/21 4:28 PM
I figured out a fix! Again, Lynn, if you are still here, this should fix your problem.

It's my mom's computer, so she has a hard time using the touchpad without accidentally activating it and I have tried to teach her shortcuts, but they never seem to stick.

The fix was so simple that I cannot believe that I hadn't thought of it before. I had tried all the previous things that you mentioned and I thought maybe it was a customizable gestures function, but it is not. I guess seeing the solution to the Numpad problem got me thinking differently for a solution.

Ok, so all you need to do is uninstall the calculator. Yes, it is a preinstalled app, but it is still uninstallable. If you still want a calculator, all you need to do is find a third party (not Microsoft) one either online or from the Microsoft store. That's literally it. I guess the Numpad only supports the gesture for the default calculator, so if the calculator is uninstalled, then obviously the gesture can't open it. Really facepalming that it took me this long to think of this solution, but better late than never.
# Posted By John | 6/10/21 7:55 PM
John, I appreciate your enthusiasm in share your "fix" for that calculator issue. I'll just say that my money is on that calculator getting REINSTALLED by Windows. It may be on a next uodste, or the next restart, or just the next login. The latter is what I find for the removal of the numpad driver. "MS knows best", they seem to think.

But we'll see. If it indeed "stays away", then good on ya for that solution. :-)
# Posted By Charlie Arehart | 6/10/21 8:02 PM
That' a good point, but luckily the computer had a backlog of updates (somehow autoupdates got turned off), and the calculator did not come back when they all finished. Fingers crossed it stays that way, I can see it rearing its head again at some point though.
# Posted By John | 6/11/21 2:53 PM
Hi all,

The task scheduler method to deactivate the numberpad works well for me, thanks !

Also, thanks a lot for all your comments and ideas about how to get rid of the calculator "numpad shortcut swiping" issue.
I guess this is more likely to happen to left handed people, like me, who use their left hand and fingers on the numpad, naturally closer to the upper left numpad "button".

I tried to uninstall the calculator as suggested by John, but on my laptop (Asus Vivobook S433E, win10) this action results in a more annoying effect :
Now, when accidentaly swiping over the upper left corner of the numpad, Windows opens a popup telling me to use the Windows Store to reinstall the calculator. This popup is less easy to close than the calculator, so it's even worse than before...

Any ideas to avoid it ? Thanks !
# Posted By Philippe Petit | 6/16/21 3:01 AM
Phillippe, has the task approach really worked over days and restarts? I would not for me. If so, then good to hear for your sake and perhaps others.

On the removal of the calculator, I'm afraid I have no more ideas for now. Perhaps others may chime in.
# Posted By Charlie Arehart | 6/16/21 6:48 AM
Charlie, the task approach really works over days.
Which triggers did you choose ?
Mine are those :
- At the start of the system
- At the opening of the windows session
- Everyday at 9:25 and then repeat each 30 mins
- When unlocking the work station
(sorry for the approximative translation of the triggers, my windows is in French).

This did the trick for me, no more blinking of the numberpad, no more unwanted activations.
Hope this helps !
# Posted By Philippe Petit | 6/17/21 3:15 PM
Ah, ok. Those 4 "triggers" would surely do the trick. :-)

To be clear, I had only done the one at startup (as Forrest had proposed initially, and as I shared in my comment on June 2).

And for the sake of others who may be tempted to follow Phillippe's lead, note that when Forrest's steps talked about using the "triggers" tab in setting up the task (as he notes, using "create task" rather than "create basic task"), that will offer these other options that Phillippe has proposed.

Thanks for the suggestion, Phillippe. I daresay that would seem to be the most complete solution so far. (I'm satisfied for now with my shortcut approach. But let's see if you or others might chime in after some more time to confirm if yours is a preferable approach.)
# Posted By charlie arehart | 6/17/21 3:36 PM
Hello. I have raised my problem before, but it has not been resolved. I think this problem only exists in the Asus S14S 433JQ laptop. After turning on the laptop, the pad number accidentally turns on and off, which also disrupts the function of the touchpad. I followed the above solutions. Wow, it was useless. Only the pad number turns off, but the touchpad still has a problem and crashes. If anyone has a solution to the problem with this S14S 433JQ laptop, please help. Thankful
# Posted By Ali | 6/22/21 2:23 AM
Hello. I have raised my problem before, but it has not been resolved. I think this problem only exists in the Asus S14S 433JQ laptop. After turning on the laptop, the pad number accidentally turns on and off, which also disrupts the function of the touchpad. I followed the above solutions. Wow, it was useless. Only the pad number turns off, but the touchpad still has a problem and crashes. If anyone has a solution to the problem with this S14S 433JQ laptop, please help. Thankful
# Posted By Ali | 6/22/21 2:23 AM
Copyright ©2021 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting