MTP driver crash on windows with usb 3.2

[CaTaTo23]

Hi, I want to report a problem with usb 3.2 driver crash on windows, I tried onboard usb as well as pci e usb card, doesnt matter usb a or c, I only manage get it randomly work with type C cable 1 time, but it stoped work after update as well. Usb 2.0 cables work 100% fine. MTP Driver return code 10 (Insufficient system resources to complete the API call) or something like that (sorry I not use english version windows so that might be not exact description in device manager). My android phone works fine on any cables I tested. My deck bios version is 110. My computer is: rysen 5900x, b550 chipset, win11.

Anyway thanks in advance guys for doing valves work

[dafta]

This might be an issue with the driver installed on Windows. I haven't personally tested on Windows 11, might also be an issue.

You could try uninstalling the driver, plugging in the Deck again, and enabling DeckMTP, to let Windows reinstall the driver. If that doesn't work, we can see about other troubleshooting steps.

[CaTaTo23]

Nope, nothing change if I delete driver or updating it to similar, in the driver info driver date development is 2006 year, so it might be not only on win11

[dafta]

Okay, so I finally got a Windows machine to test it on, and at first it gave the same error. But, after shutting down the PC (shutting down, not restarting) for at least 10 seconds, and the Deck just for good measure, it worked on the first try. I'll have to investigate this a bit further, but for now, could you try doing the same?

[CaTaTo23]

Nope, after fully shutting down pc and reboot steamdeck mtp driver still crash (c to c but it souldn't matter), but it worked with front usb a to c, also I would like to report other issue, may be I'm just dum at permission managment in linux but my games folder on main drive that use heroic just not show up in mtp, after creating other folder it shows up normally, but as soon as I add game on that folder in heroic(and wine prefixes too) it disappears from mtp, I tried to add all permission for my user but nothing changed, it also happening with other folders, but I have no explanation of them dissapearing, here is screenshot of ssh and mtp in same folder

[CaTaTo23]

Front usb was 2.0 btw, so it didn't change anything

[TuNdRa-Plains]

This seems partially related to Windows in some form - Windows 11 exhibits this behaviour on X570 USB 3.x Controllers.
However the USB 2.0 headers will connect & Run MTP Mode fine. I've dug through most of the Windows 11 suggested fixes short of a complete OS Reinstall and nothing resolves it on USB3. (This is across: Direct headers on the board, rear-panel USB, 2 different USB3 Hubs, 2 different cables)

Just for dev ref; this is on SteamOS 3.5.5, Bios F7A0119.

[Honzackcz]

This seems partially related to Windows in some form - Windows 11 exhibits this behaviour on X570 USB 3.x Controllers. However the USB 2.0 headers will connect & Run MTP Mode fine. I've dug through most of the Windows 11 suggested fixes short of a complete OS Reinstall and nothing resolves it on USB3. (This is across: Direct headers on the board, rear-panel USB, 2 different USB3 Hubs, 2 different cables)

Just for dev ref; this is on SteamOS 3.5.5, Bios F7A0119.

I can add to this with Windows 11 and X670E, any faster USB connection then 2.0 will crash while transferring a file, it can delete files and create empty files tho. (SteamOS 3.5.5, BIOS F7A0119)

It is the same thing with this issue:
#2 (comment)

[dafta]

Potentially fixed by 1.0.3, needs testing.

[Honzackcz]

DeckMTP 1.0.3 still doesn't work with higher USB version then 2.0 (SteamOS 3.5.19, BIOS F7A0120)

The USB-C to UBS-C issue ( #2 ) is most likely the same issue with this one because only USB-C to USB-C cables I have are 3.0+

[dafta]

Did you try it again just now? Because the 1.0.3 version on the testing store was just updated an hour ago. Did you update it?

[Honzackcz]

Yep, I download the 1.0.3-f0917db from the testing store.

[dafta]

Okay, thanks for the info. I will try to replicate this and see if I can't find the issue.

By the way, I noticed you are using the F7A0120 BIOS version, which still had some issues with DRD. Would you be willing to test with version F7A0121 or newer?