Firmware update on Windows 10 doens't work

[karmalvel]

Hi!

I got the email saying the new firmware is available and started the process to install rust and all that was informed on "https://solokeys.com/pages/firmware-update-for-windows". Now the problem is that when I try to do anything with the key, be it asking version or trying to update, I get the same error: "Error: Empty list of Solo 2". I have three usb-c -version keys and one usb-a and all have the same problem. I've tried to restart everything, reinstall everything and even tried with three computers, but all give the same error. Any and all help would be appreciated!

[needs-coffee]

@karmalvel have you tried opening a cmd prompt as administrator and seeing if the solos are listed? Are you using a USB extension/hub? do the keys get recognised/usable by the computer when not updating? (i.e. with websites or in windows device manager)

EDIT
also you could try with the exe on the releases page and not using rust and see if this is the issue - https://github.com/solokeys/solo2-cli/releases/tag/v0.2.0

[ursa2]

I ordered a Solo 1 USB-A Red/Black. The package only says Solo USB-A. Windows is calling it 3.1.2. I'm using a USB 2 port.

I'm going to try the Solo on another computer tomorrow and see if that works.

[needs-coffee]

I ordered a Solo 1 USB-A Red/Black.

then the solo2-cli wont work - you need the https://github.com/solokeys/solo1-cli to update this. This is the repo for the solo2 which is different. The latest solo1 firmware is 4.1.5

[JohnLGalt]

I just received V2 keys, LEs at that, a couple of days ago. I went through the process of setting everything up, got the VS part installed, Rust installed, and cargo install solo2 installed package 'solo2 v0.2.1', verified by running cargo install solo2 again and it stating it was already installed and thus Ignored it.

One key is the regular Type A key, the other is the Type-C Hacker. I've been interested in mainly setting up the Type A key for now to add it to my other keys for my accounts, but I've tried, just for S&G, both keys, connected to my system, They appear just fine in Device manager, as you listed above, in all three spots exactly as you state. However, running solo2 app admin version in a standard cmd window (or cmd instance in Terminal ,tried both) has it take a long time before returning Error: Empty list of Solo 2. I just tried in an admin-elevated cmd window and the command has not done anything thus far. It's been literally 5 minutes waiting for a response.

One thing to note - when I first set everything up, and then inserted the Type A key for the first time in a USB 3.0 slot, Windows wanted to reboot before it could use the key. I'm going to try to remove all of those instances of the key from the system, reboot, and then insert the key and see if it reinstalls the drivers, and see if that fixes it.

Windows 11 22H2 (build 22621.674)
Windows Defender - Real-Time Protection and Tamper protection enabled, Controlled folder access disabled, Core Isolation (Memory Integrity) enabled

Anything else that you may think I should try to get this working?

EDIT: The elevated cmd window just returned Error: Empty list of Solo 2 - as I expected it would. Gonna kill drivers and try again, see if it makes a difference.

[JohnLGalt]

After doing all of the above, same results, except for one thing - it is not taking as long.

I thought it might have been because my Titan Security keys were inserted, confusing the system, so I unplugged that, and then deleted all the drivers as mentioned above. With the Hacker Type-C the light stayed blue, but same Error. With the regular Type A, light was green, but same error also. Checking DM, I see all the same entries as before for all the devices.

Going to try one last thing, that is disconnecting every external USB hub that I have (been using the connections on the case, not the hubs), and try using the back I/O panel connectors to see if that makes any sore of difference, even though I know the case connectors are wired directly off on motherboard USB connectors.

Also to note:

On my rig, the entry under Smart card readers is Microsoft Usbccid Smartcard Reader (WUDF) and under Smart cards as Unknown Smart Card.

[ursa2]

Sorry have been away. I got the Solo to work on two other computers with webauthn.io. So, the problem with it not working is only on the first computer I tried. Since it works, the problem if with only that one computer and I will try to figure out why.

Thank you for the help.