Creative SB Audigy 2 ZS driver issue - NO SOUND- after Windows 1903 update

Hi!

This worked for my Creative Audigy 2 ZS and Windows 10 1903 update:

https://extreme.pcgameshardware.de/windows-7-8-1-und-10-windows-allgemein/540331-win-10-update-1903-soundblaster-kein-ton.html?highlight=audigy

Download "Audigy RX Driver" from Creative

Extract all files

Go to the folder "Audio\DriversWin10\wdm"

Right-click "wdma_emu.inf" and select "install"

Restart and enjoy!

Best regards!

Markus

Thank you for this solution. It worked for me as well.

I think its insain that Microsoft pushed this build out when it breaks support for hardware that workes in previous builds.

Hi!

This worked for my Creative Audigy 2 ZS and Windows 10 1903 update:

https://extreme.pcgameshardware.de/windows-7-8-1-und-10-windows-allgemein/540331-win-10-update-1903-soundblaster-kein-ton.html?highlight=audigy

Download "Audigy RX Driver" from Creative

Extract all files

Go to the folder "Audio\DriversWin10\wdm"

Right-click "wdma_emu.inf" and select "install"

Restart and enjoy!

Best regards!

Markus

There are a few things I'd like to add your post, Markus, that may be of great help to you and others...

If you are doing a 'clean install' of Windows 10 1903, have the Audigy 2 card and get random BSODs or lock-ups; I think I found the culprit file. It is 'ha10kx2k.sys ver. 6.0.301.46. I think the file included with 1903 has a problem (but not the file included with creative's RX drivers ie: 6.0.301.56). Here are the steps I took to resolve:

1. I removed my Audigy 2 from my system and rebooted (I was locking up on the login screen).
2. I went in to \Windows\system32\Drivers and deleted ha10kx2k.sys (This may take safe-mode to accomplish).
3. I installed Daniel K's SB Audigy Series Support Pack 6.2 from https://danielkawakami.blogspot.com/2017/01/sb-audigy-series-support-pack-62.html
4. I then installed the Audigy RX driver as you suggested in your post.
5. Reboot.

I pulled my hair out trying to fix this. I think there is some sort of incompatibility with 1903 and ha10kx2k.sys. With either version (6.0.301.46 or 6.0.301.56) of the file, every time I attempt to uninstall either version, the system hits a BSOD. Dainel K's driver pack worked well with 1809 (which contains the 6.0.301.46 version of ha10kx2k.sys) MS needs to fix this!

P.S. It is curious to note that before the clean-install, Windows refused to update my system to 1903 from 1809 because it said my system was 'not ready' for the update. smh.

P.S.S. I tested installing the drivers using the setup contained within the RX DriverWin10 folder and it seems to work updating the drivers.

I updated to 1903 and lost all SB Audigy 2 functionality as well. I thought my card had died, it is fairly old after all (but I love it, hence the persistent struggle to get it back in working order...), but when booting into other OS's on the same machine it works just fine. 

Daniel K's "Support Pack 6.2" has worked for previous Windows 10 iterations until this point, but re-installing it now does not help anything. It does give me a device, reported as "Creative SB Audigy" as it's supposed to, which reports no problems in the device manager. Yet there is no sound whatsoever, and in the Windows audio settings most of the various things I'm used to seeing (all the various inputs, separate volume sliders for mic, line under the speaker tab etc) are gone. 

The big bunch of Creative software that comes with a full install of the the support pack don't do anything either.

After seeing this thread and a bunch of similar ones, I force-installed the newest official RX drivers (13 Sept, 2018) from Creative by unzipping the self-extracting archive with 7z (because if you just run it as-is it will extract and then try to run automatically but immediately give an error saying no supported device was found), browsing the resulting archive to the DriversWin10/wdm/ folder and installing the "wdma_emu.inf" manually. 

Voilá, all kinds of things happen here. The full range of Audigy audio settings that I'm used to seeing came back, and I do get sound...

...Well, sort of. I can now monitor the mic input directly, hearing myself, and both the mic- and general speaker sliders affect the volume. There is still absolutely no sound coming through from anything else (even though if you play for example music you see a visual indicator of fluctuating levels in the sound settings), and there's no change to that after numerous reboots and device enable/disable and what not. 

Curiously, when firing up one of the aforementioned pieces of Creative software that is bundled with Daniel K's support pack, I can now enable EAX and get some funky reverb, pitch and delay effects on the microphone monitor, and they all work fine. But clearly there is something in Windows that is somehow still blocking the card from outputting audio from any other sources, somehow. 

Haven't seen anyone else report on this particular issue as most people with SB issues post-1903 seem to have been fully helped by the RX driver install as detailed above. Just throwing this one out there in case anyone else has encountered this and perhaps even solved it. I will pop back in if I manage to figure this out on my own. 

EDIT just five minutes later: Well, apparently the "SPDIF Out" was muted and that was the culprit. Makes no sense to me whatsoever. Once I unmuted it, a pop-up said that the drivers had finished installing (though it obviously said that before too, so what gives?) and that a reboot was in order. Once rebooted, I heard all kinds of Windows sounds (I typically keep Windows quiet but I re-enabled all the sounds this time to get some kind of indication on whether or not things are working, without the hassle of going into the settings and testing, or playing some media file). 

Brilliant, I suppose that the muted "SPDIF Out" was somehow hindering a crucial component from installing properly. Re-muting it now has no effect on the sound.

Thanks a lot.

After I did this first it did not work. So I tried it again and again.

Even after faultless installing the RX-driver you maybe need to use the general troubleshooting of windows. This worked for me.