Touchscreen Not Working After Update – Factory Reset Temporary Fix for S62

’d like to share my experience regarding the touchscreen issue on the Garmin Approach S62, which I believe in over 90% of cases is caused by a software problem.

If your touchscreen becomes unresponsive after a software update (often triggered by pairing with an iPhone), factory resetting the device multiple times can temporarily restore functionality.

Here’s what worked for me:

  1. Perform a factory reset — not just once, but 3 to 5 times if needed.

  2. Wait at least 5 minutes after each reset is complete. The touchscreen may suddenly start responding during this time.

  3. Once the touchscreen is working, go through the initial setup but DO NOT pair the watch with your phone.

  4. If you pair it with a phone, the watch will auto-update the firmware again — and the touchscreen will most likely stop working again.

Unfortunately, I haven’t yet found a way to install an older firmware version, which I believe would solve the issue permanently. But until then, this workaround has allowed me to at least get the touchscreen working again.

Hope this helps others experiencing the same issue.

  • I have an issue with the up / down + and - signs don't work when they are placed up and down over the last week.  Hard to switch to the next hole when these don't work.  However, the + / - keys that are horizontally configured work fine. .  I have gone through 2 rebootss.  Initially it works when recording weight, then it stops when entering anything else.  

  • I have the same issue, after a factory reset i can't even select the language as the touch screen doesn't work

  • I have same issue, touch screen suddenly stopped working, even after multiple resets it still don't work.

  • If the touchscreen is not working, Garmin Support would have to be contacted so you can discuss the concern live with an expert so they can determine further a solution going forward. 

  • This is essentially the issue I am having.  (Approach S62.)  It's clear that this is a software/firmware issue rather than hardware as the touchscreen works for 15 to 30 seconds before stopping again.  Garmin's "solution" was to send them $140 for a refurbished unit that they would graciously warranty for like 90 days or whatever.  I can't imagine sending them more money to fix an issue that their update caused.  Guess I'm in the market for a new smartwatch as this thing is now unusable.  Not a great look for a $500 device or the company that makes it.  

  • I am sorry to see you are experiencing issues with your Approach S62 resulting in your watch needing to be replaced. 

    If a replacement was offered as a solution, then there is an issue determined with the hardware on your Approach S62, and if you were advised there would be a repair cost, this means your device is outside of the warranty period by a bit as Garmin Support does not make a habit of charging a device just fell outside of the warranty period and is requiring a repair solution. If the device is a few years out of warranty, then offer the exchange at a price that is relative low not reflective of what 3rd party retailers sell remaufactured or refurbished S62's 

    The cost you mentioned being quoted, is priced in a manner that allows the device to be replaced for almost a 1/4 of the original cost if you are in the US domestic shipping being provided for free on the replacement, and the UPS return label is also provided for free to send your device requiring repair back to us. 

    Garmin does not offer a repair exchange unless it is completely necessary, as we do not offer remanufactured replacement devices for sale unless a repair solution is needed.  The repair cost is also priced in a manner that is on the lower end cost-wise compared to the repair costs for smartphones/laptops. 

  • The fact that the touchscreen works at all after some factory resets leads me to believe it's not a hardware issue.  But while I appreciate this individualized attention to my post, I just can't see a reason to get back on the Garmin bandwagon.  If it is software and/or firmware, this should be a cheap fix.  That I'm not the only one with this issue suggests it's more systemic and less anecdotal.