Sound Blaster X-Fi Titanium HD not working properly in Windows 10 Insider build 18282

I was able to use this card with creative Daniel's K SB X-Fi Series Support Pack 4.0 drivers and the card and the associated creative software and drivers all worked flawlessly on the previous versions of insiders build.

After upgrading to the latest build 18282 I had no sound, drivers Creative SB X.Fi Audio it is INSTALLED inside Device Manager but Creative Control Panel says THERE ARE NO SUPPORTED AUDIO ...

Also tried install DISABLING INTEGRITY CHECKS not worked

Have you tried reinstalling the drivers? other thing you can do is remove the card reboot system go into device manager and uninstall it and under control panel delete any software that is for that device, reboot check that everything has been removed, turn system off reinstall the card and reboot system and let it install the drivers you may have to goto the makers site to get any software/drivers.
I'm a unpaid independent Advisor/volunteer

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanx but u didn't read, and clearly u dont know its' a big issue since win10 release for X-Fi owners, on Daniel's K worked but not now...


seems i need to roll back, when this happen it's the Insider Build fault, just roll back to previous version por wait next flight

https://answers.microsoft.com/en-us/insider/forum/all/windows-10-pro-insider-build-17738-no-soundblaster/f116ef1e-a5b2-4e91-85ce-c6eaa414609c

https://answers.microsoft.com/en-us/insider/forum/all/windows-insider-build-18252-removed-midi-support/909520b1-a178-4e53-9d52-b8ca91f98b19

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I did read and I guess you don't understand what happens with Preview builds when a newer build is sent out it may have changes in the core build which at times can cause issues with drivers/software until the developers can update the code to work with the newer core builds, but I guess I didn't read.
I'm a unpaid independent Advisor/volunteer

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

What's look strange it's that on Windows 10 Insider Preview Build 18277 (19H1) Daniel's K drivers were working as usual, same bug happened on 17074 and on later builds everything worked again. There arent any new modded drivers after SB X-Fi Series Support Pack 4.0 http://danielkawakami.blogspot.com/2017/01/sb-x-fi-series-support-pack-40.html

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Tried new Windows 10 Insider Preview build 18290 and SB X-Fi Series Support Pack 4.0 but STILL NOT WORKING!

Seems after 18xxx Windows seems x-fi drivers stopped working!

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Tried new Windows 10 Insider Preview build 18290 and SB X-Fi Series Support Pack 4.0 but STILL NOT WORKING!

Seems after 18xxx Windows seems x-fi drivers stopped working!

As would be expected with these Insider previews, this just happens. As the manufacturer of those drivers are not going to update their drivers for every Insider build as they are no where near any final code change. Just not worth the time, effort and cost to do this.

The only thing you can do is to report this issue in Feedback Hub so the MS engineers are aware of this, but the responsibility of drivers working with new code is up to the manufacturer. Take this up with SoundBlaster, and they will most likely inform you that they will not bother with any Insider builds till close to RTM when the windows code has been finalized.

You should not be running Insider builds on your main working, gaming system anyhow. If you must, consider dual-booting and running a Release build that these drivers do work on. Did you even read the Insider Agreement prior to joining the program.

https://insider.windows.com/en-gb/program-agreement/

Johnny

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated April 12, 2025 Views 942 Applies to: