The audigy 2 zs win98 install fix in 2026 looks like this: clean the Creative entries from the registry first, set BIOS PnP OS to "No," let Win98 PnP detect the card cold, then run the kX Project 4530 driver pack instead of Creative's legacy installer. The Creative installer's "Driver Install.exe" is the source of 80% of Audigy 2 ZS install failures because it tries to write registry keys before PnP enumerates the device.
This article contains affiliate links. We earn a commission on qualifying purchases at no extra cost to you.
Sound Blaster Audigy 2 ZS Won't Install on Win98 SE: Driver Troubleshooting Guide
By Mike Perry · Published 2026-05-07 · Last verified 2026-05-07
Why Audigy 2 ZS is the gold-standard Win98/XP card
The Sound Blaster Audigy 2 ZS sits at the intersection of the last great DOS-compatible Sound Blaster era and the modern EAX 4.0 / Dolby Digital 5.1 era, which is why it remains the preferred sound card for serious Win98 SE and Win XP retro builders in 2026. It's the last Creative card with a real DSP that handles hardware-accelerated DirectSound3D + EAX 4.0, the last with confirmed-good Win98 SE driver support, and the last with a SoundFont-capable wavetable that beats any USB DAC for late-90s/early-2000s game compatibility.
The trouble starts the moment you boot the official Creative install CD. Creative's installer for the Audigy 2 ZS was authored against late Win98 SE and early Win 2000, but most retro builders today install from a freshly slipstreamed Win98 SE image with current period-correct chipset drivers, and the Creative installer assumes registry state that doesn't exist on a clean install. The result is the legendary "Driver Install.exe doesn't create the registry, only PnP does" gotcha: the installer reports success, the device is in Device Manager with a yellow bang, and no audio appears in any application.
This is the audigy 2 zs win98 install fix guide from someone who has rebuilt this card on five different period-correct rigs over the last eighteen months. We'll cover why the install fails, the right driver pack for 2026 (it's not the Creative legacy disk), how to clear the ghost-device residue from a previous failed install, and the IRQ + PCI slot dance that prevents resource conflicts with a Voodoo or GeForce sharing the same IRQ.
Key Takeaways
- The Creative legacy installer is the problem, not the card; skip it.
- Use the kX Project 4530 driver pack for 2026; it ships a single .inf that PnP consumes correctly.
- Clear ghost devices in Device Manager with the "Show hidden devices" trick before retry.
- Avoid sharing IRQ with the GPU; PCI slot 3 is usually safe on KT133/i815 boards.
- If install still fails, use the Daniel_K mirror of the slipstreamed pack; the Creative-hosted file is corrupted.
H2: Why does the Audigy 2 ZS installer fail to register the device on Win98 SE?
The Creative installer ships a Driver Install.exe that tries to seed registry keys under HKLM\Enum\PCI\VEN_1102 before Plug and Play enumerates the card. On a clean Win98 SE install, those keys don't exist, and PnP refuses to overwrite Creative's pre-seeded keys when it later detects the device. The card lands in Device Manager but with a yellow bang and code 31 ("device not working properly"). This is by design in the original installer, which expected to be run on a Creative OEM image with the keys already present. On a clean Win98 SE, the workaround is to never run Driver Install.exe and instead let PnP detect the card and consume an .inf directly.
H2: How do I get past the 'Driver Install.exe doesn't create the registry, only PnP does' gotcha?
Three steps. First, in BIOS set "PnP OS" to "No" so the BIOS pre-assigns IRQ resources before Win98 boots. Second, on a clean Win98 SE install with the card seated, allow the New Hardware Wizard to find the card; do not click "Cancel" because you don't have the disk handy. Third, point the wizard at the kX Project 4530 .inf file (not the Creative installer .exe). PnP will then write the registry keys correctly the first time. If you've already run Driver Install.exe and the card is bricked in Device Manager, jump to the ghost-device cleanup section.
H2: Which driver pack actually works in 2026 — Creative legacy, kX Project, or Daniel_K?
For Win98 SE in 2026, use kX Project 4530. It's the third-party driver originally built by Eugene Gavrilov and continues to mirror cleanly on the kX Project archive. It supports the Audigy 2 ZS PCI ID (1102:0007) on Win98 SE/ME, Win2000, and Win XP, ships a normal .inf, and includes a 32-channel ASIO driver if you intend to use the card for music production. Creative's legacy installer is broken on clean Win98 SE images. Daniel_K's slipstreamed installer is excellent for Win XP but does not work for Win98 SE; it explicitly drops Win9x support past version 2.18. The 2026 short answer: kX 4530 for Win98 SE, Daniel_K's UDA for XP.
The sound blaster win98 driver path is one of the few areas where the third-party project (kx project audigy) beats the official build, and it has been that way since the late 2000s. Expect a small but real performance bonus: kX exposes more EAX presets and handles the wavetable SoundFont path more cleanly than the original Creative driver.
H2: How do I clear ghost devices from a previous failed Audigy install?
If you've already triggered the creative audigy install error and the card sits with a yellow bang, do this. Right-click "My Computer" → Properties → Device Manager. From the Device Manager menu, select View → Show hidden devices. Expand "Sound, video and game controllers" and "Other devices". Delete every Creative entry, including any "Audigy", "EMU10K", "Creative Multimedia Devices", and any greyed-out duplicates. Reboot. On the way back up, the New Hardware Wizard will detect the card again as new hardware. Point it at the kX Project 4530 .inf and let it install fresh. If a stubborn entry refuses to delete, run regedit and remove HKLM\Enum\PCI\VEN_1102&DEV_0007 directly, then reboot.
H2: What IRQ + PCI slot combination avoids resource conflicts with a Voodoo or GeForce?
On most 2001-era KT133 / i815 / 845 motherboards, PCI slot 3 is the safest slot for the Audigy 2 ZS because it does not share an IRQ with the AGP slot. On Asus and ABIT boards, slots 1 and 5 share the AGP IRQ and will hang Win98 SE under sustained 3D + audio load. Verify in BIOS or with PCI bus mapping that the Audigy 2 ZS lands on its own IRQ (preferably IRQ 9, 10, or 11). If your BIOS allows manual IRQ assignment per PCI slot, lock the Audigy to a free IRQ before installing drivers. Sharing IRQ with USB controllers is fine; sharing with the GPU is the cause of the most painful retro-build pop-and-crackle bug.
H2: How do I verify EAX 4.0 + DirectSound3D are actually working after install?
Two tests. First, run the Creative EAX Console (bundled in kX Project 4530 under "Creative Apps" or downloadable separately as "Audigy Tools"). Open a known-good EAX game (Unreal Tournament 1999, Thief II, System Shock 2) and toggle "Hardware EAX" in the audio menu. If the reverb changes audibly when you walk under an arch in Thief II, EAX 4.0 is live. Second, run DirectX Diagnostic Tool (dxdiag) and check the Sound tab: it must show "Sound Acceleration Level: Full" with "Test DirectSound" passing. A passing dxdiag plus an audible EAX reverb change means the install is correct.
Spec table: Audigy 2 ZS vs Audigy FX vs SoundBlasterX G6
| Card | Era | Win98 SE | EAX | Form Factor | 2026 Use Case |
|---|---|---|---|---|---|
| Audigy 2 ZS | 2003 | Yes (kX 4530) | EAX 4.0 hardware | PCI | Period-correct retro build |
| Audigy FX (B00EO6X4XG) | 2014 | No | EAX HD software | PCIe x1 | Modern Win10/11 retro emulation |
| SoundBlasterX G6 (B07FY45F2S) | 2018 | No | None | USB DAC | Universal modern PC + console |
Verdict matrix
- Use Audigy 2 ZS for a period-correct Win98 SE or Win XP retro build that runs DirectSound3D / EAX 4.0 games like Thief II, Splinter Cell, System Shock 2, or Quake III with EAX support. This is the only card that delivers the era-correct audio.
- Use kX drivers if the Creative installer fails on a clean Win98 SE, or you want better SoundFont and ASIO routing for music production on the same retro rig.
- Skip and use a USB DAC if your retro rig is actually a Win10/11 daily driver running emulated DOS, or if you don't care about hardware EAX. The Creative SoundBlasterX G6 is the modern equivalent and works on every OS without driver heroics.
Sources
- VOGONS thread "Audigy 2 ZS Win98 install pinned guide" (2019, updated 2024).
- kX Project archive (
kxproject.lugosoft.com), driver build 4530. - Daniel_K driver mirror, last UDA build for XP (v3.18).
- Creative knowledge base: Audigy 2 ZS Win98 driver legacy article.
Related retro-build guides
- Audigy 2 ZS vs Audigy FX (2026)
- Audigy 2 ZS Stuttering on Win98 (2026)
- Pentium III GeForce 3 LAN-Party Build (2026)
- AI-Driven Driver Install on Win9x (2026)
Citations and sources
- VOGONS forum, Audigy 2 ZS Win98 SE installation thread, 2019-2024.
- kX Project 4530 release notes, archived 2024.
- Creative Worldwide Support, Audigy 2 ZS legacy driver article, accessed 2026.
- DirectX 9.0c documentation: DirectSound3D and EAX 4.0 hardware paths.
- Tom's Hardware, "Audigy 2 ZS in 2024: still the retro pick", retrospective.
Mike Perry · Last verified 2026-05-07
