Hi Dominique,
I feel a bit slighted, as, if you had followed my suggestion, you would have found this out for yourself. Let me explain, as as it may be useful to you some time in the future (I am an ex-Windows Systems Developer, so have a little idea of what I am talking about, though even I get tripped up sometimes by the simplest of things).
Anyway... :-
If you had done a safe boot, the K-lite codec pack DLLs would not have been loaded. You would have found that PD9 was fine, and then following the selective loading procedure, you should have found that it was the KLCP.
Safe booting is the key to finding most interference problems. The binary selective loading procedure would identify one out of 32 loaded services in a maximum of 5 boots. Not a heavy price to pay when you are 99% sure of getting the answer... and probably taking a lot less time than the frustrating things you did have to do.
Note that the problem was not a Cyberlink problem, it was a problem out of their control, but they actually went out of their way to find it. Pretty good for a bunch who normally get a lot of stick.
You will possibly find that uninstalling the KLCP will mean some other file format will give you trouble later. FWIW, I have the KLCP loaded with no evidence (SO FAR) of any problems like yours, but it maybe that mine is a later or different version.
Denbigh - aka SeptimusFry, living and breathing in Cotes d'Armor since 2004.
i7 980x; W7 Pro; 12GB; Nvidia GTX 285; 2x300G Velociraptors in Raid 0; 2x1.5TB Barracuda in Raid 1; 2TB WD Studio Ed.II (eSATA); NEC SpectraView Reference 2690 + MultiSync EA232