USB: It is currently not possible to connect any USB device to a macOS ARM VM yet. (Resolved)

Discussion in 'Windows Guest OS Discussion' started by GaryM21, Aug 23, 2022.

  1. GaryM21

    GaryM21 Bit Poster

    Messages:
    6
    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?
     
  2. GaryM21

    GaryM21 Bit Poster

    Messages:
    6
    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?
     
  3. GaryM21

    GaryM21 Bit Poster

    Messages:
    6
    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?
     
  4. GaryM21

    GaryM21 Bit Poster

    Messages:
    6
    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...
     
    KurtW2 likes this.
  5. KurtW2

    KurtW2 Bit Poster

    Messages:
    6
    Works as you stated on the M2 chip as well. Read the Installation guide carefully.
     

Share This Page