My first impressions as a Windows user

TL;DR: Everything seems to be OK in a starting point. I've managed to import a gpg key, proof twitter and GitHub.
There is a bunch of tiny UI problems although. Starting from the beginning:
- You can add an installer option which adds the keybase install dir to the PATH variable. Searching for the "Keybase Shell" shortcut is not always convenient (yes, Windows users do use command line)
- When the website invited me to add a public key without a private key in the very beginning, I haven't manage to follow this way, I had no gpg or keybase installed on the current PC at that time and just copird the public key from mit.edu, My key was on the phone (OpenKeychain) and there's no way to import it from there. Maybe you should add this importing option, the OpenKeychain app has an option to search for keys in keybase.io
- Then I installed gpg and keybase, exported the key from OpenKeychain and imported it to gpg, then added it to keybase. Works fine.

I have managed to catch two UI bugs:
1. The tray icon doesn't work in unusual multi-screen configuration
2. The CLI tool breaks my console color

Thanks for inviting me!

And is there a poll for adding new services? I'd like to see vk.com and habrahabr.ru there

No files, tests, or entry points are named. Split the report into the installer/PATH request, multi-screen tray behavior, CLI color corruption, and key-import flow; begin by reproducing each Windows issue and locating its owning component. Done would require separately scoped fixes with verification for each behavior.

Written by the indexing model from the issue text.