
Actually, Cyberlink Tech Support jumped on the problem and invested at least 3 hours with a senior tech by remote control in trying to nail down the issue. I (an old systems hand) watched the proceedings and was impressed with the debugging tools and stepwise interrogative procedure used. In the end, they didn't have a solution for it

but did jointly determine with me that the problem arises from conflict with the particular mix of graphics libraries and codecs installed on my O/S platform. In particular, there is a likelihood that the conflict stems from program components loaded by Corel VideoStudio X4, but a further investment of hours was in neither of our futures. Is VideoStudio a program that you happen to have on your machine too?
I give Cyberlink credit for the effort to ferret out the issue, which can be very complex in a Windows environment with so much 3rd party software installed.