keybase / keybase/keybase-issues

Windows 11 Updates appear to break KBFS

Open
#4,279 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I'm experiencing a condition whereby Windows 11 updates are installed automatically, causing KBFS to break; the "K" drive is reported in Explorer as a local drive. The workaround currently in place is to rerun the Keybase installation (APPS -> Keybase -> Modify), which reconnects KBFS to the Keybase service. The Windows client is the latest available at keybase.io

Windows Updates have been paused for as long as possible in the meantime, but this can't be the long term solution. Looking for guidance.

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

Start with the Keybase Windows client and installer, using the reported Windows 11 update as the trigger. Reproduce the state where Explorer reports the K drive as local, then compare it with the result of Keybase installation's Apps -> Keybase -> Modify. Done means identifying why KBFS disconnects after updates and confirming the K drive reconnects without reinstalling.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.