Studio Effects is not only about the camera — Voice Focus, its NPU-powered noise removal, can make a noisy room sound like a studio. But when Windows reports that no microphone is detected, the whole audio side of the effects stack goes dark: no Voice Focus toggle, no input level movement, and your calls fall back to raw, noisy mic audio.

“Mic not detected” sits at the intersection of two systems: Windows audio (devices, drivers, privacy permissions) and the NPU effects layer (Voice Focus). The microphone itself can be perfectly fine while either layer blocks it. That is why the fix order matters — you check the audio plumbing before you touch anything AI-related.

This guide works bottom-up: physical and privacy checks, device routing, driver repair, then the Voice Focus layer itself. If your mic records fine but calls still sound bad, our Copilot+ PC microphone guide picks up where this one leaves off.

Why this happens

  • Microphone privacy blocking access: Windows 11 privacy settings can deny microphone access globally or per-app — the most common cause, and the easiest to miss.
  • Wrong input device selected: With headsets, docks, and monitors all exposing microphones, Windows often listens to the wrong one.
  • Audio device disabled: The microphone array can be disabled in Sound settings or Device Manager, sometimes by an OEM utility or update.
  • Corrupt audio driver: A broken Realtek, Intel Smart Sound, or Qualcomm audio driver makes the mic vanish from the input list entirely.
  • Bluetooth headset routing confusion: Headsets switching between Hands-Free and Stereo profiles can leave Windows with no working input path.
  • NPU driver breaking Voice Focus: The mic works for recording, but the Voice Focus effect toggle is missing because the NPU layer failed.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check microphone privacy permissions

Windows 11 can silently revoke microphone access after updates, and no driver fix will help while the OS-level gate is closed. This is the first check because it is the most common cause and takes thirty seconds.

  1. Go to Settings > Privacy & security > Microphone and confirm Microphone access is turned On.
  2. Confirm “Let apps access your microphone” is On, and that your calling app specifically is allowed in the list below.
  3. Also check “Let desktop apps access your microphone” — classic Win32 apps like older Zoom builds need this separate toggle.
  4. Open Settings > System > Sound, scroll to Input, and see if your microphone now appears with a moving volume bar when you speak.
  5. If the mic appears here, privacy was the blocker — retest Voice Focus in Quick Settings.

Fix 2: Select the right input device and unmute it

Windows routinely picks the wrong microphone — a monitor’s mic, a dock’s mic, or a disconnected headset — especially on laptops that move between desks. If you use a USB dock, also glance at our USB dock not working on ARM laptop guide since docks are a frequent source of audio-routing chaos.

  1. Go to Settings > System > Sound > Input and click the dropdown to see every input device.
  2. Select your intended microphone (internal array or headset mic), then speak and watch the input volume bar.
  3. Click the device, then Properties, and make sure it is Enabled and the volume is up — not muted at 0.
  4. In the calling app’s audio settings, set the microphone explicitly instead of “Default” or “Same as system.”
  5. Disconnect Bluetooth headsets temporarily and retest with the internal mic to isolate headset routing issues.

Fix 3: Re-enable a disabled audio device

Microphone arrays get disabled more often than people expect — by OEM audio utilities, by Windows updates, or by an accidental click in a legacy dialog. A disabled device does not appear in the normal Sound settings list at all.

  1. Go to Settings > System > Sound, scroll down, and click More sound settings to open the classic dialog.
  2. In the Recording tab, right-click empty space and check Show Disabled Devices and Show Disconnected Devices.
  3. If your microphone appears grayed out, right-click it and choose Enable, then Set as Default Device.
  4. Speak and confirm the green level bars move.
  5. Also check Device Manager > Audio inputs and outputs — if the mic shows a down-arrow (disabled), right-click and Enable device there too.

Fix 4: Reinstall the audio driver

If the microphone does not appear even among disabled devices, the audio driver is the problem. On AI laptops this is usually the Intel Smart Sound Technology driver, Realtek audio, or the Qualcomm audio stack on Snapdragon machines.

  1. In Device Manager, expand Audio inputs and outputs and Sound, video and game controllers.
  2. Right-click the microphone array and audio controller entries, choose Uninstall device (do not delete driver files on the first pass), and restart.
  3. After reboot, check whether the mic reappears in Settings > System > Sound > Input.
  4. If it is still missing, uninstall again — this time checking “Attempt to remove the driver for this device” — then install the audio driver from your laptop maker’s support page as administrator.
  5. Restart once more and confirm the mic records in the Sound Recorder app before testing calls.
  6. If you are setting up a new machine and hitting this during initial setup, our AI PC new laptop setup checklist covers driver order so audio does not get skipped.

Fix 5: Restore the Voice Focus effect toggle

If the microphone records fine but the Voice Focus toggle is missing from Quick Settings, the audio layer is healthy and the NPU effects layer is not. Voice Focus needs the NPU driver just like the camera effects do. See Microsoft’s Windows support page for official audio-effects background.

  1. Open Device Manager > Neural processors and confirm the NPU is present with no warning icon.
  2. If flagged, update or clean-reinstall the NPU driver from your laptop maker’s support page, then restart.
  3. Go to Settings > System > Sound, select your microphone, and look for the Voice Focus / audio effects section — enable it there directly.
  4. During a call, press Win + A and check the Studio Effects panel for the microphone effect toggle.
  5. Retest on a call with background noise (a fan, typing) — working Voice Focus audibly strips it out.

Fix 6: Rule out hardware with a USB microphone test

If nothing above brings the internal mic back, determine whether the problem is the built-in microphone hardware or the Windows audio stack — a five-minute test with any USB mic or headset settles it.

  1. Plug in any USB microphone or USB headset and select it in Settings > System > Sound > Input.
  2. If the USB mic works perfectly, your Windows audio stack is fine and the internal mic array (or its connection) is the fault — contact your laptop maker’s support, especially under warranty.
  3. If the USB mic also fails to appear, the Windows audio subsystem itself is damaged — run Settings > System > Troubleshoot > Other troubleshooters > Audio and consider an in-place Windows repair install.
  4. Before a warranty call, note your audio driver versions and BIOS version — support will ask, and having them ready shortens the process considerably.

Closing

“Mic not detected” is almost always a gate, not a grave: a privacy toggle, a wrong device selection, a disabled entry, or a driver that needs reinstalling. Work the audio plumbing first — privacy, routing, drivers — and only then the Voice Focus NPU layer. Test with Sound Recorder at each stage so you always know whether the mic itself is alive. Once Windows hears you again, Voice Focus comes back with one toggle.

Frequently asked questions

What is the Studio Effects microphone feature?
Studio Effects includes an NPU-powered Voice Focus effect that removes background noise from your microphone in real time. It appears as a microphone effect in Quick Settings and in Settings > System > Sound, processed on the NPU so calls stay clear without CPU load.
Why does Windows say no microphone is detected?
The usual causes are microphone privacy blocking access, the wrong input device selected, a disabled audio device, or a corrupt audio driver. If the mic works in one app but not another, it is a permission or routing issue, not a hardware failure.
Does Voice Focus need the NPU?
Yes — Voice Focus is an NPU effect on Copilot+ PCs. If the NPU driver is broken, the Voice Focus toggle may vanish even though the microphone itself works fine for basic recording.
Can a headset cause the 'mic not detected' error?
Yes. Bluetooth headsets in particular can confuse Windows’ device routing — the system may listen to the laptop mic while you speak into the headset, or vice versa. Unpairing the headset temporarily is a quick way to isolate this.