keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.9k stars 1.23k forks source link

Attached are the error message I receive when trying to update to the latest version. #20374

Open JPanter-NT opened 5 years ago

JPanter-NT commented 5 years ago

my log id: 8139425aa690d43f76c18f1c

Keybase Upgrade Error - 2019-10-15 As per Log ID, Attached are the error message I receive when trying to update to the latest version.

my log id: 8139425aa690d43f76c18f1c

maxtaco commented 5 years ago

This is a very old version that you might not be able to upgrade from. Can you uninstall the app and then reinstall it from our web site?

JPanter-NT commented 5 years ago

Hello, I receive the same error when I try to uninstall.

I’ve had this issue with another application, and the provider was able to send me the old installation file for the version it was requesting. With this, I was then able to point the uninstaller at the old file and uninstall, then reinstall the current version.

Is that an option?

Thanks,

Jason


Jason Panter Manager, Information Systems & Technology Education & Training Division Aurora College

Phone: 867-872-7010 jpanter@auroracollege.nt.camailto:jpanter@auroracollege.nt.ca

From: Maxwell Krohn notifications@github.com Sent: Tuesday, October 15, 2019 10:30 AM To: keybase/client client@noreply.github.com Cc: Panter, Jason jpanter@auroracollege.nt.ca; Author author@noreply.github.com Subject: Re: [keybase/client] Attached are the error message I receive when trying to update to the latest version. (#20374)

This message is from an external sender. Be cautious, especially if opening links or attachments.

This is a very old version that you might not be able to upgrade from. Can you uninstall the app and then reinstall it from our web site?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/keybase/client/issues/20374?email_source=notifications&email_token=ANP2XCET2TLUT552C37V4Z3QOXVWVA5CNFSM4JA65SCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJM5BI#issuecomment-542297733, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANP2XCFQTR2IPLU7ZLCRIMTQOXVWVANCNFSM4JA65SCA.

earthbound19 commented 5 years ago

I encounter the same issue trying to upgrade from the relatively much more recent version v4.4.1. The .msi was cached in:

C:\Users\<my username>\AppData\Local\Temp\KeybaseUpdater.blah-blah-blah-blah-junk-string-mcBlah\ and the new installer tries to run the old installer (to uninstall it) from that path (and stops and prompts me to locate the file there), and it can't find it because I give a hooey for good computer maintenance and routinely clean temporary/junk folders.

If new Windows installers are also caching the msi in a "temporary" location but treating it as a permanent location, that is an issue. No msi installer should be "permanently" cached in a temporary location.

Unfortunately no .msi for 4.4.1 seems to be available anywhere, or I'd drop it into that temp location so it could uninstall properly. I'll have to use one of the billion cottage industry actually-uninstall-that windows uninstaller tools to be rid of the old program so that I can upgrade. Will the hack uninstall also find and wipe cryptocurrency stored in one of the monster labrynthine Windows user data paths? If so, can my backed up keys restore access to it from some blockchain ledger thingy shared by all nodes in the network? That remains to be seen. I do have a bit of the keybase-affiliated crypto..

Note that caching the installer in a temp folder also breaks uninstall (it won't be able to run the .msi to do a standard uninstall via Windows' control panel -> programs and features) if users do sensible things like routinely clear junk folders.

earthbound19 commented 5 years ago

Properly solving this issue means having new installers be able to uninstall the old program whether the old msi is around or not.

magneticflux- commented 4 years ago

I encountered this issue on v5.1.1.

It also seems to be exacerbated by using Chocolatey to manage the install.