keybase / keybase/client

after update all executables are gone

Open
#14,131 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

installer windows
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Keybase GUI Version: 2.7.2-20181003093825+89c6c11dc6

I've been having this issue for a while now...
Keybase does an automatic update after wich I've lost all executables and I can't use it anymore.
Reinstall doesnt work, repair doesnt work, only remedy is a full remove and repair (using some microsoft utility) and then reinstall.

Anybody else have something similar?

I'm running it on Windows 10, machine is in a domain (another Win8 in domain doesnt have these issues), only one info line in the updater log (Error opening uninstall subkeys: File not found), the actual msi log has a few lines of interest (upd.exe is being held in use, RemoveLegacyBundle could not be run, and Config.msi folder could not be deleted) but it does end with Keybase -- Installation completed successfully.

Any advice? Thx!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start with the updater log and MSI log on Windows 10, focusing on the held upd.exe, RemoveLegacyBundle, and Config.msi messages; done means an automatic update leaves the executables usable and repair or reinstall succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
desktop, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.