No audio Output Device for Windows 10

Anonymous
2015-07-30T16:39:28+00:00

I just Installed windows 10 this morning everything runs fine expect for the sound, where is it?

I have tried troubleshooting the problem its says it has fixed it but the little red cross is still is cuddling into the speaker icon. I have tried everything uninstalling and installing the sound again.....does nothing. I even disabled and enabled it......does nothing. I must tell you I am not computer literate and would love for someone to just give me simple instructions and a step by step guide on how to actually fix this problem.

IDT - Audio Device - IDT High Definition Audio CODEC - Error 0x8007001f <<<<<<<<< this is the error that keeps appearing. 

Help me Obi windows Kenobi you're my only hope :)

* Moved by the Moderator to a more appropriate forum category

Windows for home | Windows 10 | Performance and system failures

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.

0 comments No comments

129 answers

Sort by: Newest
  1. Anonymous
    2015-08-16T20:49:41+00:00

    I sort of stopped half way through the calamity of having no sound now that we have all gone to the "Big 10", and I'm sorry that dude was absent upon critical rollout timeline and SHAME on product MANAGER for ever letting this poo-poo on the public that probably has a lot to do with supporting your paycheck. 'YOU'RE FIRED!" ABSOLUTELY INCROMHENSIBLE DISTRUCTION TO AN OPERATING SYSTEM!!!!!!!!!!!!!!!!!!!!!!!

    There is no way to make this HUGE error up! I just cant wait to see what you suggest we install next

    Just an idea: Send that product specialist to Iran or did you hire him from there?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-08-14T15:28:36+00:00

    These are the Hardware IDs:

    PCI\VEN_1102&DEV_000B&SUBSYS_00411102&REV_04

    PCI\VEN_1102&DEV_000B&SUBSYS_00411102

    PCI\VEN_1102&DEV_000B&CC_040300

    PCI\VEN_1102&DEV_000B&CC_0403

    It doesn't look like Creative has released their X-Fi drivers for Windows 10 yet:

    http://support.creative.com/kb/ShowArticle.aspx?sid=126331

    I expect their post a link on the above site when they are ready. Thanks!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-08-13T23:30:35+00:00

    I just Installed windows 10 this morning everything runs fine expect for the sound, where is it?

    I have tried troubleshooting the problem its says it has fixed it but the little red cross is still is cuddling into the speaker icon. I have tried everything uninstalling and installing the sound again.....does nothing. I even disabled and enabled it......does nothing. I must tell you I am not computer literate and would love for someone to just give me simple instructions and a step by step guide on how to actually fix this problem.

    IDT - Audio Device - IDT High Definition Audio CODEC - Error 0x8007001f <<<<<<<<< this is the error that keeps appearing. 

    Help me Obi windows Kenobi you're my only hope :)

    I got the solution.  right click the sound icon on toolbar.  Select playback devices from the menu. double click on speakers to open properties.  go to Advanced section.  Change bit rate to either 24 bit/44100 HZ or 24 bit192000Hz

    this solved my problem and restored sound

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-08-13T23:15:57+00:00

    These are the Hardware IDs:

    PCI\VEN_1102&DEV_000B&SUBSYS_00411102&REV_04

    PCI\VEN_1102&DEV_000B&SUBSYS_00411102

    PCI\VEN_1102&DEV_000B&CC_040300

    PCI\VEN_1102&DEV_000B&CC_0403

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-08-13T15:49:42+00:00

    Don't exactly know what we did but the speakers all of a sudden started working.   I think changing the drivers from IDT High Definition Audio CODEC to High Definition Audio Device did it. Thanks for all the help. Bob

    Yes, that would definitely do it. :-) Glad to hear you're up and running.

    By the way, to your previous question about the "System32" directory, not to worry... The name of that directory has it's roots way back in Windows history, and it doesn't mean that your system is 32-bit.

    Thanks!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments