M4 with Windows 11 ARM emulator bluetooth protocol?

Discussion in 'Windows Virtual Machine' started by JillB3, Dec 16, 2024.

  1. JillB3

    JillB3 Bit poster

    Messages:
    3
    I have a medical device that worked perfectly via Parallels with a bluetooth dongle on my old macbook pro. I recently bought the M4 MBP and the device software (RaySafe View) searches but cannot find the medical device. I'm using the same dongle as I did with Windows 10. I've spend hours on remote sessions with Parallels and emails with the device manufacturer. Parallels final answer was the device software is not ARM compatible and the device manufacturer said it is not really a compatibility issue between ARM and RaySafe view, the issue lies between in how well the emulator can mimic Windows. Users can set up the emulations in different ways depending on which emulator they are using and how they set it up, meaning it is more or less impossible to create a Bluetooth protocol for each variety. If that is true, the Parallels support person couldn't figure it out and I watched them try for 3 hours straight. Finding the issues with the Xbox controllers makes me wonder if it could be the bluetooth dongle, even though the dongle works with other bluetooth devices like my Bose speakers.
     
  2. HenryB12

    HenryB12 Bit poster

    Messages:
    5
    I encountered a similar situation after moving from an Intel-based Mac to an Apple Silicon system running Windows 11 ARM through Parallels. In my experience, the issue was not necessarily the application itself but how Bluetooth devices were being handled through the virtualization layer. Even though the Bluetooth dongle was detected and worked with common devices such as speakers and headphones, specialized hardware that relied on proprietary Bluetooth protocols or custom drivers often failed to be discovered. Since your device worked under Windows 10 on the previous MacBook, I suspect the problem may be related to Windows 11 ARM emulation, Bluetooth driver translation, or how Parallels passes the Bluetooth stack to the virtual machine. If RaySafe View depends on low-level Bluetooth communication, the application may be running correctly while the device discovery process is failing. It might be worth testing the setup on a native Windows PC or checking whether RaySafe has verified support for Windows 11 ARM environments, as that could help determine whether the limitation is with the software, the Bluetooth implementation, or the virtualization platform itself.
     

Share This Page