Daf,
I see your points, and certainly there are situations where rolling back the driver makes sense, especially if it causes a system-wide issue.
But in this case, PapidoFrance had the correct solution (simply uncheck the hardware acceleration option) yet SteveK not only kept insisting to roll back the driver, but I felt he became very condescending in the process, and I felt bad for FlyingPanMan.
I'll just back up my thinking with two points. First, if the new driver was indeed solving problems in other areas, say he was a gamer, then what do you do? That's why I felt rolling back should be a last resort, especially since the other, better solution had already been presented.
Second, it seemed as if SteveK was completely absolving Cyberlink from any culpability. Ok, if Nvidia's logo starts showing up on everyone's Microsoft Word Docs, doesn't it stand to reason people are going to be contacting Microsoft telling them to rewrite their code to block Nvidia from such nefarious activity? Or at the very least MS would be compelled to tell Nvidia to knock it off.
I think that is the same expectation people have of Cyberlink when a third party shows up and starts hacking around.
That's all I was trying to say, it's all good, thanks for chiming in!
Eric
Windows 10 64 Bit
ASUS Z87 Pro MB BIOS 2103
i7-4770K Haswell OC'd to 4.3Ghz
16GB Corsair Vengeance DDR 1600Mhz
EVGA Geforce GTX 960 2GB GDDR5 v368.22
Samsung SSD 840 Pro 256 GB (Rapid Mode)
Power Director 14 Ultimate 64 Bit