Newbie struggles with Windows integration

I understand that Windows integration is not first-class yet, and some of the following is user error, but here are some problems I ran into. Even generating this bug report via keybase log send in the shell generated the following error:

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

• ERROR Error (InstallLogPath): open KeybaseInstallUpload.DDY57ELIJ33JJIEUEV6WS6IN3ABLGQWP.log: The system cannot find the file specified.

I've been trying to create private shared folders, and first I thought you needed to create them, which (as you presumably know) doesn't actually work, either in the keybase shell or in Windows Explorer. For example, if I type "mkdir acertain,bac" when I'm in my private directory, the command silently doesn't do anything. If I try to do it from Windows Explorer, I get a variety of error messages. Right now, I'm in the state where Windows Explorer tells me that I have two folders in private: "acertain" and "New folder." If I try to rename "New folder," I get that the action can't be completed because it's open in another action. If I try to create another new folder, I get (after getting the spinning circle for 5-10 seconds) that the folder name I am creating is too long.

After some experimentation, I discovered that folders can be created just by cd'ing into them from the keybase shell, so that was cool. I created a file in acertain,bac called hello.txt from the keybase shell (echo "Hello, Brad!" > hello.txt), but since it seemed to hang, I control-C'ed it. Then when I tried to edit it from Windows, it told me that the file was in use (even five minutes later). I could at that point create a new file in that subdirectory, though.

my log id: 6a4ea4e5c71cd811e3f0d01c

Start by reproducing the reported Windows Explorer and keybase shell behavior for private-folder creation, file locking, and keybase log send, using the provided log ID for the upload error. Compare the observed errors with the expected behavior and determine whether the symptoms share one cause or need separate fixes. Done means the reproducible Windows issues are fixed and verified against these scenarios.