I have been reading this forum all over but I can't find a clear answer. Maybe I am late in facing this problem.. I have an old laptop, twin tablet Acer Iconia, It did pretty well until 1511 but the next updates killed the touch function. I was satisfied with it until MSFT decided I could not keep it at 1511. It just reinstalled 4 times and I keep rolling it back. Anything I can do? I am thinking of pointing it to a dummy WSUS.
The machine is running W10 Pro from standard WU cycle. It started as W7 or W8.1 and was upgraded automatically up the ladder. When 1607 came up the touch stop working, I rolled it back to 1511, the same happened for 1703. Now MSFT won't take no for an answer In short I would like this machine to stop upgrading since the touch hardware is no longer supported.
This is pure gold. Now I will have time to look for a permanent solution for my touch screens, yes this laptop is basically 2 tablets with an hinge.
What did I miss here? I just wanted to make sure everybody that contributed to solve my problem received their due.
Tiger didn't see that you liked the solution after Mr.X posted the link here, i posted you liked the linked post after that, not before
Have you contacted the Acer Service Center in your country? If not, that would be my first way to go! Now, if the initial driver was for Windows 7, means that Laptop/Tablet was designed for Windows 7, it's likely that that the Touch Screen will work in Windows 8.1, but Windows 10 later builds. What you could try is: extract the TouchScreen Driver from 1511 first. After that upgrade to 1607, delete the installed Touch Driver after full install and use the extracted Touch Driver from 1511 to install without to restart (important) the machine after the deletion of the Touch Driver from 1607. If that works, do the same for 1703. And again, it's important that you didn't restart the machine after deletion (NOT uninstall!!) of the new Touch Driver!! That way worked on 2 Tablets of friends of mine, one Acer, one Lenovo, which had the same problem.
Nice approach. I suspect it would not work because under 1511 it uses a mixture MSFT default system drivers and a Cypres windows 7 driver. under 1703 everything shows up as working, no errors in device manager. When I try using touch, fingers are detected but do limited actions. If I disable multitouch the mouse pointer appears and I can move it with my fingers. The first thing I will be looking for is a valid diagnostic tool for touch. This in itself is a project. It is hard to get good ones for mouse or keyboards. Not only is it a question of drivers but also of how the system responds to those drivers. This will be a nice winter time problem tosolve.
I am still trying to grasp all the implications of LTSB. I needed an immediate solution to stop the thing from updating every few hours. I will now have the time to do the required reading and learning. Thanks!