Start with the cable, port and power
Most “not detected” problems come from the cable, the port or the driver, rather than a dead interface. Work through these checks first:
- Swap the cable. Many USB cables are charge-only and have no data lines.
- Connect directly to the computer. Skip unpowered hubs, USB ports on monitors and front-panel ports on the case.
- Try another port. For USB-C, try a different adapter or a direct USB-C to USB-C cable.
- Check the power supply. If the interface has its own power supply, make sure it’s connected and switched on.
Thunderbolt interfaces
Thunderbolt interfaces need a Thunderbolt port. A plain USB-C port won’t work with them, so check which port your computer has.
On Windows
Install the driver
Install the maker’s driver, ideally before you first connect the interface, and restart the computer afterward. Download it from the maker’s website rather than relying on a generic driver.
Check Device Manager
Press Windows + X, choose Device Manager, and expand Sound, video and game controllers. A yellow triangle or an “Unknown device” entry means there’s a driver problem. Reinstall or update the maker’s driver, then restart.
Check microphone privacy
Open Settings > Privacy & security > Microphone. Allow microphone access for apps, and for desktop apps.
Turn off USB selective suspend
In your power options, disable USB selective suspend. This stops Windows from putting the USB port to sleep to save power, which can cause the interface to drop out.
On Mac
See whether macOS detects it
Open System Information and look under USB or Thunderbolt. If the interface is listed, the hardware is being detected, and the problem is more likely in the app or its settings. If it isn’t listed, check the cable and port again.
Allow the accessory
On Apple silicon Macs running macOS Ventura or later, you may see an “Allow accessory to connect?” prompt. Approve it.
Check permissions and MIDI settings
- In System Settings > Privacy & Security > Microphone, allow your DAW.
- Open Audio MIDI Setup and check that the interface is listed.
Older driver extensions
Some older kernel-extension drivers need approval under Privacy & Security. On Apple silicon, they may also need changes to Startup Security Utility in Recovery mode. Follow the maker’s guidance first, and weigh the security trade-off before you change any security setting. Treat lowering security settings as a last resort.
When the DAW doesn’t use it
Sometimes the operating system sees the interface, but the DAW doesn’t. Select the interface in the DAW’s audio preferences. On Windows, choose the interface’s ASIO driver. Being shown by the operating system doesn’t mean the DAW is using it, so check the DAW’s settings separately. In FL Studio, a common symptom is a take that records nothing; see why your FL Studio recording is silent.
Update drivers and firmware
Check the maker’s website for the latest driver and firmware, and install any updates. Restart after you install them.
Common misconceptions
- ASIO4ALL doesn’t fix hardware or USB detection problems. It’s a driver layer and can’t repair a cable or port.
- “Not detected” is usually the cable, the port or the driver, not a dead interface.
- Being shown in the operating system doesn’t mean the DAW is using the interface. Check the DAW separately.
When to contact the maker
If the interface still doesn’t appear after these steps, try it on another computer. If it still doesn’t show up, contact the maker or a repair shop.
For a related problem, see how to fix static, buzz and digital noise from an audio interface. For the full setup path, see how to set up an audio interface for home recording.