Windows client hard to get working

Keybase GUI Version: 1.0.14-20160303171223+229c1f1

Writing this issue allthough I guess it is hard to debug it:
on a Windows PC.
Have managed to make a 'k:\public\roelvanderplank' folder after a few tries.
Making a 'k:\private\roelvanderplank' folder keeps failing.

Tried making a 'keybase log send' but got the following errors, hence trying to write it all in here:

Continue sending logs to keybase.io? (type 'YES' to confirm): YES

• WARNING error opening log "D:\Data\rpl01081\AppData\Roaming\Keybase\keyb
  ase.kbfs.log": open D:\Data\rpl01081\AppData\Roaming\Keybase\keybase.kbfs.log: T
  he system cannot find the file specified.
• WARNING error opening log "D:\Data\rpl01081\AppData\Roaming\Keybase\Keyb
  ase.app.log": open D:\Data\rpl01081\AppData\Roaming\Keybase\Keybase.app.log: The
  system cannot find the file specified.

Success! Your log ID is:

3647c489e0459d6c3f81971c

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:%203647c489e0459d6c3f81971c

Thanks!

All errors when working from the UI, e.g. when opening an explorer and creating a folder. Errors such as https://www.dropbox.com/s/ekyqhxehh36h22a/Schermafdruk%202016-03-08%2021.27.02.png?dl=0 keep appearing.

So far I have succeeded in creating a single 'test.txt' file in my public folder, but managing the K drive from windows is not really a success... Cannot pinpoint as to what is causing the mayhem, sorry about that.

Kind regards,

Roel
P.S. Wanted to testdrive the keybase filesystem on my linux mint virtual machine as well, however, that is build as 32 bit, and there does not seem to be a ....ease.keybase.io/keybase_i_386.deb file in there to install... (The _amd64.deb obviously does not work)

No source file or test is identified. Start by reproducing the Windows GUI failures when creating public and private folders, then use log ID 3647c489e0459d6c3f81971c and the reported missing log files for investigation. Done means Windows folder creation works reliably and the relevant errors are covered by a reproducible report or test.