Separate names with a comma.
13.3.1 still exhibits this issue with Parallels 18.2.0.
What's more, turning off the `Enable USB 3.1` option in Parallels seems to make the dropped frames/latency issue go away. It seems USB 3.1...
I *think* that since applying the 13.3 update, I'm seeing USB throughput issues, particularly with an USB2 device from Vector (VN1630). I keep...
Hello? Can we get an update on Parallels on this issue?
@DebasmitaM@Parallels can you please share an update with everyone here? These are debilitating issues for those of us that rely on USB. With...
https://download.parallels.com/desk...315.92570515.1634809561-1903624072.1632665082
Not all of us can file a support ticket number, some of us are using this in enterprise settings where Parallels asks you to contact a system...
I've already gone through this and filed a technical report here: 385830716. I really don't have the time to upgrade to 17.1.1 and check this...
I'm also having issues with TI's XDS110 debuggers in Parallels 17.1.1 still. Downgrading to 17.0.1 resolves those issues and makes USB reliable...
Report 385830716 has been sent. Please don't ask me to do this again as it requires several restarts and time to roll forward then roll back....
I also continue to find USB highly unreliable in 17.1.1. Devices may look like they're connected, but they aren't at all reliable like they used...
I'm betting you hit the "upgrade" button when running the installer. The installer will check for updates before running and present you with an...
FWIW, this broke quite a bit of USB functionality for Windows VMs too:...
I'm also having USB issues with CAN-related devices not working properly anymore when they were with Parallels 16.x.
It's not specific to windows 10 either. It's any VM I've tried (Ubuntu included) that has the "Use All Displays in Full Screen" option on.
I'm having the same issue. What is going on here? How did they break something so fundamental?
Same thing happens to me in Windows 10. I can't rearrange the displays or have their arrangement follow that of OS X.
Another update and still nothing...
I've already reported the problem months ago. I was even told by parallels support that it was reproduced, again months ago.
Another 2 months for another release AND IT'S STILL NOT FIXED. What is going on here? PD9 did not have this bug.