search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
900 stars 37 forks source link

KBFS on Win 10 Fails #3319

Open sdosremedios opened 5 years ago

sdosremedios commented 5 years ago

K:\ drive is not mounted and directories are inaccessible. Reinstalled keybase and kbfs; no improvement. Worked for months, until December Windows Update.

screenshot 5

maxtaco commented 5 years ago

cc @zanderz

zanderz commented 5 years ago

Please check the files tab - we shipped new drivers with an important security update, so you will need to follow the prompts to remove the old one and add the new one. paste

rivy commented 5 years ago

Same problem here...

I uninstalled the old driver, rebooted, installed the new driver, rebooted, ... the "K:" drive is inaccessible.

keybase ctl restart brings the system back up to accessibility for explorer and the shell.

Version info ...

C:\Users\Roy>ver

Microsoft Windows [Version 10.0.16299.785]

C:\Users\Roy>kb version
Client:  2.12.3-20181221135356+d161abd500
Service: 2.12.3-20181221135356+d161abd500
rivy commented 5 years ago

Problem resolved with Windows 10 update ...

C:\Users\Roy>ver

Microsoft Windows [Version 10.0.17134.472]

It looks like you have a minimum version dependency now.

rivy commented 5 years ago

I'm still having periodic file system drop-outs requiring keybase ctl restart to fix. Generally, it seems to happen after restarting from sleep/hibernation.

C:>ver

Microsoft Windows [Version 10.0.17763.292]
ygol commented 5 years ago

I have the same problem under Win10 version 1903 (OS Build 18362.10019). Uninstalled previous version and installed latest. "keybase ctl restart" I regain access to drive k: and after a few minutes I lose access again. [The system cannot find the path specified. (3)]

my log id: 874b58914da5b1be6310e41c

Lanie-Carmelo commented 4 years ago

I'm having the same or a similar issue. File Explorer integration works for a few days at most, but then when I try to access the K: drive again I get: "Location is not available K:\ is unavailable. If the location is on this PC, make sure the device or drive is connected or the disc is inserted, and then try again. If the location is on a network, make sure you’re connected to the network or Internet, and then try again. If the location still can’t be found, it might have been moved or deleted." I usually have to do an uninstall of the driver, reboot, and reinstall to fix this but that only helps for a few days again. By clicking on K: in the Keybase settings, I found this error: Error: Unable to open/stat file: K: at file:///C:/Users/lanie/AppData/Local/Keybase/Gui/resources/app/desktop/dist/main.bundle.js:1:4143701 at FSReqCallback.oncomplete (fs.js:158:21) I'm on a Windows 10 Insider build but I've had this issue since I started using Keybase a few months ago, and my Windows 10 version number has changed several times since then, so I don't think my Windows 10 build is causing the problem.

JamesAtMLP commented 2 years ago

I have been having the same issues. Keybase is critical for our work. I have been though all the uninstalls and re-installs of kb and dokan. I have even installed a band new version of Windows 11. -With a scratch install of Win11 and no other s/w installed, no antivirus/ no f/w -install kb -enable explorer integration - All looks OK

The first error i can find in the log is file: keybase.kbfs DialSocket -> ERROR: open \.pipe\kbservice\Users\james\AppData\Keybase\keybased.sock: the system cannot find the file specified.

kb log id: 203666b52b34426dc30028301c

JamesAtMLP commented 2 years ago

I've found a solution. It's a bit of a dirty workaround, but it works for me.

After starting the GUI from the Windows start menu KB hangs on load. then, from a cmd prompt type c:\keybase ctl start (this will allow the GUI to start) the type c:\kbfsdokan K: (this starts dokan and allows the files bit to work)

I've put these commands in a batch file, i cant find an elegant way to make this work on windows startup / login as the batch file just runs a leaves the terminal window open and then kills the doken stuff on close.

so i created a shortcut to run the batch file and set the shortcut to run = minimised

Now, after restart, I run KB manually from start menu and double-click the shortcut. This seems to work for now.

Hope it helps