1. Microsoft® Windows XP SP1, Windows 2000 SP3, Windows Millennium Edition or Windows 98 Second Edition. Creative Sound Blaster Audigy 2 or Audigy 2 ZS series audio card (with.
2. Creative Sound Blaster Audigy2 ZS SB0350 5.1 Channels 24-bit 192KHz PCI Interface Sound Card (318. Driver Disk Audigy 2 ZS Internal I/O Drive. Warranty, Returns, And Additional Information. It isn't recognized by Windows 10 at all, and the drivers from Sound Blaster are completely useless.

• Creative Audigy 2 Sb0350 Driver Windows 10

Creative Audigy 2 Sb0350 Driver Windows 10

I have an Audigy EAX-HD Sound Blaster Model SB0160 on PCI slots.

Today, I upgraded the Computer to Windows 10 version 1803 (from version 1709) and although the drivers are installed correctly, the sound does not come out of the speakers and even the 'Creative Audio Console' control software no longer works with the following error 'Can not find the audio device '.

In particular, if I make the test from the 'Audio' window in the 'Playback' tab, you can clearly see to the right of the device description that the level rises (the little green bars) as if the device were producing audio, but actually in the speakers or any other listening device like a simple headset will not hear ANYTHING. Chocolatey for windows.

Download the latest version of Creative SB Audigy 2 ZS (WDM) drivers according to your computer's operating system. Creative SB Audigy 2 ZS (WDM) Drivers Download for Windows 10, 8, 7, XP, Vista Driver Guide.

I uninstalled the drivers; I tried different versions of drivers; I have formatted the computer completely using the boot-dvd; I have updated from version 1709 to version 1803 with drivers already installed; i tried also last unofficial version of drivers;

However, the problem remains.

It is not a problem of sound card or other hardware, because on Windows 10 version 1709 and any PREVIOUS version of Windows 10, 8 (8.1), Seven, Vista, XP the sound worked perfectly including the 'Creative Audio Console' control panel.

It is ridiculous that having this same Operating System and same developed source code has created this serious problem, for PRIMARY AUDIO CARD in this my computer.

Considering that you are discussing with a technician, I am open to ANY 'software advice' to solve the problem here, why I'm not going to buy another sound card for this stupid bug.