Cant access K: drive on windows 10

[terozio]

After some time ago I have lost access to all folders in the protected K: drive. I have rebooted, reinstalled and done everything I can think of.

Keybase gui still works, I can use the chat and modify my profile. But I cant access any of the folders in K: and K: is not visible in Windows explorer either.

my log id: 8380e1820bc5406de524591c

[strib]

cc: @taruti

[zanderz]

This is an error caused by a failure to install the Visual C++ Redistributable. It will probably work if you uninstall those using the control panel and launch our installer again.

[terozio]

I uninstalled keybase and all the versions of VC++ redistributable. After that I reinstalled keybase but it ended up in the exactly same state. I still cant see or access K:

Generated new logs with the id: 0b6334e6963ee6c5d543781c

[zanderz]

I think the VC Redistributable installation errors may have been a red herring. You have everything installed, but our service thinks the Dokan drivers are not working (Dokan failed: code=-3 "Driver install error"). I assume you've rebooted since the reinstalls.

I see that you have Symantec Endpoint Protection (SymEFASI.sys) installed - did that happen to have been installed around the time your Keybase files stopped working? It is possible that the two drivers are incompatible.

[terozio]

I have booted after the reinstalls yes. I cant say when exactly symantec was installed, but I assume it has always been running since my laptop is managed with the corporate policies. I would assume there are many more reports if keybase is not working at all with Symantec Endpoint Protection.

[junderw]

It could also be a Group Policy to hide drive K.

Perhaps an IT admin was noticing some program mounting K drive, thought it was suspicious and decided to block K drive mounting?

[junderw]

Did you clear Keybase use with your IT dept. before using it on company hardware?

[xzenor]

I know this is an old post but maybe this'll help future visitors of this question. Check to see if the Dokan filesystemdriver is installed because that's what Keybase uses on Windows for the KBFS access. It should be listed in "Programs and features" as something like "Dokan Library" with a version behind it.

Without it, there's no K: drive. Keybase installs it the first time but if you remove it once, you can repair and reinstall all you want but the keybase setup will not install it again.

You can install the latest version from https://github.com/dokan-dev/dokany/releases. Reboot after install and the K: drive should be back.

There really should be a mention in the Keybase-setup about the Dokan filesystemdriver being installed. I removed it because I never heard of it, couldn't remember installing it and sure as hell didn't need it (or that's what I thought). A little heads up from the keybase-setup that they're installing a third party driver would have been nice.

[zanderz]

@xzenor Please mention your concern in keybasefriends/feature-requests. Last fall we changed the installer to not add the driver by default, and enabled a clickable message in the UI to install it as a second step.

[xzenor]

@zanderz oh that's what that message did.. it was unclear to me that that actually installed the driver. But anyway, once you manually uninstall the driver you no longer get the message.

I'll drop the request for making it more clear in the proper place.

[rivy]

I ran into this today.

After installing keybase, the tray window just disappears when I clicked on any kbfs folder. Installing dokany as directed by @xzenor and rebooting fixed the problem. I didn't see any message prompting installation from keybase itself.

But, anyway, there really should be an obvious warning or error message prompting installation of dokany when the user tries to use the kbfs without dokany installed.

$0.02

[zanderz]

@rivy Thank you for pointing this out, this is indeed a bug we're tracking internally with KBFS-2986.