Setting up keybase for WSL2 and Native Windows

I am user mslinn, mostly using WSL2 on Windows 10. Never got Keybase to work on any platform before. I've got the GPG keys that I generated years ago. I would like keybase to work from WSL2 and native Windows.

The PGP files for native Windows are here at present:

$ cd /mnt/c/Users/Mike\ Slinn/
mslinn@Bear Mike Slinn
$ ls -alF .gnupg/
total 68
drwx------ 1 mslinn mslinn   512 Aug 28 12:07 ./
drwxr-xr-x 1 mslinn mslinn   512 Aug 28 12:16 ../
srwx------ 1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent=
srwx------ 1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.browser=
srwx------ 1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.extra=
srwx------ 1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.ssh=
drwx------ 1 mslinn mslinn   512 Aug 28 12:07 crls.d/
drwx------ 1 mslinn mslinn   512 Jun 25 22:55 private-keys-v1.d/
-rw-rw-r-- 1 mslinn mslinn 54279 Aug 28 12:07 pubring.kbx
-rw-rw-r-- 1 mslinn mslinn  4393 Aug 28 12:07 pubring.kbx~
-rw------- 1 mslinn mslinn  1200 Aug 28 12:07 trustdb.gpg

Native Windows Client

"Oops, something went wrong. Sorry, your account is already established with a PGP public key, but we can't access the corresponding private key."

Where should I put the .pgp file containing the key?

WSL2

The PGP files for WSL2 are here at present:

$ ls -alF .gnupg/
total 84
drwx------  4 mslinn mslinn  4096 Aug 28 12:07 ./
drwxr-xr-x 37 mslinn mslinn  4096 Aug 28 12:28 ../
srwx------  1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent=
srwx------  1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.browser=
srwx------  1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.extra=
srwx------  1 mslinn mslinn     0 Aug 26 06:00 S.gpg-agent.ssh=
drwx------  2 mslinn mslinn  4096 Aug 28 12:07 crls.d/
drwx------  2 mslinn mslinn  4096 Jun 25 22:55 private-keys-v1.d/
-rw-rw-r--  1 mslinn mslinn 54279 Aug 28 12:07 pubring.kbx
-rw-rw-r--  1 mslinn mslinn  4393 Aug 28 12:07 pubring.kbx~
-rw-------  1 mslinn mslinn  1200 Aug 28 12:07 trustdb.gpg

When I try to run keybase this happens:

$ run_keybase
Shutting down keybase service...
Launching keybase service...
Starting the redirector...
Starting KBFS...
Launching Keybase GUI...
run_keybase: Success!
                                                  ▄▄▄▄█▀
╭───────────────────────╮          ▄▄          ▄▄▄█▄▄▀
│                       │         ███▄▄▄▄▄▄▄▄▄▄███▄██
│  Encrypt everything!  │       ▄▄▄████▄▄▄███████████
│                       ├────  ▄▄▄▄▄████▄█████████████
╰───────────────────────╯      ███▄█▄█████████████████▄▄
                                ▀▄███████▄▀ ███████████▄▄
                                  ▄▄▄▄███    ███████████▄▄
                                 ▄████████   ██████████████
                                ▄███▄█████▄▄  ▀▄████████████
                               ███████▄▄██▄█▄▄ █████████████
                              ▄▄█████████████▄▄ ████████████
                           ▄██▄▄████▄▄▄█▄▄█████ ████████████
                                ███▄▄▄▄▄███████▄▄█████████▄▀
                                ▄█████▄▄█████████████▄█████
                                █▄██████████▄▄▄▄▄▄▄███████
                              ▄▄▄▄▄██▄▄█████▄████████████
                            ▀▀▀▀▀▀▀▀▄▄▄▄██▄▀ ▀▀▄▄▄▄▄▄▀▀▀
                                  ▀▀▀▀▀▀▀▀▀
$ keybase login
Your keybase username: mslinn
# Hangs here

my log id: 12b2acbac71809705e69811c

Start with the reported run_keybase and keybase login commands, comparing the native Windows and WSL2 .gnupg locations and the login hang. Use log id 12b2acbac71809705e69811c to investigate the service output. Done means the existing PGP identity can be accessed and login completes in the reported environments.