How to Fix “Audio Disconnected: Microphone Is Not Available” Error

The “audio disconnected” or “microphone is not available” error appears in Zoom, Microsoft Teams, Google Meet, Discord, and browser-based apps when the system loses access to your microphone input. It can happen mid-call or block you from joining entirely. The cause is rarely obvious — hardware, OS permissions, a driver fault, and app settings can all produce the exact same error message. This guide walks through each fix in order from fastest to most involved.

How to Fix “Audio Disconnected: Microphone Is Not Available” Error

What This Error Actually Means

The error has two distinct failure modes. In the first, the OS or app loses contact with the microphone mid-session — often triggered by a USB device going to sleep, a driver crash, or another application claiming the input. In the second, the microphone is blocked before the call even starts, usually because an OS permission was reset after a recent update or a conflicting app is holding the device.

What This Error Actually Means

The platforms most commonly affected are Zoom, Microsoft Teams, Google Meet, Discord, and any browser-based tool running in Chrome or Edge. Each platform adds its own layer of input device settings on top of the OS, which is why fixing it at the OS level alone sometimes is not enough.

Work through the fixes in this order: hardware connection → OS permissions → app input device selection → audio drivers → advanced audio controls. If you already know your hardware is functioning, start at Step 2.

Step 1 — Verify the Hardware Connection First

Ruling out a hardware fault takes less than two minutes and prevents wasted time on software fixes.

Step 1 — Verify the Hardware Connection First

1. Unplug the microphone fully and firmly re-seat the USB or 3.5mm connector. Do not use a USB hub — connect directly to a port on the machine itself.

2. Try a different USB port. Front-panel ports on desktop PCs often have weaker power delivery and are more likely to drop USB audio devices under load.

3. Check the microphone for a physical mute button or switch. Hardware mute controls on USB and headset microphones are easy to accidentally engage.

4. Open a system recording app — Voice Recorder on Windows or QuickTime Audio Recording on Mac — and speak into the mic. Watch for an input level indicator moving on screen.

5. If audio registers in the system app, the microphone is working and the problem sits at the app or OS permissions layer. Skip to Step 3.

6. If no input appears anywhere, continue to Step 2 before concluding the device is defective.

Step 2 — Grant Microphone Permissions on Your OS

OS privacy permissions are the single most common cause of this error, and they are frequently reset without warning after a Windows or macOS update. This step takes under a minute.

Windows 10 / 11

1. Open Settings and navigate to Privacy & Security → Microphone.

2. Toggle “Allow apps to access your microphone” to ON.

   

3. Scroll down to the per-app list and confirm the toggle is enabled for Zoom, Teams, or your browser.

   

4. Close and fully restart the affected app — minimizing it is not sufficient.

Note: After a Windows feature update, per-app microphone toggles sometimes reset to OFF while the master toggle stays ON. Always check both levels, not just the top-level switch.

macOS (Ventura / Sonoma)

1. Open System Settings and navigate to Privacy & Security → Microphone.

2. Find the app in the list and enable the checkbox next to it.

3. Quit the app completely using Cmd+Q, then reopen it.

4. If the error persists after re-enabling access, restart the Mac. macOS occasionally requires a full reboot for permission changes to register correctly.

Step 3 — Select the Correct Input Device Inside the App

After a driver update, a USB reconnect, or an OS restart, apps frequently default to the wrong input device or revert to “Same as System” when the system default has changed. Always select the specific named device rather than “Default” to prevent the error from recurring.

• Zoom: Settings → Audio → Microphone dropdown → select the named device (such as “USB Audio Device” or your microphone’s brand name), not “Default.”

• Microsoft Teams: Settings → Devices → Microphone → select the specific device from the dropdown list.

  

• Google Meet: Three-dot menu (bottom right during a call) → Settings → Audio → Microphone → select the correct device.

  

• Discord: User Settings (gear icon) → Voice & Video → Input Device → select the specific device from the list.

  

After switching, speak into the mic and watch the input level meter inside the app. If it responds, the fix worked. Rejoin or refresh the call.

Step 4 — Update or Reinstall Your Audio Drivers (Windows)

A corrupted or outdated audio driver can cause the microphone to appear in Device Manager while failing silently inside applications. Follow these steps in order.

1. Press Win+X and select Device Manager.

   

2. Expand “Sound, video and game controllers.”

   

3. Right-click your audio device and select Update driver → Search automatically for drivers. Allow it to finish.

   

4. If no update is found or the error continues, right-click the device again → Uninstall device → check “Delete the driver software for this device” → click Uninstall.

   

5. Restart Windows. The OS will reinstall a clean driver automatically on reboot.

6. After restarting, press Win+R, type services.msc, and press Enter.

   

7. Locate Windows Audio in the list → right-click → Restart.

   

8. Test the microphone in Voice Recorder before reopening your call application.

Step 5 — Disable Exclusive Mode and Audio Enhancements

Exclusive mode allows a single application to lock the microphone and block every other app from accessing it. When Zoom, Teams, or a background recording tool holds exclusive control, all other apps report the microphone as “not available.”

1. Right-click the speaker icon in the taskbar → Sound settings → More sound settings.

   

2. Click the Recording tab.

3. Right-click your microphone → Properties.

   

4. Select the Advanced tab.

5. Uncheck “Allow applications to take exclusive control of this device.”

   

6. Click the Enhancements tab and select “Disable all enhancements” if you are experiencing signal drop or distortion alongside the error.

   

7. Click OK and retest.

Note: This is a frequent silent conflict in multi-app setups where a game, streaming tool, or second conferencing platform is running in the background at the same time as your main call app.

Fix for Browser-Based Apps (Chrome / Edge)

If the error appears in Google Meet, the browser version of Teams, or any web-based conferencing tool, the microphone block may be set at the browser level rather than the OS level.

1. Click the lock or info icon in the address bar of the affected site.

   

2. Select Site settings → Microphone → change the setting to Allow.

   

3. If it is stuck on “Block,” click Reset permissions, reload the page, and grant access again when prompted by the browser.

   

4. Test in an Incognito window (Chrome) or InPrivate window (Edge). If the mic works there, a browser extension in your standard session is blocking access.

   

5. Restart the entire browser after changing site permissions — closing and reopening just the tab is not sufficient.

Note: Chrome and Edge persist microphone blocks silently without displaying any visible warning, which causes many users to spend time on driver fixes before reaching this step.

When the Hardware Itself Has Failed

If the microphone does not appear in Device Manager after a clean driver reinstall and produces no input in any app or system tool, the hardware itself is likely defective. Connect a known-working microphone to confirm the system is otherwise healthy. For users who need a replacement that avoids driver conflicts entirely, the Hollyland LARK A1 is a practical option — it connects via a USB-C or Lightning receiver, requires no driver installation, and is recognized immediately by both Windows and macOS, removing the permission and compatibility friction covered throughout this guide.

When the Hardware Itself Has Failed

Frequently Asked Questions

Why does my microphone keep disconnecting during Zoom calls specifically?

The most common causes are Windows USB power management putting the device to sleep and Zoom losing its saved default device after a driver update. In Device Manager, open USB Root Hub properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Then re-select the named device in Zoom’s audio settings to restore a stable connection.

My microphone shows in Device Manager but the app still says “not available” — what’s wrong?

The app either lacks microphone permission in OS privacy settings (Step 2) or another application has taken exclusive control of the device (Step 5). Work through both steps in that order. One of these two causes accounts for the majority of cases where Device Manager recognizes the device but apps cannot access it.

Does this error occur on Mac as well?

Yes. On macOS, the most common trigger is the app not having microphone access in System Settings → Privacy & Security → Microphone. This permission resets frequently after a macOS update without any notification to the user. Granting access and fully restarting the app resolves it in most cases.

Next Steps

Work through the fixes in order: hardware check, OS permissions, app input device selection, driver reinstall, exclusive mode. Most users resolve the issue at Step 2 or Step 3 and never need to go further. If none of the software fixes restore the microphone and the device fails to appear in Device Manager after a driver reinstall, the hardware is the problem. Start at Step 1 and stop as soon as the microphone shows a live input level in a test app.