login OK but never logged in (windows client)

after doing keybase --home $HOME login today and verifying my device from my osx machine I got:

note: the --home ~ is because I'm running keybase from msys2 and I'd like my $HOME to be used instead of $HOMEPATH

OK Success! You provisioned your device <device_name>.

You are logged in as ksophocleous
  - type `keybase help` for more info.

but I'm not logged in as keybase --home $HOME status is indicating

$ keybase --home ~ status
Username:      ksophocleous
Logged in:     no
Session:       no session
    is valid:  no
    keys:      locked
    lksec:     not loaded

KBFS:
    status:    not running
    version:
    log:       C:\msys64\home\kostas\Keybase\keybase.kbfs.log

Service:
    status:    running
    version:   1.0.15
    log:       C:\msys64\home\kostas\Keybase\keybase.service.log

Platform Information:
    OS:        windows
    Runtime:   go1.6
    Arch:      386

Client:
    version:   1.0.15

Desktop app:
    status:    not running
    version:
    log:       C:\msys64\home\kostas\Keybase\Keybase.app.log

Config path:   C:\msys64\home\kostas\Keybase\config.json
Default user:  ksophocleous
Other users:

command-line client:
    C:\tools\keybase\keybase.exe --home C:/msys64/home/kostas status [pid: 6940, version: 1.0.15]

it appears that the device key inside config.json is not set correctly.

{
    "current_user": "ksophocleous",
    "users": {
        "ksophocleous": {
            "device": null,
            "id": "...",
            "name": "..",
            "salt": "..."
        }
    }
}

If I set the device to the id of the newly provisioned device and then do keybase --home $HOME status it shows that I'm logged (and everything else works as well).

But I have to do it manually (via a text editor).

note: I also restarted the service after manually changing the device value, but I don't know if this is required.

my log id: e32aa11b9a613b9a4d33ec1c

Start with the Windows/MSYS2 login path invoked by keybase --home $HOME login and inspect how provisioning updates config.json, especially the user's device field. Reproduce the login, then run keybase --home $HOME status; done means the device is recorded automatically and status reports the user as logged in without manual editing.