UNi Xonar drivers above v1.64 will work in Windows 10 but since the audio drivers are not yet made specifically for Windows 10 there could be some issues that you could run into depending on audio settings used. Different drivers could work differently so if you encounter any issues try installing the other UNi Xonar versions.
Apart from driver issues there could be issues solely from Windows 10 sound system that would be fixed with future Windows updates. There is also a
small chance that some things could break with future Windows updates.
- Update 30 Aug 2016: Thank you for the feedback so far. Based on the feedback received there shouldn’t be any problems installing the drivers on Windows 10 Anniversary Update (build 1607) whether it’s an upgrade or a new installation. One user reported that audio card was recognized only when installing the drivers when booting with Disable Driver Signature Enforcement option. Apart from drivers installation aspect, this new Windows build brings new problems for some users like the following reported ones: crackling or loud popping sound in the speakers, audio card not being detected sometimes or disappearing in Windows and 5.1 analog not working. For those of you who started having problems only after the Anniversary build upgrade you could roll back to a previous Windows 10 build (#1, #2). If that is not possible you can download a older Windows 10 build from here and install it without a internet connection present. To prevent upgrading to build 1607 you need to disable “Windows Update” service from Control Panel->Administrative Tools->Services.
- Update 3 Aug 2016: Microsoft made changes to driver signature policy with the Windows 10 Anniversary Update (1607) that could make the Xonar drivers not working/installing anymore. There are some exceptions from this driver signature enforcement. At the moment it’s unclear to me if installing the drivers in Test Mode or with Disable Driver Signature Enforcement still works. I’m interested in hearing you experience under this discussion thread.
- Update 28 Nov 2015: The Windows 10 Threshold 2 update does not seem to fix many of the sound issues that where present so far and it may introduce new ones. In my opinion Windows 10 is a very buggy OS, the only things working fine are the spying of its users(#1, #2) and the periodic removal of user preferences and programs(#1, #2, #3, #4).
- Update 19 Oct 2015: The audio fixes from Insider Previews >= 10547 will probably be included in the upcoming “Threshold 2” update that will be released around November 2015.
- Update 1 Oct 2015: The Windows 10 development team is fixing some audio issues with Windows 10. The fixes where made available for testing starting with Windows 10 Insider Preview build 10547.
100% compatible drivers when?
Because of the very slow development of the audio drivers by C-Media and the long time it takes for C-Media partners (ASUS and HTOmega) to release the new drivers it may take a while before we have a 100% compatible driver for Windows 10. If we are lucky we will have new audio drivers in 2-3 months after Windows 10 RTM launch. As soon as new audio drivers became available I will release a new UNi Xonar drivers package.
- Update 25 Jan 2017: 1825 audio drivers for Windows 10 are available. These are the first audio drivers that only work on Windows 10. Hopefully they will perform better than those that supported also Windows 7 and Windows 8.1.
- Update 01 Oct 2015: 1823 audio drivers are the first drivers released for Windows 10 by ASUS/C-Media. Whether they perform any better than 1822 or STXII 11.5 drivers remains to be seen.
About Chrome stutter issues on sites like YouTube. (27 Aug 2015)
- Update 27 Aug 2015: The stutter issues on youtube are fixed with the latest Chrome build released on 20 Aug 2015 (v 44.0.2403.157). Reports indicate that stutter issues are still happening for videos on other websites (eg. daily motion, facebook, instagram).
- Update 7 Aug 2015: After some testing and some reading it seems that the stuttering issues are not related to the UNi Xonar drivers. I’ve got the same behavior with Realtek’s onboard audio and from what it looked liked. My guess the issue is caused either by Windows 10 or Chrome.
There is a Chromium issue opened here.
Here are some things you could try:
- Change Chrome audio buffer size.
- Change/keep sample rate to 44.1 kHz both in the audio panel and Windows Volume->Playback devices->(…) Audio Device Proprieties -> Advanced -> Default Format.
- Change sample rates back and forward a couple of times.