So, I recently had to replace my Intel MacBook Pro with a M1-Pro based 14" MacBook. This obviously eliminated Boot Camp as an option, so I went back to using Parallels (18) for my WinDoze needs. I tried installing CHIRP so I could programs some radios I have and nothing worked as expected. I then found the following in a FAQ regarding Apple silicon and Parallels 18... "USB devices: It is currently not possible to connect any USB device to a macOS ARM VM yet." This is a show stopper for me. What's there point of using Parallels if it can't connect to any serial devices? When will this critical feature the restored to Parallels?
I resolved my issue. First, I bought a genuine FTDI based cable. Second, I downloaded the FTDI ARM based drivers from FTDI that are listed as being compatible with the M1, M1 Pro, etc Apple chip set. Then I manually installed the drivers for the cable. BUT, and this is the key, it failed to load. The issue is that downloads in the Windows/Parallel contain DO NOT go to the C: drive. You need to manually move (or copy) the downloaded drivers the the C: drive partition or WinDoze bitches about the drivers and fails. Simply moving the driver package to C: and reinstalling, the rebooting (of course) resolved the issue and my USB device is now working...
Possible correction...this FAQ of known limitations apparently apples to running a MacOS VM on a Apple silicon based Mac. But, I am not able to get any serial device to show up when running Windows 11 on my M1 Pro based MacBook. Has anyone been able to get USB devices connected and functional on Parallels 18 running Windows 11 on any M1, M1 Pro, or M2 based Mac?
It's my understanding that Apple provides, in the latest OS (Monterey), drivers for CH34x and FTDI based usb cables. And I assume Windows 11 does well. Does Parallels 18 map these drivers correctly?
I resolved my issue. First, I bought a genuine FTDI based cable. Second, I downloaded the FTDI ARM based drivers from FTDI that are listed as being compatible with the M1, M1 Pro, etc Apple chip set. Then I manually installed the drivers for the cable. BUT, and this is the key, it failed to load. The issue is that downloads in the Windows/Parallel contain DO NOT go to the C: drive. You need to manually move (or copy) the downloaded drivers the the C: drive partition or WinDoze bitches about the drivers and fails. Simply moving the driver package to C: and reinstalling, the rebooting (of course) resolved the issue and my USB device is now working...
Hey I am having a lot of issues trying to connect my USB devices to a M2 ARM based Apple processors. I am using the latest Apple iOS and the Latest Parallels version too. I am also using apple original adaptor from USB-C to USB. Can you please help me? Thanks
Hello! In order to proceed with further investigation, kindly provide us with the below information: 1. Reproduce the issue. 2. Collect a technical report (right-click Parallels icon in Dock > Help > Send technical data > check "Attach screenshots..." > press Send Report) and send the report's 9-digit ID in a reply. Thank you!
I have never been able to connect my USB device to my virtual machine. I have a Komplete keyboard (piano) and also a thunderbolt audio interface. Both devices are not recognized, and when I want to install a driver for some hardware it tells me that it is not possible to do so. It is a headache.
USB passthrough is possible for Windows and Linux VMs on Apple silicon. USB passthrough is not possible for macOS VMs on Apple silicon because macOS VMs use the Apple virtualization framework which does not currently have this feature.
Wouldn't there be any other solution to be able to install drivers or connect these types of devices. On another architecture other than ARM? (Honestly, I barely know about this topic, I don't know how it works or what options there are... but I would like to know if there was another option to connect my devices in Windows, since for this sole reason I acquired Parallels: to edit audio on a Windows machine within my Mac)