Provisioning Failure on Windows 10 with existing Keybase Account

[write something useful and descriptive here]

my log id: 63006d025080dc7d8ff8701c

It appears that the current release of Keybase does install properly. It also appears that the attempt to login succeeds (it recognizes the name and recovers my profile picture). I am also logged in at the web interface, so I think that did work. The previous successful install was 0.8.25 on node.js, which now produces a config file warning.

I confirmed that cmd started at the location where the newer Keybase is installed does find gpg. And the send log operation works there.

But on startup of Keybase, which apparently happens automatically on Windows startup, the login fails with a provisioning error.

Hints: 1. I have not changed the group policy that prevents execution under AppData, but the current install seems to overcome that, at least partially. 2. AppData is on an SSD with compression (and I would love to move AppData to the D: HDD but have found no way to do that).

[PS: It is unfortunate that the Help panel does not provide an About with Keybase version identification]

No source files, tests, or entry points are named. Start with log id 63006d025080dc7d8ff8701c and the provisioning error on Windows startup, then compare the current release with the previously successful 0.8.25 node.js installation. Done means reproducing the failure or documenting its cause and a verified resolution.