2.14.12 is here

isazi

@radu-negoescu I have only had your kind of issues running a virtual machine.

Radu Negoescu

@isazi this is not a virtual machine. and the fact that drag&drop install works but suuntolink normal install doesn’t points to an issue not related to my setup, as far as I can understand it at least …

surfboomerang

@radu-negoescu Maybe someone from Suunto who knows the firmware update process can tell what the difference is between a “normal” update and the drag&drop method?

To me it makes no sense why the first one fails altough the firmware seems to download correctly because the update started and the second one succeeds.

@radu-negoescu even if @j-dominguez case was a bit different, I have a feeling that maybe there is a relation between the two cases: can’t download firmware file vs. corrupted download?!

cosme.costa

@radu-negoescu In other posts that people have commented this issue it was related to a faulty cable, could be the case?
The other people could charge the watch without problems but when was related to updates then they have this issue.

Radu Negoescu

@cosmecosta I’d be surprised if it was the cable. It is the same one that works for the “manual FW update”

Radu Negoescu

@andrasveres this might actually make sense. if only there was a way to capture the automatic download? where is it hiding?

@radu-negoescu not sure about that, but it might be in %appdata%\Suuntolink folder as most of the files are stored there.

Radu Negoescu

@andrasveres nope, first place I looked, no recent files matching

@radu-negoescu then I have no clue. You are looking into Roaming and not the Local folder under AppData, right?

cosme.costa

@radu-negoescu said in 2.14.12 is here:

@cosmecosta I’d be surprised if it was the cable. It is the same one that works for the “manual FW update”

I do not know but maybe using the automatic update it make some checkings that fail due the cable…if you can access one easily I think it worth to try.

I don’t think its an issue with the watch, like corrupted firmware, because you do not have problems with the watch between updates. For what you tell us the issue is only when updating, so can only be cable/suuntolink/computer permissions. I would discard computer permissions because the update wouldn’t start, at least this is my experience with my work laptop connected to my work network.

BTW I have updated mine using WIN10 PRO 64 bit as you are trying

Radu Negoescu

@andrasveres I wasn’t

What do you guys have?

@radu-negoescu the new firmware download link was posted a while ago, you could download that and compare by content to check if they match.

Radu Negoescu

@andrasveres they are identical

cosme.costa

@radu-negoescu I have the same. As I have told you, check the cable…

@radu-negoescu you compared by content or hash I guess. I have no clue then, it might be what @cosmecosta said: cable or SunntoLink problems.

Update: you can get an MD5 hash for your file and compare to what appears on @cosmecosta posted image too.

Radu Negoescu

@andrasveres yes, by content and md5 hash too. Since I don’t have a spare cable, this is not something I can check. Let’s see if I can convince my wife she really wants my S9Baro so I can get the titan

But you want to hear something truly weird? drag&dropping the FW downloaded by SuuntoLink leads to the exact same error (disconnected watch after the first reset), whereas drag&dropping the manually downloaded FW works (even though it also throws a watch disconnected error at the very end, upon reset version 2.14.12 is installed!?)

Occam’s razor says faulty cable and lucky break on 2nd attempt, but … but … seriously?

surfboomerang

@radu-negoescu Try a different PC first?

Dimitrios Kanellopoulos

@radu-negoescu can you please send logs from suuntolink and pass me the I’d ?

@radu-negoescu the beauty about IT is that there is always something that breaks It can be easily a faulty cable too (broken contact and it gets okay as you move it a certain way) or your SuuntoLink installation (as @surfboomerang suggested, you can try on a different PC).
As suggested by @Dimitrios-Kanellopoulos send in the log files to Suunto so they can check what exaclty is happening.