Ask a Question

[Closed] Problem with auto_update on Windows Skipper 3.0.1.1129

0 votes
asked Oct 10, 2014 in Solved by d.deboer-axtion (210 points)
recategorized Oct 10, 2014 by ludek.vodicka

It looks like Skipper auto-update thinks the machine is a Unix-arch and therefore create a wrong reference to the update paths.
Same issue occured with the auto-update yesterday, which made me do a clean install.

Screenshot

1 Answer

0 votes
answered Oct 10, 2014 by ludek.vodicka Skipper developer (140,450 points)

It's really strange. And your 3.0.1.1129 version detected some new version to download?
Or which version you originally had?

Can you check how Skipper detects your computer through following dialog? :

enter image description here

commented Oct 10, 2014 by d.deboer-axtion (210 points)

http://ibin.co/1dDnBUAaQ1Cb

There it is

commented Oct 10, 2014 by ludek.vodicka Skipper developer (140,450 points)

This seems to be ok. Which version caused this invalid update?

commented Oct 10, 2014 by d.deboer-axtion (210 points)

An update to version 3.0.1.1129. I'm not aware of the buildnumber of this version.

commented Oct 10, 2014 by ludek.vodicka Skipper developer (140,450 points)

Based on your updated screenshot this doesn't looks to invalid OS detection, but rather to some invalid access/permissions in your temporary folder where Skipper stores update files.

I have tried to update it from previous 3.0.0 version and update was successful. Unfortunately I don't know how to reproduce it. Please let me know if this problem occurred again on your side.

commented Oct 10, 2014 by d.deboer-axtion (210 points)

Okay. As a quick fix I uninstalled it and performed a clean install.

commented Oct 10, 2014 by ludek.vodicka Skipper developer (140,450 points)

Ok, sorry for these complications.

Snow Theme by Q2A Market
Powered by Question2Answer
...