Cant connect my USB device (telescope) after PD 17.1.0 Update

I am also having USB issues with 17.1. All my PIN pad devices stopped connecting. 17.01 was working fine. How do I get back to 17.01?
I'm running MacOS 11.6 and Windows 10.
 
KavehV said:
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 option to get 17.1 instead. You have to simply close that window and select the option to install the "current" version.

Downgrading to 17.0.1 fixed the issue for me as well.
Click to expand...
ok, did so.
But that didn't solve my situation. CZUR ET18 pro does not go into either Windows 10 or macOS Monterey RC2 and maybe that's a problem with this macOS update.
 
Jon Donshik said:
I am also having USB issues with 17.1. Running W11. My Phillips SpeechMike, which is a speech recognition microphone that I use for Dragon Naturally Speaking, will not work. It is recognized by the Mac, used to work in Parallels immediately prior to upgrade to 17.1 (from 17.0.1), but now wont connect. In USB devices in Parallels menu, the hardware shows up, and is checked (to be used with VM, rather than host Mac). However, the Phillips SpeechMike software (Phillips Device Control Center) does not see the microphone and therefore I cannot dictate with the microphone. Interestingly, Dragon does recognize the Mac's built-in microphone and I CAN dictate that way. However, the Phillips microphone is much more accurate.
Click to expand...
Exactly the same issue for me - just downgrading now to see if it fixes this - have wasted hours trying to fix this myself!
 
Same for me. Running up to date Windows 10, and with the last Parallels update (17.1) a development board with a multi-endpoint USB interface (CDC, HID, and MSD) stopped working in the VM - but still worked in the Mac. Downgraded to 17.0.1, and all is well. It looks as though something was causing the VM to drop DTR to the CDC interface - there's a 1Hz heartbeat that the development board generates toward the serial port, and an LED on the board that blinks with the serial traffic. That LED stops blinking as soon as I fire up TeraTerm and try to open the COM port (yes, the COM port appears in the Device Manager list, and it says it's working properly, but no traffic in or out.
 
salvomic said:
ok, did so.
But that didn't solve my situation. CZUR ET18 pro does not go into either Windows 10 or macOS Monterey RC2 and maybe that's a problem with this macOS update.
Click to expand...
After the official release of Monterey I tried with the CZUR driver (scanner) on another computer where it worked before (with Big Sur): it doesn't even go there, so I think my problem is not (only) with Parallels but precisely with Monterey 12.0.1, That's why downgrading to 17.0.1 doesn't change anything here.
 
Thank you folks for the info here. I also had my USB device stop working with 17.1, and rolling back to 17.0.1 fixed it.
 
My USB device wasn't working after the recent upgrade, downgraded to 17.01 as
GlennS5 said:
I started having USB issues with 17.1.0 as well, but worked fine with 17.0.1. If you are willing to give it a try maybe 17.0.1 works fine and only 17.1.0 that is having USB issues for you as well.
Click to expand...
My USB device wasn't working after a recent upgrade, downgraded to 17.0.1 after reading this and it has solved the issue. Thank you!
 
AndrewP28 said:
My USB device wasn't working after the recent upgrade, downgraded to 17.01 as

My USB device wasn't working after a recent upgrade, downgraded to 17.0.1 after reading this and it has solved the issue. Thank you!
Click to expand...
Hello, we are glad to hear your issue has been resolved. Thanks, Parallels Team.
 
DebasmitaM@Parallels said:
Hello, we are glad to hear your issue has been resolved. Thanks, Parallels Team.
Click to expand...
@DebasmitaM@Parallels : Exactly how does going back to an earlier version 'resolve' the problem? Or were you just being sarcastic?
17.1 clearly has problems communicating with USB devices that aren't shared by the host and they've paid for the upgrade to 17.1. They shouldn't have had to revert to an earlier version of Parallels. How irritating.
 
Mark Fine said:
@DebasmitaM@Parallels : Exactly how does going back to an earlier version 'resolve' the problem? Or were you just being sarcastic?
17.1 clearly has problems communicating with USB devices that aren't shared by the host and they've paid for the upgrade to 17.1. They shouldn't have had to revert to an earlier version of Parallels. How irritating.
Click to expand...
I assume they used the wrong word since this is a workaround until solved and not a solution. I have a similar problem after upgrading to 17.1 and waiting for a new version/build where this problem is solved. Parallels is usually pretty slow to release a fix in cases like this and hopefully they will speed things up a bit and fix the USB issues introduced in 17.1.
 
GlennS5 said:
I assume they used the wrong word since this is a workaround until solved and not a solution.
Click to expand...
I'll go one further and assume that there are several new people responding to these that don't quite have a grasp of the English language and don't understand what they read... and grinding through these at a rapid pace. As a result, some people are getting responses like this and then getting their ticket closed, when in fact nothing's been resolved. As a former employer, there's a word (and a quick solution) for this, but I'll be nice.
 
Mark Fine said:
I'll go one further and assume that there are several new people responding to these that don't quite have a grasp of the English language and don't understand what they read... and grinding through these at a rapid pace. As a result, some people are getting responses like this and then getting their ticket closed, when in fact nothing's been resolved. As a former employer, there's a word (and a quick solution) for this, but I'll be nice.
Click to expand...
Well you might be right :) I opened a ticket and had to tell them many times that Yubikey is not a USB keyboard since they kept taking about my "USB Keyboard issue". I also have to say that 1st line support should get better training so they can sort out cases which require a bit more than sending some links. For example I opened a ticket because my Yubikey do no longer work after upgrading to 17.1. When they send me several articles that describe USB keyboard issues it's obvious they have no idea what I'm talking about. When I told them to dig a bit deeper instead of sending me articles that is very basic they realised that more competent support is required and sent the ticket to the next level of support. The Parallels 1st line support is not good at all.
 
Having all sorts of USB problems with 17.1 as well - primarily with my USB Audio Headset that I'm passing directly to the VM via USB. Lost all audio.

Downgraded to 17.0.1 and things seem to be working again - running MacOS 12.0.1.
 
Thanks Guys! This place it the greatest. Was pulling my hair out on this one, and although I just downgraded (thanks for the link) I have not tried it yet, but at minimal; nice to see it was not just ME!
 
Downgrading worked for me as well. A "normal" FAT32 formatted USB stick did work, but my Android Smartphone MTP mount didn't work anymore. Due to this bug I dug out two native solutions on MacOS other than buggy old Android File Transfer (the smartest being mounting the phone via SSHFS). Besides, I was close to cancelling my Parallels subscription which happens to renew in November and reverting back to VirtualBox.
Here's the knowledge base article mentioning that "some" users are experiencing USB issues with 17.1.0: KB128608
 
You must log in or register to reply here.
Back
Top