I found these tips for your driver install at:ĥ. Installation was a bit tricky even after disabling driver signing in Windows 11. I can confirm that the beta driver works under Windows 11 Home ARM64 running under Parallels 17.1.0 on 2021 MacBook Pro 14' Monterey 12.0.1 using a USB C to Serial Adapter with FTDI chip. Here is an excerpt from the email I sent them yesterday: FTDI is working on another version that should meet Windows 11 driver requirements and eliminate this burden. At the moment it doesnt meet windows 11 driver signing requirements so to test or run it you have to temporarily disable that feature. I contacted FTDI support and offered to test their beta ARM64 driver. (Heck, even FTDI hasn't done this, although I haven't tried every single one of their Raspberry Pi drivers yet.) Mostly my bump post was to ask whether anyone had successfully recompiled the FTDI Virtual Comm Port Driver under Windows 10 for ARM yet. (The procedure in the KB article does work on the Intel side, and I am able to get my application working there, so 'not a biggie.') So, I'm pretty sure I'm back to the point where I need a device driver that Windows for ARM does not currently have. There is a driver under Ports (COM&LPT) called 'oem7.inf (ftdiport.inf)' Start Device Manager to look for the port.I add the serial port to the configuration and select this device as outlined in the article (Previously I had selected it through the dynamic USB device selection).usbserial-AK06HJ9O appear in the Mac's /dev/directory

I plug the device into my Mac (I have to use a dongle to interface USB-B plug to USB-C socket).Click to expand.I do see how this should work (and even how it might work differently than the dynamic USB host selection), but I'm having no-go.

Ftdi driver