Windows Client Timeout Error - Win10x64

If I recall correctly, all I did was close the window for the Keybase FS passcode on my machine. The window closed, but I instantly got an error that something had gone wrong with the filesystem and I should submit a log. So I ran the log send command from the shell, and got this:

my log id: 82460ae8a9c5d3cef943891c

Also I think there was a problem generating the logfile, so this might not be super helpful. Here's the full output:

C:\Users\[USER]\AppData\Roaming\Keybase>keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): YES
- WARNING error opening log "C:\\Users\\[USER]\\AppData\\Roaming\\Keybase\\keybase.start.log": 

open C:\Users\[USER]\AppData\Roaming\Keybase\keybase.start.log: The system cannot find the file specified.

------------
Success! Your log ID is:

  82460ae8a9c5d3cef943891c

Here's a URL to submit new bug reports containing this ID:

  https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%2082460ae8a9c5d3cef943891c

Thanks!
------------

Start with the Windows client’s KBFS passcode-close flow and the keybase log send command, using log ID 82460ae8a9c5d3cef943891c for context. Reproduce the reported filesystem error and determine whether the missing keybase.start.log warning is related; done means the cause and a verifiable fix are identified.