[Bug] Failed to reset USB device: NetworkError (Windows)

[BertLindeman]

Describe the bug
On windows: try to connect via USB to a primehub does not complete the connect.

To reproduce
Steps to reproduce the behavior:

1. Open labs.pybricks.com
2. connect the primehub via USB cable.
3. click the USB connect button
4. select the hub and click "connect"
5. expect the USB-button to change to USB-connected and the "Run" and "REPL" buttons to enable.

Expected behavior
See the USB connect change to "connected"
and the "Run" and "REPL" buttons to enable.

Screenshots
There is a saying that a picture is worth a 1000 words. Screenshots really help to identify and solve problems.

Just before click on "Connect"

just after click on "Connect":

Extra info:
labs version (as app on win11 25H2)
"v3.6.1 (Pybricks Beta v2.8.0-beta.2)"

Robot Inventor firmware:
('primehub', '4.0.0a0', 'ci-build-4325-v3.6.1-548-g76893f68 on 2025-10-30')

Also mentionned in PR 405

[EDIT]
The same with the EV3 from the same build.
I do not know how to copy the text from the dev tools, so a picture:

[EDIT 2]
Used:

• brave
• chrome
• edge
• firefox
  All the same result

[laurensvalk]

Can confirm. Here we can also see that we do get disconnection events.

[dlech]

It turns out that WINUSB has much more limited features compared to other OSes. So even some functions in the WebUSB implementation, like reset() are not available on Windows.

I started looking into this a while back but I didn't come up with a solution yet. The reason we were using the reset in the first place is because endpoints have an even/odd thing where every other packet is marked as even (and the rest odd) to catch missed or duplicate packets. If the host and the peripheral get out of sync, it causes an error. The reset is one way to sync these back up.

Instead, I think we will have to do something with stalls and clearing the stalls on the endpoint to sync them back up.

pybricksdev has similar issues on Windows for the same reason.

[BertLindeman]

pybricksdev has similar issues on Windows for the same reason.

I did not see errors on win 11(25H2) using pybricksdev run usb myprog.py to an EV3,
but on flash to the same EV3:

    raise RuntimeError(
RuntimeError: message sequence number mismatch: 256 != 0 

[dlech]

RuntimeError: message sequence number mismatch: 256 != 0

I think that is #2375.