Client: Keybase Windows GUI does not start after update 2019-10-15

[openeyes-cz]

[write something useful and descriptive here]
After today's update I'm stuck with "Starting up Keybase". Hard reset didn't help, and when I start the latest installer from your web, it says "The specified account already exists."

my log id: 7a412dec7b9145637cf4d41c

[lestaticon]

I noticed that my antivirus program (ESET) quarantined appdatalocalkeybasekeybaserq.exe on the 15th. It was marked in ESET as just a "Suspicious Object."
I removed it from quarantine and all is well again. From searching previous issues, it may be similar to Issue #6897. Check your antivirus in case? https://www.virustotal.com/gui/file/7535181bcf92ebba7c2342e2269b5aaca0727f0f01f3383f3adc0884980a9202/detection

[openeyes-cz]

I noticed that my antivirus program (ESET) quarantined appdatalocalkeybasekeybaserq.exe on the 15th. It was marked in ESET as just a "Suspicious Object."
I removed it from quarantine and all is well again. From searching previous issues, it may be similar to Issue #6897. Check your antivirus in case? https://www.virustotal.com/gui/file/7535181bcf92ebba7c2342e2269b5aaca0727f0f01f3383f3adc0884980a9202/detection

Thanks man! That was it.

I don't have my user password for the ESET so cannot remove it from the quarantine.

Question is, why does it trigger the trojan alert...

[lestaticon]

I think it is only the nature of the program/exe, which is to silently launch the main client app I believe. The heuristic detection processes of any AV app might flag that behavior if they do not already have the current version of the exe on their database and flagged as okay. That's my understanding anyway.

[cadayton]

On one of the 3 installs on Windows 10, I'm having the same issue with the GUI not launching on one system after the update was applied and the system was shut down and restarted. The GUI is working on the other 2 systems and these systems have not been updated.

Keybase CLI 4.6.1-20191014125620+3592f81d6f
Checking for update, current version is 4.6.0-20191010021431+134c2d892b

Associated services are running
kdfsdokan.exe
keybase utility
keybase utility

Thoughts?

[maxtaco]

@cadayton do you use an antivirus product, and if so, which one?

[cadayton]

@maxtaco Windows Defender/Security, but no threats tagged.

[maxtaco]

@cadayton have you tried restarting the machine? it could be the old process got stuck in an unkillable state, preventing the new one from starting up

[cadayton]

Hi,
Its a VM guest that the keybase client is having issues on. The VM has been bounced multiple times.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 21, 2019 6:16 AM, Maxwell Krohn [e-mail] wrote:

@cadayton have you tried restarting the machine? it could be the old process got stuck in an unkillable state, preventing the new one from starting up

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.