InReach Sync on Windows 10 can't find my InRease SE+

Activated my brand new InReach SE+ for the first time today and configured some contacts and custom messages. But my InReach Sync on my Windows 10 can't find the device so I can't sync my contacts and quick messages, nor can I do firmware upgrade. I have changed USB ports, USB cables, installed and reinstalled InReach Sync on my two computers, restored the SE+ to default and re-setup, rebooted my Windows 10. Nothing works. I have never been able to have the Sync recognize my SE+. Even Windows 10 File Explore didn't find the "drive". Help!!
  • If you haven't tried it already, you might try some variants as to the state of the device when you plug it in/start sync. For example, try running sync, plugging it in, turning it on. Try the same thing, but turn it on before plugging in. Also, try plugging in and turning on before starting sync.

    You might also try a an older Windows O/S if you have access to one. But I am fairly sure I've done a successful sync a time or two on Win10.

    Honestly, though, it sounds like you might have a bad unit. If all else fails, call Garmin support.
  • I wanted to share my experience with this issue. I've always found synching my SE+ from the inReach website to be clunky because users first have to negotiate a path to identify whether they are first time users or have already downloaded the sync utility. During this process, it appears a check is made to determine the version of the sync utility and download another version if needed. There is often quite a lag in time with no feedback provided to the user about what is going on. Most times the sync utility finally opens and synching commences, but sometimes not.

    I've discovered it's much simpler and quicker to turn on the Garmin inReach SE+, plug it into a USB port, then execute a file named "SyncDesk.exe" which on a Windows 10 systems resides in folder "C:\Program Files (x86)\Garmin\inReach Sync". Synching commences immediately without any need to open a web browser. I assume the preceding details are similar for Mac systems and for inReach Explorers.