keybase / keybase/client

Windows KBFS with Dokan not working when booting up (but manual start working)

Open
#23,510 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

After installing keybase on my Windows 10 Pro (20H1 preview, slow ring, build no 19041.172) PC I figured out that if Keybase starts on startup, KBFS goes into an invalid state where the K: drive exists but is unaccessible. If I disable the startup entry and launch keybase manually after start up, the drive mounts ok (same happens if I reopen keybase if it opens at startup). I am guessing this is an issue with the way keybase handles KBFS by mounting it on start and doing it too early. Would it be possible to implement a delay?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Windows 10 startup path with KBFS and Dokan, then compare it with launching Keybase manually after boot. Trace when the K: drive is mounted during startup and identify whether delaying that work avoids the inaccessible state. Done means KBFS mounts accessibly when Keybase starts with Windows, without requiring a reopen.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
operating-systems
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.