Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update is not working with Chrome and Windows 10 19H1 (18358.1) #5

Open
qmatteoq opened this issue Mar 17, 2019 · 6 comments
Open

Update is not working with Chrome and Windows 10 19H1 (18358.1) #5

qmatteoq opened this issue Mar 17, 2019 · 6 comments

Comments

@qmatteoq
Copy link

I'm trying to update my Solo Key with my machine, which is running the latest Windows Insider preview (build 18358.1) and Google Chrome 72.0.3626.121.
Chrome is able to detect the key, but when I enable bootloader mode it keeps complaining that the device isn't in bootloader mode at all.
Here are the steps I've taken:

  1. I've plugged the key
  2. I've pressed the "Check for updates" button on the website
  3. I've inserted my PIN, followed by the press of the Solo Key button
  4. The website finds my Solo Key and prompts me to perform the update.
  5. I unplug the Solo Key, then I plug it back by keeping pressed the button
  6. After a few seconds the led starts to quickly pulse
  7. I press the Update Solo Secure button on the website.
  8. I get the error: DEVICE IS NOT IN BOOTLOADER MODE. Please unplug your key, and plug in while keeping pressed until the LED blinks. Then try to flash again
@dylmye
Copy link

dylmye commented Mar 17, 2019

I get the same issue with Chrome Mobile 73.0.3683.75 on Android 8.0.0

@conorpp
Copy link
Member

conorpp commented Mar 17, 2019

Either of you happen to have a built in authenticator on your PC? Does FIDO seem to work without anything plugged in? Maybe there is a conflict.

@qmatteoq
Copy link
Author

Hello, I've just reported the issue to the Windows team through Feedback Hub. I did some additional tests and it seems the Solo key isn't working at all on 19H1. When I press the button on the key during the login process, it isn't recognized at all. It was working fine, isntead, on 1809. I'll keep you posted if I get any update.

@nickray
Copy link
Member

nickray commented Mar 21, 2019

@qmatteoq thanks! Is there a public link to this issue report in Feedback Hub?

@szszszsz
Copy link

@qmatteoq Hi! Any updates regarding this one?

@dylmye
Copy link

dylmye commented Oct 22, 2019

@conorpp sorry, never saw your response. No, this isn't the case unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants