Microphone array missing from Device Manager

Anonymous
2018-03-18T19:34:36+00:00

Hi,

The microphone on my wife's Surface Laptop isn't working, and the "Micrphone Array" is simply missing from the device Manager. I already uninstalled and reinstalled the Realtek High Definition Audio drivers, to no avail.

It does not show in the Recording Devices dialog box, not even as disabled or disconnected.

I also tried the troubleshooters: the Speech troubleshooter that comes with Windows crashes on the middle of deployment. The Recording Audio troubleshooter runs till it lists the hardware available. Here, it lists the external microphone (that is not connected), but the local where it should list the internal array is blank (although selectable). After this, the troubleshooter crashes. 

I also found an equivalent troubleshooter online, on one Microsoft site. This downloads, but doesn't deploy, returns an "unknown error".

The computer is running Windows version 1709, OS Build 16299.309.

I also tried manually download the latest drivers and firmware from Microsoft, installed it but nothing changes.

I'm absolutely lost. Any ideas?

Thanks in advance,

//Ricardo

Surface | Surface Laptop | Sound and camera

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2018-03-20T03:29:53+00:00

    The Recording Audio troubleshooter runs till it lists the hardware available. Here, it lists the external microphone (that is not connected), but the local where it should list the internal array is blank (although selectable). After this, the troubleshooter crashes.

    One option you could try instead would be to use the PowerShell equivalent while using Administrator: Windows PowerShell (e.g. to ensure that the troubleshooter was being executed while elevated).  It may give a different perspective to your "crash" symptom too.

    CD $env:windir\Diagnostics\System\Audio

    $P = Get-TroubleshootingPack  .

    Invoke-TroubleshootingPack  $P  -Result $env:TEMP\TA

    You will see the prompts as numeric inputs.  Then when you are done you can go to the Result location to find some reports.  IE can be used to find them by AutoComplete in the Address bar and will partially interpret them for you.

    HTH

    Robert


    2 people found this answer helpful.
    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-03-19T13:17:55+00:00

    Hi,

    The challenge you are experiencing with the Microphone array might be software-related. This means that a setting may not be set up appropriately, or that a specific driver is not installed correctly.

    Since you mentioned that the Microphone array does not show, are there any recording devices available on the Sound dialog box? If you see any, right-click on it and choose "Show Disabled Devices".

    Update us with the outcome so we can further assist you.

    Regards.

    0 comments No comments
  2. Anonymous
    2018-03-19T15:01:32+00:00

    Hi,

    As tried to explain in my first post, nothing appears on the sound / recording dialog box.

    Thanks for your time,

    //RF

    0 comments No comments
  3. Anonymous
    2018-03-19T17:46:35+00:00

    found an equivalent troubleshooter online, on one Microsoft site. This downloads, but doesn't deploy, returns an "unknown error".

    More details could help.  FWIW I have noticed that some troubleshooters appear only to be automation aids which depend on using an existing troubleshooter that in fact does not exist.

    0 comments No comments
  4. Anonymous
    2018-03-19T19:45:16+00:00

    It was Microsft's own troubleshooter, found here: https://support.microsoft.com/en-au/help/4023471/surface-troubleshoot-surface-sound-and-audio-accessories

    It returns the following error

    This running the sound recording troubleshooter. The hardware and devices troubleshooter finds no problems.

    0 comments No comments