Ask
118
@oncall_omar ·

Headset mic drops out mid-call since a Windows update: what actually fixed it for you? Troubleshooting

Wired gaming headset that has worked for two years, and since an update last month the mic cuts out after roughly ten minutes on a call and only comes back if I unplug and replug. It happens on two different conferencing apps, so it is not one piece of software. I have already reinstalled the audio driver and disabled the exclusive-mode setting, which did nothing. Before I buy a replacement, has anyone chased this one to the end?

8 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @pop_filter_paz · 2w ago

    If that does not do it, try a different physical port and specifically one on the back of the machine rather than a front panel or a hub. Front panel headers and cheap hubs are the most common cause of intermittent audio devices, and the fact that it survived two years does not clear them, because a cable inside a case can work loose.

    143
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @muslin_mira · 2w ago · 3 replies

    Check USB selective suspend and the power management tab on the USB root hub before you buy anything. The classic version of this is the operating system putting the hub to sleep because it thinks the device is idle, and it looks exactly like a hardware fault: works, then does not, then works again on replug. Untick the allow-the-computer-to-turn-this-off box on every hub in the list, not just the one you think it is on.

    187
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @envelope_esme · 2w ago

      This is the fix nine times out of ten, and the trap is that people untick it on the one hub the device shows up under and leave the other three alone.

      96
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @chmod_confused · 2w ago

      Same fix here about a year ago. It also explains why it always seemed to happen after roughly the same interval.

      71
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @stdlib_stef · 2w ago · 2 replies

    Also worth ruling out the software layer: some vendor control apps update themselves quietly and take over the device, and some conferencing clients grab exclusive access. Close the vendor app entirely, not to the tray, and see whether the fault survives. I lost a whole evening to a companion app I did not know had installed a service.

    121
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @printbed_gremlin · 2w ago

      Vendor audio suites install a background service that survives closing the window, and the uninstaller often leaves it behind. Check the services list rather than the tray, which is where I finally found mine.

      88
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @duckweed_dev · 2w ago

    Test it on a phone with an adapter or on another machine for an hour. Fifteen minutes of that tells you whether you are debugging a headset or debugging a computer, and everyone including me skips it and then buys a new headset that has the same problem.

    108
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @boom_pole_bex · 2w ago

    If it turns out to be the cable at the connector, which is where these usually die, and the headset is otherwise fine, a lot of models have a replaceable cable for a fraction of a new set. Worth checking before you write it off.

    87
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report