I am trying to connect my Windows 10 computer to my Lego WeDo 2.0 hub using Bluetooth, and it says that there is a “Driver Error”. Does anybody know why this is happening and/or how to fix it?

I have tried disconnecting and reconnecting, as well as updating my computer. It pairs to the device, but does not fully connect.

Thank you.

Hello! I have had this problem with my Picoboard in the past, and I need to know more about your problem.
Please use this format:

Have you installed the Scratch Device Plugin Helper: (Yes/No)
Have you tried going online and searching for Lego WeDo 2.0 drivers: (Yes/No)
Has this product ever worked for you: (Yes/No)

I am also having trouble getting it to connect. I've followed the instructions and it connects and pairs through the bluetooth settings. When I open scratch device manager, it won't connect to the wedo.
This computer is a Windows 10, brand new, and I'm running all of the most current versions of scratch and the device manager. It connects on my mac, but I don't want kids to use my mac in the makerspace.
I read on another forum that it has something to do with the newest Windows update, but there was no solution given.
Thanks!

s_team337 wrote:

I am trying to connect my Windows 10 computer to my Lego WeDo 2.0 hub using Bluetooth, and it says that there is a “Driver Error”. Does anybody know why this is happening and/or how to fix it?

I have tried disconnecting and reconnecting, as well as updating my computer. It pairs to the device, but does not fully connect.

Thank you.

kkcmmakershop wrote:

I am also having trouble getting it to connect. I've followed the instructions and it connects and pairs through the bluetooth settings. When I open scratch device manager, it won't connect to the wedo.
This computer is a Windows 10, brand new, and I'm running all of the most current versions of scratch and the device manager. It connects on my mac, but I don't want kids to use my mac in the makerspace.
I read on another forum that it has something to do with the newest Windows update, but there was no solution given.
Thanks!

It is probably a Windows 10 error