Aspire R5-571TG missing hid touchscreen drivers

Jameshuttonitpro
Jameshuttonitpro Member Posts: 3 New User
edited October 2023 in 2020 Archives
A customers Aspire R5-571TG came in for a DC jack replacement. I noticed that the touchscreen doesn't work. Updating it thru Acer or Windows Update was unsuccessful in this aspect. Copying drivers from the local Windows Store on an identical model also met with negative results. Driver searches on the web just yield links to malware. I need the driver. Any ideas?

Answers

  • JackE
    JackE ACE Posts: 45,213 Trailblazer
    Does DeviceManager show any red or yellow warnings? Some models may be equipped with non-touch LCDs. All available ACER driver update downloads can be found in this link https://www.acer.com/ac/en/US/content/support-product/6761?b=1

    Jack E/NJ


    Jack E/NJ

  • Jameshuttonitpro
    Jameshuttonitpro Member Posts: 3 New User
    No, the touch device just doesn't show up I'll try the link again. thinking about resetting the PC
  • JackE
    JackE ACE Posts: 45,213 Trailblazer
    Check DeviceManager's HID folder. The driver should show up as an HID-compliant touch screen if installed. If it doesn't show up it's likely either not a touchscreen-equipped model or the touch cable has come loose or has a break. The driver itself is generic part of the Win10 operating system like a mouse usually with a WinXP era 2006 datestamp. Jack E/NJ 

    Jack E/NJ

  • Jameshuttonitpro
    Jameshuttonitpro Member Posts: 3 New User
    JackE said:
    Does DeviceManager show any red or yellow warnings? Some models may be equipped with non-touch LCDs. All available ACER driver update downloads can be found in this link https://www.acer.com/ac/en/US/content/support-product/6761?b=1

    Jack E/NJ


    You know this was so long ago I don't know what we did to fix that thing. Thank you for your input
  • JackE
    JackE ACE Posts: 45,213 Trailblazer
    Thanks for reporting back. I'm gonna guess it was an automatic Win10 update that messed it up.  And then another later automatic Win10 update that fixed it. I suggest that you make sure ControlPanel's restore point app has SystemProtection turned on so automatic restore points are created when the high probability of another errant Win10 update strikes and messes something else up.   :)   Jack E/NJ

    Jack E/NJ