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.