Windows 11 ARM with bluetooth dongle can't see 1 device but sees others.

I have a medical device I use for work 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) when running in Windows 11 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. Parallels Tier 2 customer support engineer said "Parallels Desktop is visualization software, not emulation software"
Reading about 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. My case has been escalated to the Parallels development team but there is no timeline given for when they may be able to get back to me. Meanwhile, I have a $2800 MBP that I bought Thanksgiving week that I can't use for work. I'm past the return window, but am gathering all of my correspondence and research information on why it won't work for me, and am going to beg Apple to let me return it since I can't use it. Does anyone have any thoughts about the dongle being the potential issue? It's a ASUS BT500.

 

They were right, Parallels Desktop virtualizes operating systems not emulate them. If your ASUS works with other devices except the medical device, most likely it is an issue with the Raysafe View software with Windows on ARM being unable to utilize the bluetooth device, there must be something in between that is not working well on ARM.

In virtualization, virtual environment has to share the same hardware architecture as the host system. Raysafe View and most Windows application were designed for x86-based architecture and Windows only really allow those applications to run on ARM-based Windows through a compatibility layer. While many would run, it is not guaranteed whether it would function as intended, the developers would have to tweak some codes but generally, it is really difficult and not even worth their time due to the fact that as of the moment, Windows on ARM is not widely used or adopted, heck, Copilot laptops weren't even that popular.

In emulation, you would be able to run an x86-based OS on an ARM-based device. But since Parallels Desktop virtualizes, not emulate, that's not possible and I highly doubt that there are any software out there that can emulate x86 Windows on ARM-based Macs due to the fact that it is pretty difficult and emulation tends to be tremendously slower.

 

I suspect that the RaySafe View device that connects to virtual Windows session is based on Intel chipset instructions and that is why they don't support Apple Silicon (M#) and Windows ARM version that works on this platform using Parallels v18, 19 or 20. Windows ARM, not being based on Intel chipset, can't emulate all the microprocessor command sets... especially typical for special devices, such as medical, engineering, sensors, etc. They may be time dependent, as example, or perform processing operations (like a graphics processor) in the Intel processor, which can't be emulated. Have you confirmed that RaySafe application and device have requirement's for Intel-based processor... or ARM environment just untested/unsupported?

Why are you using a Bluetooth Dongle (ASUS BT500)? Are you using this on MBP versus using/sharing MacOS Bluetooth with Windows 11 ARM environment? Have you tried removing the dongle and using native bluetooth in MBP? Some setup in MacOS, Parallels and Windows ARM is required to enable this, as well as installing drivers to support connection (typically map bluetooth to serial/COM port and then to app). Or perhaps use a new Bluetooth dongle that claims support for Windows ARM on M4 MBP?

In general, bluetooth devices should be able to be connected from MacOS to WindowsARM OS, ensuring latest Bluetooth drivers (eg Broadcom) for computer hardware platform/model are installed on host system (Windows) and correct driver(s) are installed to facilitate Windows ARM being able to communicate to bluetooth device, possibly map to serial/COM port and then be accessed by application running on Windows (11) ARM. Solution unfortunately is to use NATIVE computer with Intel chipset or Intel-based MacBook (Pro)... perhaps your earlier MacBook could be used or re-installed w latest possible MacOS/software, as available?