Error logging into app ("can't access PGP private key") on Windows

I'm having issues trying to log into the Keybase app through the GUI and performing actions after upgrading from the command line app. I'm using Win10 with Gpg4win/Kleopatra, and the keybase server does not have my PGP private key.

I enter my username and password, and I immediately get the screen with the title There was an error provisioning with the description stating that keybase can't access the private key. I'm able to use naked gpg to encrypt/sign things normally, so I don't think the problem is there. I'm unable to login through the app. After dismissing the dialog and trying to log in again, I get bumped out to the keybase "home" screen, with the white text on blue toast This device has been revoked, please log in again. at the top of the app. If I try logging in again, I start over at the top of the paragraph!

When I try to use keybase on the command line, nearly every "authorized command" (such as keybase follow [username]) is followed with the error text - ERROR no secret key available. gpg -K returns my private key as found, and I've tried logging in/out of keybase, though I get the PGP private key warning, followed by the no secret key available orange message.

I've also tried to prove my key to keybase using keybase pgp select --only-import, but it doesn't change any behavior.

I'm a little stumped, so I'm asking you all for help :)

my log id: b23652b39bdf569374b5c11c

Start with the Keybase log identified by b23652b39bdf569374b5c11c and reproduce the Windows login failure using Gpg4win/Kleopatra. Compare the GUI provisioning error with the command-line no secret key available result and the keybase pgp select --only-import attempt; the issue is done when login and authorized commands work with the available private key.