WIN11 INPUT issue with MIC that worked and then stopped working

Beata Higham 20 Reputation points
2025-07-15T23:26:12.86+00:00

I'm here as I have tried everything so far and the mic is still not producing absolutely any sound.

I have a focusrite audio interface.

MIC was working fine, but then I plugged in Guitar to the Audio Interface, which required me to change AUDIO DEVICE TYPE within the DAW from Windows Audio (that mic was working with) to ASIO, because Guitar didn't want to work with Windows Audio. I used Guitar just fine and wanted to record audio using my MIC that is a condenser if that makes any difference, and I have phantom power on at 48V so it SHOULD WORK again. At first I thought the issue lies in the ASIO Audio Device Type, so I changed it back to Windows Audio, setting the Output back to the audio Interface (Focusrite Audio) and Mic back to Analogue 1 and 2 (Focusrite Audio) Which was the DAW setting prior to playing guitar. Mic seems dead.

I used troubleshooters and tutorials on Sound Input and made sure that everything is the way it should be. It is. Mic still dead though.

Finally as the last resort I uninstalled all Focusrite Input Drivers, restarted computer hoping this will work. It didn't

System is recognising the mic. Apps say Mic has been in use by DAW and WIN11 settings, showing me exact timeframe so i see that its detected, enabled, the channels are right, the 24 bit 48000 hz matches the DAW, volume is obviously 100% at the moment.

When testing, with gain and output and volume all 100% (it should kill my ear drums), Headphone volume 100% i get literally 0% of volume level from Mic.

I don't know what else to do, please help.

Is there any way to check this type of mic otherwise?

Windows for home | Windows 11 | Settings
0 comments
Answer accepted by question author
Kai-H 24,410 Reputation points Microsoft External Staff Moderator
2025-07-16T06:04:01.2433333+00:00

Hello , Beata Higham

Welcome to Microsoft Q&A.

Thank you very much for providing such a detailed troubleshooting process. This is definitely a classic and extremely confusing audio interface issue. I completely understand your frustration. You’ve already ruled out all the surface-level causes, which is excellent. Based on your description, the problem appears after switching between ASIO and Windows Audio driver modes, so we can narrow down the focus.

ASIO (Audio Stream Input/Output) drivers, in order to achieve ultra-low latency, directly and exclusively control your Focusrite audio interface hardware. When you select ASIO mode in your DAW, it effectively bypasses most of Windows’ standard audio processing pipeline.

The issue is that when switching back from ASIO to Windows Audio, sometimes the ASIO driver or Focusrite’s control software fails to completely “release” control of the hardware. This may leave the device in a muted or “routing-interrupted” state at the hardware level—even if Windows and your DAW appear to be configured correctly. The system believes the microphone is working, but the physical input signal is being cut off before it ever reaches the software layer due to this “ghost configuration.”

We can perform a deeper “hard reset” and diagnosis process, from software to hardware. Please follow the steps in order and do not skip any, as each one is designed to rule out a specific possibility.

Step 1: Force-refresh the state in Focusrite Control software

This is the most likely step to resolve the issue. Your Focusrite interface’s companion software—Focusrite Control (or MixControl for older models)—is the true control center for the hardware, taking precedence over both Windows and DAW settings.

  1. Completely close your DAW software. Ensure it is not running in the background.
  2. Open the Focusrite Control software.
  3. Look for input level meters: In the interface, find the channel representing your microphone input (Analogue 1 or 2). Speak into the mic and check whether the level meter moves.
    • If the meter moves: The issue lies in the software routing. In Focusrite Control, check if that channel is muted or if the fader is pulled all the way down. Also check the Output Routing to make sure Analogue 1+2 is correctly routed to an output (like Headphone Out or Main Monitor Out).
      • If the meter does not move: This confirms the “ghost control” theory—the signal is being blocked at the hardware level. Try the following in Focusrite Control to “wake it up”: 
         - Change the Sample Rate from 48kHz to 44.1kHz, then change it back.

       - Toggle Input Type (e.g., switch between Line/Inst if available).

             - Save and reload presets: In the _File_ menu, save the current settings as a Snapshot, then load a factory preset (like “Direct Routing”) to see if signal returns, and finally reload your saved Snapshot.

Step 2: Full physical and driver reset

If Step 1 doesn’t work, we’ll force the computer and interface to re-initialize their relationship.

  1. Keep your computer powered on.
  2. Disconnect the Focusrite USB cable.
  3. Wait 10 seconds.
  4. Completely shut down your computer (not just restart).
  5. Wait 30 seconds.
  6. Boot the computer and let Windows fully load.
  7. Reconnect the Focusrite USB cable. Wait for Windows to re-detect and initialize the device.
  8. After this, first open Focusrite Control to check the input level, then launch your DAW.

Step 3: Final hardware testing

This is the standard process to isolate the fault. We need to determine if the issue is with the microphone, the XLR cable, or the audio interface itself.

  • Test the interface: If you have a guitar, it’s a perfect test source. Plug the guitar into the instrument input (Inst) on the Focusrite. Select that input in Focusrite Control and your DAW. If you get a signal, at least part of the interface is working.
  • Test the cable: If you have another XLR cable that you know works, swap it and retest.
  • Test mic/interface combinations (cross-check with another microphone if available).

I believe the issue most likely lies in the internal software state mentioned in Step 1. Please try these steps carefully and let us know the results. Looking forward to your feedback.

Best wishes

Kai Ho | Microsoft Q&A Support Specialist

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.