-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
I get the same issue with |
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. |
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. |
@qmatteoq thanks! Is there a public link to this issue report in Feedback Hub? |
@qmatteoq Hi! Any updates regarding this one? |
@conorpp sorry, never saw your response. No, this isn't the case unfortunately. |
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:
The text was updated successfully, but these errors were encountered: