> Complete documentation index: [llms.txt](/llms.txt). Markdown versions of all pages are available by appending `.md` to page URLs.

# Windows and macOS

> Fix a Binho Supernova, Pulsar or Atira that is not found on Windows or macOS, and undo a driver change that broke it.

The Supernova, the Pulsar and the Atira need no driver on Windows or macOS. This page covers what to check when the adapter is not found, and how to undo a driver change that breaks it.

On Linux, see [Solving USB Connection Issues on Linux](/support/troubleshooting/solving-usb-connection-issues-on-linux/).

## No Driver Needed

Each adapter presents two USB interfaces:

| Interface | Used for | Windows | macOS |
| --------- | -------- | ------- | ----- |
| HID | Commands and replies | Built-in HID driver | Built-in |
| Vendor (bulk) | Large transfers in PyCosmicSDK and CosmicSDK | WinUSB, bound automatically | Built-in |

The firmware tells Windows (8.1 and later) to bind WinUSB to the vendor interface through a Microsoft OS 2.0 descriptor. No INF file, installer or **Zadig** is needed.

## Windows

### The Adapter Is Not Found

1. Open **Device Manager** and plug the adapter in. Look for a new entry under **Human Interface Devices** and **Universal Serial Bus devices**.
2. If nothing appears, change the cable first. Many USB cables carry power only. Then try another USB port, directly on the computer rather than through a hub.
3. Close every other program that may use the adapter: Mission Control 3, Mission Control 2, a Python script, a browser tab on [mc3.binho.io](https://mc3.binho.io).
4. If the adapter appears as a USB drive named **SUPERNOVA** or **PULSAR**, it is in its bootloader. See [Firmware and Bootloader](/support/troubleshooting/firmware-and-bootloader/).

### Undo a Zadig or libusb Driver Override

If Zadig was used to install **libusbK** or **libusb-win32** on the adapter, that driver replaces the WinUSB binding and large transfers can stop working. Put the default back:

1. Plug the adapter in and open **Device Manager**.
2. Find the adapter under **libusbK USB Devices**, **libusb-win32 devices** or **Universal Serial Bus devices**.
3. Right-click it, choose **Uninstall device**, and tick **Attempt to remove the driver for this device** (or **Delete the driver software for this device**).
4. Unplug the adapter and plug it back in. Windows binds WinUSB again on its own.

Repeat for each Binho entry that shows the replaced driver.

### Installer Warning

The Mission Control 3 Windows installer is code-signed. If **Windows protected your PC** (SmartScreen) appears for a new release, click **More info**, check that the publisher is Binho, then click **Run anyway**. Download the installer only from [binho.io](https://binho.io/test-measurement/mission-control-3).

## macOS

1. macOS uses its built-in drivers. Nothing needs to be installed. On a Mac laptop with Apple Silicon, macOS may ask once whether to allow the accessory to connect: allow it.
2. If the adapter is not found, check **System Information → USB** (hold **Option** and choose **Apple menu → System Information**). If it is not listed, change the cable and the port.
3. Close other programs that may use the adapter.
4. If the adapter mounts as a drive named **SUPERNOVA** or **PULSAR**, it is in its bootloader. See [Firmware and Bootloader](/support/troubleshooting/firmware-and-bootloader/).

## PyCosmicSDK

PyCosmicSDK runs on Python 3.10 to 3.14, with wheels for Windows x64, macOS on Apple Silicon and Linux x86_64. Check what it sees:

```sh
python -c "import pycosmicsdk; print([(d.model.name, d.serial_number, d.fw_version) for d in pycosmicsdk.list_devices()])"
```

An empty list means the operating system does not see the adapter: go back to the checklists above. More in the [PyCosmicSDK getting started guide](https://binhollc.github.io/pycosmicsdk/getting-started.html).