1803 August update broke creative sound card panel

0091/2

Well-known member
After updating to the lastest patch I found the sound blaster control panel no longer works.
"Input file or data stream does not conform to the expected file format specification."
Anyone here with a creative sound blaster Z has this issue?
:mad: I can't switch to my headphones now.
 
Last edited:
Everything works for me, but windows insists on putting a preview up of whatever is on the screen at random times. This isn't me initiating anything. This is a windowed preview 50% the size of the screen that sometimes goes away by clicking in a blank area, and other times it doesn't budge for a minute or two.

Who in the heck at MS thought it a good idea to randomly show me what's already right in front of me in a separate window? Gotta figure out how to disable this crap.
 
Everything works for me, but windows insists on putting a preview up of whatever is on the screen at random times. This isn't me initiating anything. This is a windowed preview 50% the size of the screen that sometimes goes away by clicking in a blank area, and other times it doesn't budge for a minute or two.

Who in the heck at MS thought it a good idea to randomly show me what's already right in front of me in a separate window? Gotta figure out how to disable this crap.

I haven't that happen to me. Windows 10 app window can be buggy sometimes. I've had windows resize or disappear out the border by itself.

Any how I fixed it. The font "segoeuii.ttf" got corrupt after the update.
This did the trick. I had to reboot first before doing it.
https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker
 
Weirdness like this is why I don't upgrade to the newer feature updates. I coast along for as long as I can (and skip at least one version entirely), and then I do a clean install of the current version when it gets to the point that I basically have no choice but to upgrade. I'm currently on 1709, and will be skipping 1803 entirely (just like I did with 1703). I hope to be able to hold out until 1903, but that's probably asking a bit much considering how aggressive MS can be.

I don't care if OS upgrades today are 1000x better than they were back in the day-- there's always a chance for extra weird stuff to happen when you install over the top. And Windows 10 is bad enough as it is just having to deal with it fresh out of the box without upgrading. :bleh:
 
Weirdness like this is why I don't upgrade to the newer feature updates. I coast along for as long as I can (and skip at least one version entirely), and then I do a clean install of the current version when it gets to the point that I basically have no choice but to upgrade. I'm currently on 1709, and will be skipping 1803 entirely (just like I did with 1703). I hope to be able to hold out until 1903, but that's probably asking a bit much considering how aggressive MS can be.

I don't care if OS upgrades today are 1000x better than they were back in the day-- there's always a chance for extra weird stuff to happen when you install over the top. And Windows 10 is bad enough as it is just having to deal with it fresh out of the box without upgrading. :bleh:

The new update patches a new Intel vulnerability. I only update because of security patches. I don't think anyone should leave their systems unpatched. If you don't bank on your PC then you don't really have to worry about vulnerabilities.:bleh:
 
I haven't that happen to me. Windows 10 app window can be buggy sometimes. I've had windows resize or disappear out the border by itself.

Any how I fixed it. The font "segoeuii.ttf" got corrupt after the update.
This did the trick. I had to reboot first before doing it.
https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker

Thanks for this - it's still doing it lol. I guess I'm due for a clean install anyway. I guess I ought to count myself fortunate. This is really the only noticeable bug through all the upgrades.
 
Thanks for this - it's still doing it lol. I guess I'm due for a clean install anyway. I guess I ought to count myself fortunate. This is really the only noticeable bug through all the upgrades.

Instead of clean install try making a new user account. It doesn't hurt to try it. :bleh:
 
The new update patches a new Intel vulnerability. I only update because of security patches. I don't think anyone should leave their systems unpatched. If you don't bank on your PC then you don't really have to worry about vulnerabilities.:bleh:

Sorry... I probably could've worded that last post a little better. I only avoid the twice-a-year "feature updates" as much as I can, not the regular monthly updates (i.e., Patch Tuesdays). Each version of Win10 (1703, 1709, 1803, etc.) is supported for at least 18 months after it's released-- even after it's been replaced by a newer version.

Actually, I did hold off on the July 2018 cumulative updates because there were reports that they were causing all sorts of havoc out of the gate, but I am currently up-to-date with v1709 as of this month (16299.611).
 
Microsoft's drivers always break my creative card. I'm forced to reinstall the older creative drivers again every time.
 
Back
Top