I don't know if anybody has noticed this (because I don't read each and every post) but If you upgrade from Win 8.1 to latest Win 10 10162, latest drivers (in my case ALC 892 6.0.1.7541 WHQL) will work with Win 10 flawlessly. If you try to upgrade to a newer driver and don't disable Windows auto driver install Win will go into a loop of uninstall with the driver your trying to update. If you disable windows auto driver install, you will be able to install the latest drivers (6.0.1.7548 WHQL) but in my case they won't work. I tried to revert back to my working driver but that didn't work either. I think that this is more of a Windows issue rather than a Realtek issue because they work flawlessly in Win 8.1 and work the same if you upgrade. Just my 2 cents I will post on feedback.
Yes, this is confirmed, its a Windows 10 problem/bug, that appeared only in the latest builds. And not only affects Realtek sound cards, but others, like my Asus Xonar D2X. It's a MAJOR bug, so it would be unacceptable if Microsoft didn't fix this for RTM.
I have the same issue on my laptop man. I have to use headphones or an external speaker. I even tried the latest drivers from Realtek, I assume with time they will be updated and corrected.
Do this . Sound icon left click....playback devices...double click on your connected speakers......advanced....and here you try the sample rates one by one until you hear sound.It`s the only fix now. Even the newest driver R2.79 does not fix it , cause it`s windows problem btw.
Thanks for the quick answers - After installing build 10166 I can also confirm the issue has been resolved!
Has anyone experienced this issue. I am booting win7 and win10 on the same machine, separate hard drives. It's a gigabyte board with realtek ac1150. I use win 10 to test software in development. whenever I switch from the windows 10 disk and boot from the windows 7, I have sound issues. Sometimes no sound as if the drivers are not being loaded properly. I can only resolve this by doing a hard reset ie. completely shutdown and reboot in windows 7. This never happens when I switch from win dows 7 to windows 10 though. It only happens after I've been running windows 10 and moving to wndows 7.