Keybase installed a virtual disk system and software without even telling me

Seems Keybase just injected itself as K: drive on my system. There was no warning, no mention of that happening, just what seems like an auto-upgrade that did that.

Software should not behave as that.

Additionally, after I
a) figured out that "KBFS" is related to Keybase
b) found the menu option where "KBFS" is mentioned deep inside Keybase UI
c) turned off "Finder integration" (I'm on Windows, this is called "Explorer" not Finder)
I just got an error that "Dokan" was not found and I must manually uninstall that.

After doing that, it seems gone, but how many users will? What kind of thing is that, just injecting in this way, just assuming I have no other drive that's importantly remapped at K:, and without warning?

Start by reproducing the Windows behavior described: an unexpected K: drive, KBFS or Explorer integration, and the Dokan-not-found cleanup error. Determine the relevant Keybase installation and Windows integration entry points before defining the intended warning, drive handling, and uninstall behavior; done should include a verified, user-consented flow and clean removal.

Written by the indexing model from the issue text.