Client: Keybase causes Windows 10 Insider build 16226+ to freeze

[dsmaher]

I also reported this as Insider Feedback, but Keybase caused my entire machine to almost freeze... to the point that mouse clicks and keypresses (including ctrl-alt-del) did nothing, even though mouse moves and screen redraws seemed to continue to function.

This happened as soon as Keybase started up, which means it happened within 30-60 seconds of logging in.

I had this happen on two machines. On one, I rolled back the Windows build (by restoring a backup), and on the other I uninstalled Keybase (through a very painful process involving windows safe mode because it was the only way I could get into Windows without launching Keybase - the freezing issue prevented disabling keybase during startup). Both solutions worked, but only the rolled-back machine (on build 16193) can still run Keybase.

Both were on version 1.0.23 of Keybase.

[maxtaco]

Thank you for this report and sorry for any inconvenience. Cc @taruti and
@zanderz

On Thu, Jun 29, 2017 at 5:30 PM Dan Maher [e-mail] wrote:

I also reported this as Insider Feedback, but Keybase caused my entire
machine to almost freeze... to the point that mouse clicks and keypresses
(including ctrl-alt-del) did nothing, even though mouse moves and screen
redraws seemed to continue to function.

This happened as soon as Keybase started up, which means it happened
within 30-60 seconds of logging in.

I had this happen on two machines. On one, I rolled back the Windows build
(by restoring a backup), and on the other I uninstalled Keybase (through a
very painful process involving windows safe mode because it was the only
way I could get into Windows without launching Keybase - the freezing issue
prevented disabling keybase during startup). Both solutions worked, but
only the rolled-back machine (on build 16193) can still run Keybase.

Both were on version 1.0.23 of Keybase.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/7591, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_3hYuCcz9XqvxJ-AvFe-dhxv3vyzks5sJBdYgaJpZM4OJ5D-
.

[Diagonactic]

I, too, have had this issue. Same version of keybase, on both 16232 and 16237 insider preview, though, so I can confirm it wasn't fixed one version later. It worked on 16193, as well.

I found a way to eliminate the hang that will prevent you from having to launch into safe mode. You'll be reinstalling keybase if you choose to roll back but at least you won't have to fight through boot menus.

Workaround

1. Power off your machine by holding down the power button for 5 seconds (hard reset, warning -- may have disk corruption afterward so let the system idle for a little bit in hopes that the caches flush).
2. On boot, log into the PC and immediately after hitting the arrow, hold both shift keys down (I think only the right shift is required, but I couldn't remember, so I just did both which worked fine). This prevents items in "Startup" from running which gives you a responsive system for a few more seconds if you have things set to launch.

Step 1 - Preventing the hang so you can remove keybase

You have to do this very quickly, so be ready to perform these steps as soon as the Start button appears.

1. Once the task bar shows up, let go of both shift buttons and hit CTRL+SHIFT+ESCAPE to launch the task manager.
2. Hit the Details button in the lower left-hand corner of the window that pops up (it won't be in details mode if you had previously set it up that way because this version of windows modified the task manager so the settings are reset).
3. Hit the Details tab and click the list.
4. Type "exp", and hit the End Task button.

This will prevent the hang, but you'll have little you can actually do within Windows because Explorer is a rather critical piece of software (you can't even open Settings), but it gives you a moment to prepare for the next set of steps.

Step 2 - Uninstall keybase

1. From within Task Manager, choose File and Run new task
2. Type "control" and hit Enter
3. Click "Uninstall a program"
4. Find keybase and choose the Uninstall button.
5. Find "Dokan Library" and choose the Uninstall button. I'm not strictly sure that this is required, but I have a feeling that the issue is actually with Dokan, rather than Keybase, so I removed it to be safe

Step 3 (optional) - Rollback the installation.

A reboot may be required after removing those libraries, I can't remember.

1. Back to Task Manager, hit File and Run new task. Type explorer. You'll see the task bar show up, again.
2. Launch Settings
3. Type "Recovery" and find the option to go to the previous version of windows.
4. Follow the prompts.

Once you've got the old version back on you can reinstall keybase and it will work. You'll want to dig through settings and either eject yourself from the Insider Preview program or prevent updates from installing (this is limited to 7 days so make sure you do this again at the end of that period).

NOTE: The easiest way would have been to use the USB/CD media and rollback via the troubleshooting menu. I tried that the third time this update was installed and it failed. Worse yet, after successfully rolling back twice, the third time wouldn't allow me to roll back. I cannot say for sure that this was because I used the USB option first or if there was something else going on, but since it happened, I thought I'd mention it.

I've confirmed that this same issue occurs in 16237, as well 16237 that was released, today.

Edited to correct version of Windows I'm stuck on and info related to new Insider release

[Diagonactic]

Small update: This issue will now affect all users in the Windows Insider program. Build 16232 was pushed to the "Slow Channel" a few days ago. The only option for new installs of Windows is to avoid the Insider program until this problem gets resolved by MS or Keybase[0].

[0] Considering that the OS should never allow any application to cause a hard lock like this, the responsibility for the issue is squarely in Microsoft's court IMHO, but I'm willing to bet there's something that can be done on the Keybase side to work around whatever MS have done, here.

[maxtaco]

Thanks so much, can you please take a expedited look, @zanderz and @taruti

[maxtaco]

CC: @strib and @malgorithms too

[zanderz]

I have been trying to get the relevant updates but they aren't showing up. Meanwhile, this is almost certainly due to interaction with the Dokan drivers. I would be very curious what would happen if our installer were run on the command line with nodriver=1, which should omit the Dokan drivers. I will continue trying to get the relevant Windows version to test.

[maxtaco]

One last CC here: @jzila

[taruti]

Yes, this is Dokan related :(

[Diagonactic]

Thanks for the tip on nodriver=1. That got the client back and eliminated the hang, albeit without keybase filesystem, which is a useful feature but not the only one I use so this works until that gets figured out. 👍

[zanderz]

We are continuing to try to secure the relevant Windows build. Meanwhile, there is a chance that a newer Dokan driver will solve this. If some brave volunteer would like to try, their latest release is here.

[Diagonactic]

@zanderz Happy to try that out --

Do I only need to install the driver (i.e. will that restore Keybase Filesystem functionality) or do I need to do something in addition to that (reinstall keybase without that parameter, etc)?

[zanderz]

Just installing + rebooting should give your KBFS mount back - unless the original problem persists.
Thanks a lot for trying it!

[Diagonactic]

@zanderz Well, the bad news is that it didn't even take a reboot. The hang started about 30 seconds after the install completed (kinda expected it was going to happen because the CPU fan went crazy as it did during boot when the issue surfaces).

One small plus side is that installing the Dokan library triggers a System Restore point. In build 16237, I was unable to use the workaround I posted because even killing Explorer doesn't prevent the hang. Booting from the USB media and kicking off a System Restore puts everything back.

I found the related issue on their project as well, so it looks like they're poking at it, too. If there's anything else I can test, let me know (here or via keybase chat mdip)

[zanderz]

Thank you @Diagonactic! Hadn't seen a Dokany issue on this till now. Guess that won't fix it.

[Diagonactic]

It looks like they've released the install media for one of the problematic builds. You have to be signed up for the Insider Preview program which can be done by anyone from within Windows 10 (and probably from their site, directly; not sure since I'm already signed up).

You can grab the ISO from the Windows Insider Preview Advanced. The drop-down at the bottom will generate a link that works for 24-hours. 16232 is one of the affected builds. The other, 16193, is not (that was the last build I had that worked with keybase/Dokan).

If you have problems getting it, let me know which one you need and I'll figure out a way to get it to you privately (since publicly would be a ToS violation and privately probably is, as well, but I'm finding it hard to not justify since it's available to the public after a few clicks on a public web page).

[Diagonactic]

Since folks might not be checking the related issues - @zanderz got the logs together using the mirror service for Dokany and they're looking into it now. It sounds like the log files were unexpectedly limited (not terribly surprising given how this bug surfaces and how well it obliterates a working system; in all likelihood, relevant logging messages are not being written once the issues surfaces).

Sounds like the ball is rolling, though, now that all of the necessary information is handy. Never realized how much I miss keybase filesystem; glad my other PC wasn't in the insider program :)

[zanderz]

Don't forget you can still access KBFS without the driver by using the keybase fs commands in Keybase Shell

[phillijw]

Same issue here on 16232. Let me know if there's anything I can do to help.

[dixonge]

In the meantime, can we add a warning note to anywhere someone might download this software from? It certainly would have saved me a lot of hassle this morning...

[Rondom]

Issue has been fixed in Dokany GIT: https://github.com/dokan-dev/dokany/issues/554#issuecomment-317973085
You can help with testing, if you want.

[Diagonactic]

It works! I'm on the latest insider preview and with the updated Keybase-signed Dokan library 1.0.4.84, I was able to access Keybase File System.

Installing Keybase with Keybase Filesystem on Insider Preview Editions Affected by Freeze Bug

For those who have encountered this issue, until an official, signed release is made by the Dokan project, you can use the following procedure:

• Download the latest keybase installer from here. Choose Save not Run.
• Open a command prompt. (Hit Win+R and type "cmd.exe")
• In the window, do the following:

cd %USERPROFILE%\Downloads
keybase_setup_386.exe nodriver=1

• Download the Keybase signed Dokan Driver Build
• Double-click the file or otherwise open it and choose "Extract All"
• In the folder that appears, navigate to dokan_wix\bin\x64\Release
• Double-click Dokan_x64.msi and install with defaults

If you're not on x64 (almost everyone is/should be), use the x86 doler and Dokan_x86.msi.

Thanks for all of the work, fellas!

[taruti]

We are soon shipping a Dokan driver with the upstream fix with Keybase installer. @zanderz has the details. Thanks to everyone for working on this.