![]() Since doing the last option, I have no longer have the problem, and others have attested to the same. One last thing: set the task to run as the "system" account, as I discuss in this comment. Reading my discussion of my original idea of removing the driver (the previous bullet here) may give useful context. For those, see this comment from Forrest, then this one from Philippe and then this one from me and another). For now it seems the best ideas is that from "Forrest" of creating a Windows scheduled task to do the job, along with "Philippe's" suggestion of how to cause that task to run on each startup or login, etc.As for my subsequent idea of removing the driver via a shortcut, that could be run on-demand, that may well be an option to consider if somehow the next, more automated solution doesn't work for you.Some may want to consider also "Ivan's" idea below of changing Device Manager to point to a "wrong" driver: see this comment, but it's another option which proved not to be permanent for me.As for my original idea of removing the numpad driver from Windows Device Manager, as I discussed below here, that option proved not to be permanent: something kept putting it back.I discuss that here (and others commented it worked for them), but I and others wanted to avoid installing such tools (autohotkey, powertoys, sharpkeys, etc.) if possible Some folks may be open to 3rd party tools to remap the "num lk" keyboard shortcut which has helped some.In time, I may revise this post again (or create a new post) offering the options and their steps spelled out in my own words. For now I link here to either the text of mine or the comments from others or myself which discuss each one. The best seems to be the last one in this list, creating a Windows scheduled task that removes the driver and runs on startup. You could alos read the comments (now over 100 of them).īut to cut to the chase, here in brief are the few options that worked. ![]() Those who are gluttons/have time can read on in my post here for what I'd originally written (including what I found before that did not work, and what I initially tried-that also did not work permanently). Folks "just wanting a solution" should try that. ![]() So I have revised this post (in Sept 2022) to now highlight right at the top here a list of the most successful few of the various solutions, ending with the one that seems to have worked best. (Again, some proved to be more "permanent" than others.) But great news is that many folks following along here (since the original posting of this in Dec 2020) had offered ideas which worked for them. ![]() But over time even that did not work PERMANENTLY. First, I had found some proposed online (which did not work for me), so I created this post to share what I found an initial solution that did work. To be clear, there are indeed various "solutions". 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?Īre you annoyed by that behavior, and all the more that you can't find how to "permanently" disable it? In this post, I discuss ways to try to do it, including the one solution that finally worked best for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |