keybase / keybase/client

Update to latest version on Windows Server 2012 fails when I'm not logged in as admin

Open
#8,378 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

On August 12, 2017, I updated Keybase on one of my Windows Server 2012 machines to Keybase's latest version at the time, 1.0.27-20170811082951+e587022.

Normally I am not logged in as local admin of the machine. My user account does have admin privileges.

Keybase was unable to complete the update. I had to perform manual steps to resolve the issue and make Keybase work again.

The problem was that the updater places an update application in my temp folder, to be executed upon reboot of the machine.

In Windows Server 2012, my temp folder is not a trusted location, and thus Windows will refuse to execute applications that are scheduled as Run, RunOnce, via scheduled tasks, and similar.

Executing the update manually fails as well.

To resolve, I had to move the update application into the system's temp folder, log in as admin, and run it from there.

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 by tracing the Windows updater path that places the update application in the user's temp folder and schedules or executes it, then reproduce the failure on Windows Server 2012 without an elevated login. Done means the update completes without requiring the reported manual move and administrator login.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
operating-systems, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.