I use Vista Codecs, and I tried out the x64 components a while back. It didn't really work out as I had hoped, so after running the "set 32-bit media player as default" registry and icon several times, I uninstalled x64 components. However, my MKV files still *insist* on firing up 64-bit WMP 11. Even yanking MKV references out of the registry and trying to re-associate it with the 32-bit player, it just fires up the 64-bit player anyways.

How can I fix this?

VCP does not handle any file associations. I can attempt to teach you to use Windows though . . .

The only suggestion I can offer is to re-associate each format to WMP11 32bit by
manually browsing to the program files (x86) folder and selecting the 32bit executable for WMP11


shark

Your comment is cute, but I have tried re-associating it that way many, many times. Even immediately after associating it this way, it will launch the 64-bit player anyway.

This post has been edited by S.SubZero: Jul 21 2008, 04:12 PM

The comment was meant to be cute, sorry, but I had no other approach with which to respond.

I do not beleive VCP has anything to do with the issue you present especially since VCP does not create file associations, ever. It may have been caused by using some 'other' codecpack (Klite?) that is distributed to Vista users without proper testing within Vista's x64 environment.


shark

I have not used a different codec pack with this install.

I have attempted to reproduce the issue on Vista Ultimate x64.

I did as you stated. Set the x64 WMP as default, associated an MKV to it, checked to see that the x64 player was in use.
I then set WMP back to the 32bit default and I didnt even have to re-associate, MKV just started using the 32bit player.


shark

Try running the set 32-bit media player as default registry icons by right clicking and selecting run as admin.

This post has been edited by JamesG: Jul 24 2008, 06:34 PM

Post-mortem for this since I finally fixed it.

The key "HKEY_CLASSES_ROOT\Applications\wmplayer.exe" needed to have the "open" and "play" command subkeys set to the %programfiles(x86)% directory, as they continued to refer to %programfiles% and this is why it kept trying to load the 64-bit player. Once I corrected this, the problem went away.