Menu ▾ ▴

#363 Getting Device error

1.x
open
nobody
None
2026-10-10
2026-10-10
No

This has always worked right, all of suden the mic is not detected the image shows the erro the mic works fine with out the software no issues.!

1 Attachments

Discussion

  • Peter Verbeek

    Peter Verbeek - 2026-10-10

    Usually this is caused by a new Windows update which includes some update software for your AWC4710 mic. Unfortunately it might be difficult to get Equalizer APO going (again) on it. Did you install specific software for this mic yourself?

     
  • Chris Buhneing

    Chris Buhneing - 2026-10-10

    First off thanks for your reply. No just windows default detection no other software other then APO. It is a shame becuase it has worked so well. I did recently update windows 11 to the 26h2, but really did not notice APO not working untill I was in discord last night.
    Thanks

     
    • Peter Verbeek

      Peter Verbeek - 2026-10-10

      Since you mention Discord could you verify if Equalizer APO is working when using a recording app like Audacity. This rules out a Discord issue. Also note that Discord has an audio setting called "Audio subsystem". Usually Automatic does the trick but others have set it on Legacy.

      Btw. I yet have to try install 26H2, just to see if how or if it affects Equalizer APO. This is important for my Peace equalizer users and my continuous support of Equalizer APO (of which I'm not the developer).

       
  • Chris Buhneing

    Chris Buhneing - 2026-10-10

    I think I have it figured out, the speakers work fine with APO and the Peace interface, the mic worked untill I did the update in which MS updated the driver for it, I reverted back to the old driver and it works fine now. I wish MS would not include updated drivers for hardware in there feature updates it breaks things and is to hard to keep up with. Thank Man

     

    Last edit: Chris Buhneing 2026-10-10
    • Peter Verbeek

      Peter Verbeek - 2026-10-10

      Yeah, one of things that sometimes happens. I don't understand why this happens. What possibly has been changed in the driver and/or software? Anyway, glad to hear you have figured it out.

       

Log in to post a comment.