Bug Report – VirtualHere + Apple Silicon + ScanSnap S1500

Bug Report – VirtualHere + Apple Silicon + ScanSnap S1500

Product: VirtualHere USB Client & Server
Versions tested:

• Server: VirtualHere USB Server v4.8.6 (Windows 10, running on VirtualBox)
• Client: VirtualHere Universal Client v5.9.5 (macOS Apple Silicon M4)
• Scan device: Fujitsu ScanSnap S1500 (USB 2.0)

Summary

When a ScanSnap S1500 is accessed via VirtualHere from an Apple-Silicon Mac (M4), the scanner enters a dead USB state after the client disconnects.
After this happens, the device cannot be reconnected by any client (Intel or ARM) until the USB device is physically reattached or re-captured by the Windows VM.

This does not happen when only Intel Macs are used.

Environment

• Windows 10 VM (VirtualBox)
• ScanSnap S1500 attached via USB to the VM
• VirtualHere Server v4.8.6 running (GUI and Service tested)
• Intel Macs (macOS) with VirtualHere client: stable
• Apple Silicon Mac (M4) with VirtualHere Universal Client v5.9.5: causes failure

Reproduction steps

1. Intel Mac connects to the ScanSnap via VirtualHere → works
2. Intel Mac disconnects → works
3. Apple Silicon Mac (M4) connects → works
4. Apple Silicon Mac disconnects
5. Any client (Intel or ARM) tries to reconnect → device no longer works
6. Only a USB replug (or VM USB re-capture) restores the scanner

Observations

• Intel macOS clients do not cause this
• Apple Silicon clients always perform a USB bus reset on disconnect
• The ScanSnap S1500 cannot survive this reset and becomes unusable
• Using Rosetta (x86_64) on Apple Silicon does not change the behavior
• Using the macOS client as a kernel/service client avoids the reset, but the Windows Server blocks service clients, so this mode cannot be used

Impact

This makes it impossible to use ScanSnap S1500 (and likely similar USB-2 isochronous scanners) in a mixed Intel + Apple-Silicon macOS environment via VirtualHere.

Requested

Please provide a client option on macOS Apple Silicon to disable USB bus reset on device release, or change the default behavior to match Intel macOS clients.