Possible issue with Vista's default codecs

Zenoth

Diamond Member
Jan 29, 2005
5,202
216
106
I'll try to make this short.

I installed Vista some time ago, and I never tried any third-party codecs installation programs, so after I installed Vista all the codecs in the OS were the default ones. Then, eventually (and because I was experiencing strange sound-related issues in Sacred 2, and because someone suggested me to try that) I tried a codec pack named Vista Codec Package (simply), the program's icon is a shark with a pair sunglass if it tells anything to you guys (it seems to be a popular download anyway). So after some time I decided to uninstall it (because I was still having the same sound-related issues, so I thought that the new codecs didn't helped), and it uninstalled without problems.

Then, more recently, and after experiencing the same sound-related problems (and after posting about it on several occasions) I had been told that the "best" codec package to try is the K-Lite Codec Pack. So I tried that, and I installed one of the pre-set options, since I didn't know what I was doing, so I let the program do it, it installed automatically and all was working fine after the installation. However it would be interesting to note that just before the installation finished the installer popped-up a warning window in which it said that it detected broken codecs, and that to fix them it was suggested to delete their respective registry entries, so I accepted, and it deleted two such entries. But I still got the sound problem I referred to earlier, so I again decided to uninstall that K-Lite pack, and so it uninstalled without problems.

After I uninstalled it I decided to run CCleaner's registry cleaning tool, and it detected more than sixty erroneous entries, which I let CCleaner fix. Then I restarted the system. After that I went on Google and made some research about programs which would be able (if any) to tell me if my default Vista codecs were alright to start with right after I installed the OS itself and before installing any third party codecs packs. I found no such programs capable of telling me just that under the conditions I wanted, but I did find a program capable of telling me if the current codecs I have (if they're default to the OS or not is not detected by the program, and that's what I wanted to know, but I least it's capable of telling me about the currently present ones, default or not) are working fine or are "broken".

That program is Codec Sniper, but it's supposedly old, and was designed to detect codecs and their status under Windows XP, so I don't know if the information given under Vista is actually relevant and precise. But anyway, I tried it, and it shows that a good number of my codecs are "broken" (what "broken" codecs mean exactly I'm not sure, can they be "fixed"? I don't know, do I just have to re-register them? I don't know, it just says it's "broken"). That's the result I have when I run it right now.

Now I have questions:

1) Is the information given by that old program actually good?
2) Is there a way to test those exact codecs and know for sure if they're indeed "broken"?
3) If they are indeed broken, can they be repaired? And if so, how?

Thanks.
 

VinDSL

Diamond Member
Apr 11, 2006
4,869
1
81
www.lenon.com
Originally posted by: Zenoth
I'll try to make this short.

I installed Vista some time ago, and I never tried any third-party codecs installation programs, so after I installed Vista all the codecs in the OS were the default ones. Then, eventually (and because I was experiencing strange sound-related issues in Sacred 2, and because someone suggested me to try that) I tried a codec pack named Vista Codec Package (simply), the program's icon is a shark with a pair sunglass if it tells anything to you guys (it seems to be a popular download anyway). So after some time I decided to uninstall it (because I was still having the same sound-related issues, so I thought that the new codecs didn't helped), and it uninstalled without problems.

Then, more recently, and after experiencing the same sound-related problems (and after posting about it on several occasions) I had been told that the "best" codec package to try is the K-Lite Codec Pack. So I tried that, and I installed one of the pre-set options, since I didn't know what I was doing, so I let the program do it, it installed automatically and all was working fine after the installation. However it would be interesting to note that just before the installation finished the installer popped-up a warning window in which it said that it detected broken codecs, and that to fix them it was suggested to delete their respective registry entries, so I accepted, and it deleted two such entries. But I still got the sound problem I referred to earlier, so I again decided to uninstall that K-Lite pack, and so it uninstalled without problems.

After I uninstalled it I decided to run CCleaner's registry cleaning tool, and it detected more than sixty erroneous entries, which I let CCleaner fix. Then I restarted the system. After that I went on Google and made some research about programs which would be able (if any) to tell me if my default Vista codecs were alright to start with right after I installed the OS itself and before installing any third party codecs packs. I found no such programs capable of telling me just that under the conditions I wanted, but I did find a program capable of telling me if the current codecs I have (if they're default to the OS or not is not detected by the program, and that's what I wanted to know, but I least it's capable of telling me about the currently present ones, default or not) are working fine or are "broken".

That program is Codec Sniper, but it's supposedly old, and was designed to detect codecs and their status under Windows XP, so I don't know if the information given under Vista is actually relevant and precise. But anyway, I tried it, and it shows that a good number of my codecs are "broken" (what "broken" codecs mean exactly I'm not sure, can they be "fixed"? I don't know, do I just have to re-register them? I don't know, it just says it's "broken"). That's the result I have when I run it right now.

Now I have questions:

1) Is the information given by that old program actually good?
2) Is there a way to test those exact codecs and know for sure if they're indeed "broken"?
3) If they are indeed broken, can they be repaired? And if so, how?

Thanks.
LoL! Short huh? :D

Here's short for you...

I run the CCCP codec package in Windows OSs - end of codec problem(s):

http://cccp-project.net/

And, Crap Cleaner is the best too - never had a problem with it! If you got a problem with CC - that ain't the problem!
 

Zenoth

Diamond Member
Jan 29, 2005
5,202
216
106
Ah, indeed, you should see some of my "longer" posts out there, hehe. Well, the thing is I don't know which codecs are installed with the OS by default, I've Googled just that for a few hours and the only things I found were codecs packages to download. I'm very surprised to see that there's apparently no official information directly from Microsoft or reliable sources to tell us about such information (which codecs come with the OS, and if there's ways to repair or replace them if they ever become corrupted or damaged).

You're suggesting me to download a codecs package and that's exactly what I don't want to do until I figure out what's wrong with the supposedly "broken" codecs I currently have. When I fix them (or if there's anything to fix at all) then I will consider downloading another codecs package, but to repeat myself I won't do that until I find the information I need concerning my current issues with my codecs.
 

Mem

Lifer
Apr 23, 2000
21,476
13
81
Originally posted by: Zenoth
I'll try to make this short.

Then, eventually (and because I was experiencing strange sound-related issues in Sacred 2, and because someone suggested me to try that)


I've Sacred 2 on Vista x64 runs fine sound wise,I'm guessing its not a codec issue but maybe a sound driver issue?..Are you using onboard sound or your x-fi?... try updating the drivers etc..

Keep your DX9.0c updated too even in Vista link. .

Btw I use K-Lite (4.93 is latest) full version Codec pack,never had any issues over the years.


 

VinDSL

Diamond Member
Apr 11, 2006
4,869
1
81
www.lenon.com
Originally posted by: Zenoth
You're suggesting me to download a codecs package and that's exactly what I don't want to do until I figure out what's wrong with the supposedly "broken" codecs I currently have. When I fix them (or if there's anything to fix at all) then I will consider downloading another codecs package...
I see.

Hrm...

Have you tried GSpot yet???

EDIT I should have kept reading - see the post above this one. :D

The only 'bad' thing about GSpot is it doesn't (necessarily) tell you if an installed codec is "broken"...

EDIT2 Just thinking...

Did this "broken" codec thing happen after a recent Windows Update, by any chance?

Supposedly, the latest ActiveX update breaks codecs in Vista! ;)
 

VinDSL

Diamond Member
Apr 11, 2006
4,869
1
81
www.lenon.com
Originally posted by: tzdk
You could try InstalledCodec http://www.nirsoft.net/utils/installed_codec.html see company name and it can disable.
Interesting!

I'm glad I clicked on that link... ;)

Locations In the Registry

InstalledCodec extracts the information from 2 places in the Registry:

The Codec drivers list is loaded from:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
The DirectShow filters list is loaded from:
  • HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance
 

Zenoth

Diamond Member
Jan 29, 2005
5,202
216
106
Ok, I've tried GSpot, and it lists 90 codecs, none of which are red, and that program has been tested on Vista, so I think that it's quite possible that Codec Sniper is erroneously listing broken codecs simply because it's an old program which was never tested with Vista, and I'm thinking that it just cannot find the proper codecs paths in the registry or in the HDD and that it thinks they are broken, while in fact there's nothing broken.

As for Sacred 2 what I have done was to physically remove my X-Fi card, then uninstall the drivers (the latest WHQL ones), and then re-installed them again (the same ones) and then placed the card back, and then I tested and so far there's no more issues, basically what happened was that on some occasions some of the battle speeches of my character were delivered in very slow motion with a very low voice tone. I never experienced any other sound-related issues in any of my other games however, it was just Sacred 2. If the problem was codec-related then perhaps I would have had problems in more than just one game.

Anyhow, now the problem is fixed, and my codecs seem to be healthy according to GSpot (hopefully that one is right). I wish Microsoft would develop an official tool capable of detecting the default OS codecs and telling what's their status, if they're broken or not, that would be tremendously appreciated... but I know I'm dreaming in colors here.