If your audio interface not working is ruining your session, start with the basics: check the cable and power, select the interface as your computer’s and DAW’s audio device, install the latest driver, and set a sensible buffer size. Most problems are configuration or connection issues, not faulty hardware. Work through the steps below in order.
Step 1: Check the physical connection
Begin with the obvious, because it is usually the culprit.
- Reseat the USB-C or Thunderbolt cable at both ends, and try a different known-good cable. Many cables are charge-only and carry no data.
- Plug directly into the computer, not through an unpowered hub, which may not supply enough power.
- Confirm the interface’s power light is on. Bus-powered units need a port that supplies adequate power.
- Try a different port on your computer.
Step 2: Select the interface as your audio device
Your computer and your DAW each have their own sound settings, and both must point at the interface.
- Windows: Set the interface as the default playback and recording device in Sound settings.
- macOS: Choose the interface for input and output in System Settings > Sound, or in Audio MIDI Setup.
- In your DAW: Open audio/device preferences and select the interface (on Windows, choose its ASIO driver). If the interface is “not working” only inside your DAW, this is the most common cause.
If you are still setting things up for the first time, our guide on how to set up an audio interface covers this in full.
Step 3: Install or reinstall the driver
Outdated or missing drivers cause most “device not recognised” problems, especially on Windows.
- Download the latest driver from the manufacturer’s site for your exact model and operating system.
- On Windows, install the brand’s ASIO driver; on macOS, many interfaces are class-compliant but still benefit from the official driver/firmware.
- Restart after installing, and update firmware if the manufacturer’s tool prompts you.
- If it once worked and now does not after an OS update, check for a newer driver, as compatibility often lags behind major OS releases.
Step 4: Fix “no input” or “no sound” issues
If the interface is recognised but you get no signal, check these.
- No mic signal: Turn up the input gain, confirm the cable is in the right input, and enable phantom power if you are using a condenser (see what is phantom power).
- Low or noisy signal: Revisit your gain staging; too little gain leaves you in the noise floor.
- No playback: Raise the monitor/headphone level, and check the direct-monitor vs DAW-monitor balance knob if your interface has one.
- Track not recording: Arm the track, select the correct input on it, and check the input is not muted.
If you have signal at the input but nothing reaches your speakers or headphones, our dedicated walkthrough on how to fix no sound from your audio interface covers the playback-side checks in more depth.
Step 5: Tackle dropouts, glitches and latency
Crackles, pops and stutters usually mean the buffer is too small or the system is overloaded.
- Raise the buffer size in your DAW’s audio settings to stop glitching (lower it again only when tracking, to reduce latency).
- Close other apps and disable wireless adapters or power-saving modes that interrupt the audio stream.
- Make sure the sample rate matches between your interface, computer and project; a mismatch causes clicks. See sample rate and bit depth explained.
Step 6: Isolate hardware vs software
If nothing above works, narrow down the cause:
- Try the interface on a different computer. If it works there, the issue is software/driver on your main machine.
- Test with a different DAW or your OS sound recorder to rule out a single app’s settings.
- Power-cycle: unplug the interface, restart the computer, then reconnect.
- If it fails on every computer with good cables, the unit may be faulty, contact the manufacturer.
How to work through the problem efficiently
Troubleshooting feels chaotic when you change several things at once, because you never learn which fix actually mattered. The reliable approach is to change one variable at a time and re-test after each change. Start at the cable and work inwards toward the software, since the physical layer is both the easiest to check and the most common point of failure.
Before you dive in, take ten seconds to define the exact symptom, as the wording points straight at the likely cause:
- The interface is completely absent from your computer’s sound settings and device list. This is almost always a cable, port or driver problem, so concentrate on Steps 1 and 3.
- The interface appears but a particular input or output is silent. This is a routing, gain or phantom-power issue inside Step 4 rather than a hardware fault.
- Everything is recognised but the audio crackles or drops out. This is a buffer, sample-rate or system-load problem, so focus on Step 5.
Matching the symptom to the right step stops you reinstalling drivers when the real problem is a muted track, or buying a new cable when the buffer is simply set too low.
Common mistakes that look like a broken interface
Many “dead” interfaces are perfectly healthy. These are the recurring traps that send people down the wrong path:
- Using a charge-only cable. A cable that powers the unit but carries no data will light the power LED while the computer sees nothing. Always test with a known data cable first.
- Forgetting the DAW has its own device menu. Setting the interface as the system default does not select it inside your DAW; the two settings are separate and both must be correct.
- Expecting sound without phantom power. Condenser microphones need 48 V to function at all, so a silent condenser is usually a phantom-power switch left off, not a faulty input.
- Running through an unpowered USB hub. Bus-powered interfaces can brown out on a shared hub, causing intermittent dropouts that look like a hardware fault; a powered USB hub built for audio interfaces avoids this.
- Mismatched sample rates. If the interface, the operating system and the project disagree on sample rate, you get clicks, pitch shifts or no sound, even though every cable is fine.
- Leaving plugins or input monitoring to blame. A heavy plugin chain or a feedback loop from monitoring the wrong source can masquerade as an interface glitch.
When you suspect a fault, the quickest sanity check is to bypass your project entirely: open the operating system’s own sound recorder, speak into the mic, and play it back. If that works, the hardware is fine and the problem lives in your DAW settings.
Frequently asked questions
Why is my audio interface not recognised by my computer?
Usually a cable, port or driver issue. Try a known-good data cable plugged directly into the computer, then install the latest driver for your exact model and operating system and restart.
My interface works but there’s no microphone sound, what’s wrong?
Check that input gain is up, the mic is in the correct input, and phantom power is on if you use a condenser. Then confirm your DAW track is armed and set to the right input.
How do I stop crackling and dropouts?
Increase the buffer size in your DAW, match the sample rate across your project and interface, and close background apps. Crackles almost always point to buffer or system-load problems rather than a broken interface.
Should I use the USB port on my keyboard or monitor for my interface?
Where possible, plug the interface straight into a port on the computer itself. Ports built into keyboards, monitors and unpowered hubs often share limited power and bandwidth, which can cause dropouts or stop a bus-powered interface from being recognised at all.
My interface stopped working after a system update, how do I fix it?
Major operating-system updates often break older drivers. Visit the manufacturer’s site, download the newest driver and firmware released for your operating-system version, install them, and restart. If no compatible driver exists yet, you may need to wait for an update before the interface behaves normally again.
