HI all
I tried the regedit solution a few months back and it worked perfectly.
The only problem is I cant enable the touch now! been trying to change the value back to 1 but doesn't do anything...
any ideas?
thank you
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In this forum there are a dozen threads that ask the same question: How can I permanently disable a defective touchscreen in a Windows 10 device so that I can continue using the device without being disturbed by the faulty signals from the touchscreen.
Unfortunately in none of those threads (at least not those I've found) the question is answered properly. Instead the helpers fantasize about the device manager (which doesn't work since Windows just reenables the disabled device at the latest when rebooting) and claim that there is no other solution in Windows.
Luckily there actually IS a solution which I'll explain now:
(0 = touch disabled, 1 = touch enabled)
After rebooting the touch functionality should be disabled permanently and therefore your problem solved.
(I could not give this solution to the already existing threads because unfortunately they have been closed with no correct answer... hope someone in the future finds this ...)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
HI all
I tried the regedit solution a few months back and it worked perfectly.
The only problem is I cant enable the touch now! been trying to change the value back to 1 but doesn't do anything...
any ideas?
thank you
For the registry to update all users you need to login with Administrator account.
(0 = touch disabled, 1 = touch enabled)
Sorry, lost you at "DWORD"....
That did not do anything with this New Windows 10 version. Windows insists on reinstalling drivers for hardware it finds, disabled or not. It's VERY annoying, Microsoft!!!
Thanks for this post. Tried the device manager approach only to have it re-enabled on restart. This fixed my problem even after re-boot.