Yes, very frustrating! FWIW, I tried again using just one monitor connected to my system board (nothing was connected to my GTX card), and I could not see the hidden monitor until I also disabled my nVidia card.

With that disabled, I was able to select, extend, duplicate etc. with no problems, so something else seems to be interfering on your system.



I've noticed that new Win10 drivers are coming out every single day now, and it's probably worth re-checking for driver updates for your motherboard chipset and even BIOS/UEFI - even if you just checked a couple days ago. You can do that via Window Update or manually at the vendor's website or even from the Update Driver button in Device Manager.

Good luck!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Thank you all for the input, i'll keep checking things, if i get it working i'll come back to share the info. Thanks again

AlexanderBSV - Able to conform your findings that the video works properly on a window 7 pc but not on this pc : http://www.bestbuy.com/site/hp-envy-2-in-1-15-6-touch-screen-laptop-intel-core-i7-12gb-memory-1tb-hard-drive-natural-silver-black/3008123.p?id=1219567192721& with the OS upgraded to windows 10. The avi video freezes at 2 min. 37 sec. Have to close the installed PD12.

Quote: PowerDirector 13 Editors,

***************************
If you've missed the info, please check out News and Announcements Forum: Windows 10 Compatibility Advisor - Check If Your CyberLink Software is Ready For Windows 10!

***************************

Following a request from AlS, please add your issues under this one W10 heading and maybe see if we can get something done.

Recent threads/issues:
https://forum.cyberlink.com/forum/posts/list/44354.page
https://forum.cyberlink.com/forum/posts/list/44596.page
https://forum.cyberlink.com/forum/posts/list/44577.page

Dafydd

All INTEL Graphics users please note that this may not be a Cyberlink problem - and please re-think Win10 upgrade

Inetl has acknowledged that Win 10 users are experiencing problems with the latest Intel HD Graphics drivers released for Win 10. They are working on the problem and will release new drivers soon - this includes the 4600 GPU which PDR13 Win 10 users have reported problems.

Please see my post above of 08/08/2015 - "A word of caution." It is just not possible for any "compatability checker" to test everything. Don't be in a hurry to switch to Windows 10 - and if you have already, remember you have ONE Month to roll back to 7 or 8.1. Quote "If it works - don't fix it!" We have a year to upgrade free. AVI files are also working fine on 8.1.

Intel Support - I installed Windows 10. Intel HD graphics 4000 driver (latest from June 2015) is not accepted by Windows 10. What's wrong? (see post no. 14 from Intel and 15)

YahooTech - 8 Reasons Not to Upgrade to Windows 10

Infoworld - Win 10 Bugs

"Windows 10, Threshold 2, due to debut in October. Instead of new features, we’re getting plumbing fixes and a passel of patches. Threshold 2 (I think of it as “Service Pack 1” ) could bring a host of new features, many of which were painfully missing from the RTM (er, 10240) build on July 29."

Also Win 10 causing multi-monitor problems

ForbesTech -Windows 10 Automatic Updates Start Causing Problems

So, if you can, hold off till Oct for Threshold2.

For those stuck on Win 10 here is a way to stop forced updates. Things like graphics drivers are not always the latest or best from Microsoft so most users will want to control graphics updates.

ForbesTech - Microsoft Backtracks On Windows 10 Forced Updates


For those who hate the Win 8.1 Start Menu GUI you don't have to jump to Win 10

How to Get the Real Start Menu Back in Windows 8 or 8.1

Give Cyberlink and Microsoft a little time to iron out the wrinkles - I would even suggest that Win 10 users refer problems to Cyber Support and let this forum stay focused on PDR13 - but maybe I'm getting old and grumpy

Al Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer

Excellent info AlS. I've returned this thread to a "sticky" where I shouldn't have removed it from. Ooops,
sorry about that.
Dafydd

When I play back the AVI clip in:
Movies & TV - without errors,
Windows Media Player - without errors,
VirtualDub - without errors,
Format Factory - without errors,
XviD4PSP - without errors,
but when I use PD13, I get the error. Therefore this Cyberlink problem.

Quote: I'm glad that the converted clip works. Until a patch is released, I think that is the best solution for clips that cause errors on Win10 systems

Can you confirm then that with the latest build update, converting the file to mp4 will be a good work around for the error we are getting? Will there be any quality loss by converting to mp4 from AVI?

Quote: All INTEL Graphics users please note that this may not be a Cyberlink problem - and please re-think Win10 upgrade

Intel has acknowledged that Win 10 users are experiencing problems with the latest Intel HD Graphics drivers released for Win 10. They are working on the problem and will release new drivers soon - this includes the 4600 GPU which PDR13 Win 10 users have reported problems. Al

Al, your words of caution and your research on the subject are valuable. It's clear that there are some "birthing" pains with the Intel drivers, but the media problems that AlexanderBSV and Felbourn reported also appear on my machine, and we are using nVidia GPUs. There are other users, like christophrrb who's system ONLY works with the newer Intel drivers, so it's a pretty mixed bag.

I liked your earlier comment about the pioneers, and I agree that people should decide to upgrade to Win10 whenever they're comfortable. In a couple more weeks (not months, even) I'd expect that the upgrade path will be much smoother and you'd probably see fewer Win10-related posts on the forum.

Quote:

Quote: I'm glad that the converted clip works. Until a patch is released, I think that is the best solution for clips that cause errors on Win10 systems

Can you confirm then that with the latest build update, converting the file to mp4 will be a good work around for the error we are getting? Will there be any quality loss by converting to mp4 from AVI?

Please download the clip that AlexanderBSV linked to and also my conversion (they're the 2nd and 3rd posts on page 2) and play them in a regular player (not PD13, or the first clip will crash!) You can judge the conversion quality for yourself, and there are many free or low-cost conversion apps out there that you can experiment with on your clips. I'm confident that you'll be able to get very high quality results to work with in PD13.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Optodata
Hi - thanks for the info. In my Forbes Tech link above on multi-monitor problems it says


"Dreadful Drivers - The flaw revolves around Nvidia graphics cards with users taking to Nvidia’s forums to report Windows Update is automatically installing new drivers which break multimonitor setups, SLI (dual card) configurations and can even stop PCs booting entirely which pushes Windows 10 into its emergency recovery mode.
The problem is compounded by the fact that Windows Update doesn’t actually reveal driver version numbers prior to install or warn the user in advance so pinpointing something that has suddenly caused problems can be hard to identify."

I'm not suggesting that is your problem, nor that it's definitely Win 10 and not PDR13 which we know has Nvidia driver problems in 8.1.

My point is simply this -
I have had the unfortunate experience of every new Windows release since DOS - in true pioneering spirit! The most stable new release was Win 7 following the Vista disaster. We are only weeks into Win 10 and general consensus is that, unlike Win 7, Microsoft was premature in their release of Win 10.
Worse still, it appears that they have held back the release of commercial versions of Win 10 expecting "free" Home users to sort out the bugs and compatibility issues - so we are really still doing Beta testing for them.

Here is another link - Windows 10 Review Roundup: High Scores, Big Bugs

There are no real advantages of moving to Win 10 yet. The core is very similar to 8.1, performance about the same, and the biggest marketing attraction is the new GUI which most Win 8,1 users like me have sorted out. It will improve and things like Direct X 12 look promising for gamers.

This obviously also makes life tough for software developers like Cyberlink.

This is not my opinion, but I do agree with the experts. It will probably be the best Windows release ever due to it's cross platform compatibility allowing you to do the same things on your smartphone, tablet, and desktop - BUT NOT YET!

It has taken me (and Cyberlink) a year to have a stable system on Win 8.1 and I'm still being annoyed by Microsoft daily by automatically download Win 10 and trying to force me to upgrade. The real problem is that 30 days later Win 10 become irreversable - and even the "roll back" doesn't always work!

So if you want to avoid the "arrows", stay away from "Bleeding Edge" technology and wait for the next major release in Oct(?) and the transition should be much easier.

Al Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer

Thanks, Al. Lots of useful info! I agree that the autodownload is a problem and hopefully MS will be rethinking that.

FWIW I've been on PCs since the DOS, Novell NetWare and Windows 2.03 days; and to be honest, the effort that MS put into getting pre-beta Win10 releases out to millions of "Windows Insiders" was a really big deal. The engineering team listened to the feedback and I can attest that the released GUI is much better, familiar and more refined than the original plans

Some of the early builds were nowhere near ready for distribution, but I've been running Win10 on an original Surface Pro since March and the final build (10240) came out to us Insiders in mid-July. Since I'd had no problems on my Surface with the final two builds, I was excited to get Win10 on my other machines.

However, I upgraded 3 other PCs on 7/29 and while 2 went perfectly, my main desktop/editing system didn't fare as well and I ended up doing a clean install and reinstalling all my apps. Not great, but it's running very nicely now. So even with one hiccup/imperfect upgrade, I'm still at 4 for 4.

They've just released build *10525* to the "Fast ring" for Insiders, and I'm eager to try it out and see what changes they've made.

I know, I know. Another opportunity for arrows, but also an opportunity to see if the the AVI media errors issues have been resolved...

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote: Thanks, Al. Lots of useful info! I agree that the autodownload is a problem and hopefully MS will be rethinking that.

Referal to DOS reveals something about our ages I would probably also try Win 10 on a Surface Pro but I have lost my desktop pioneering spirit!

You can stop forced AutoUpdate in my link above Microsoft Backtracks On Windows 10 Forced Updates

Good Luck - Al Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer

Great link. Thanks!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I just wanted to quickly post that I've re-tested AlexanderBSV's AVI clip with the new 10525 Win10 build, and the crash is still present.

I believe that the fix for this issue will need to come from Cyberlink. For now, pre-converting any clips that give media errors on Win10 systems still seems like the best work-around.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

So far so good.

Ran several projects previously done with Win 7 and all is well. Win 10, i7

OK. Windows 10 is a confirmed problem for PD13 !

In Win 7 the preview window was able to keep up to normal editing functions up to FULL HD preview resolution with some instances where I had to step down to HD preview resolution mode. PD13 cannot keep it up at those settings in Win 10. The best I can now do is High preview resolution and that is frequently bogged down at times.

Time to re-code folks ! Win 10, i7

Quote: OK. Windows 10 is a confirmed problem for PD13 !

In Win 7 the preview window was able to keep up to normal editing functions up to FULL HD preview resolution with some instances where I had to step down to HD preview resolution mode. PD13 cannot keep it up at those settings in Win 10. The best I can now do is High preview resolution and that is frequently bogged down at times.

Time to re-code folks !

I haven't noticed a difference in preview capability. What format are your source clips in, and what kind of effects/transitions/adjustments are in your project?

It's possible that some specific combination of those in your project is slower in Win10 than with Win7, and it would be nice to have more info to see if we can isolate which ones are problematic. I typically use 1080/60p MTS sources.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Since W10 has installed all my videos show a green screen when playing back. Sound it ok but there are no images. Cyberlink support has been pretty power. Can anyone help or advice me on how to resolve? Thanks

Quote: A word of caution:

I may be getting old and losing my "pioneering spirit" but I have been through every Windows release since DOS and have had some rough times - the worst being XP to Vista and then Vista to Win 7.
General consensus is that Microsoft may have rushed things a bit and that 8.1 users should wait a few months until patches fix driver compatibility issues etc.
Also for those having issues with Win 10 and PDR13 you have ONE MONTH from upgrading to roll back to 7 or 8.1.
It took me long enough to have a stable PDR13 under 8.1 but now issues may with Win 10 and not Cyberlink.

We have a year to take advantage of the free upgrade and in reality, Win 10 benchmarks are slightly slower than 8.1. I have a 3rd party Win 7 type Start Menu so I intend leave it to the Pioneers for a while and focus on PDR13.
Al

I was a member of the beta team for over a year and a half on Win10. For me all of the Cyberlink products worked flawlessly with Win7. A few weeks ago I reported an issue to technical support while using PD13. It was sluggish and rendering of a 15 minute video would take over 1 hour.

Other than ensuring the correct video driver is installed there are a some Win7 functions to fine tune. Indexing will slow your computer or device to a crawl and use plenty of memory. Turn off indexing or set up a schedule for it. Defender is another one to set up under task scheduler. As it is Defender will decide to run on it's own when you begin processing a video.

Nvidia says they worked with MS to develop a perfect set of drivers. However, MS built a new, I will say, plug and play set of universal drivers. This was quite an issue in the MS IT forums for users. CUDA would not work with both sets installed. Hidden in the changlog of Nvidia there is a contradiction. Nvidia states the newest drivers do not support series 600, 700, 800 video cards. With their latest set of drivers for Win10 the line is missing from the changelog file. It remains on their website.

In order to do a test all of the Nvidia drivers were removed. The MS drivers worked without any errors. The CPU and all of the components were recognized by Win10. Since I do not play online games the Nvidia experience is not required for me. I would not suggest you remove the Nvidia drivers if you are not having problems. Many of the Nvidia add ons are not required and they take resources away from PD13. As another long time user of Windows, I suggest to every Win10 user to do some homework, so you can safely turn off some non-essential services. Problems with MP4, AVI and others is caused by a clash of decoders and encoders installed on a computer or device.

The moderator and other users here are offering instructions to assist you. The MS forums for Win10 are also an excellent source of information. AIS mentions the pioneering spirit. It does exist and is based on sharing ideas to help others. AIS you are not old I programmed assember with punch cards

I'm getting extremely frustrated with Cyberlink's PowerDirector 13 support (so-called). Today I inquired what the status of my problem's 'escalation'. I reminded them that PWRD13 runs fine on my Win7 HD, but when I clone that HD and immediately upgrade to Win10, I get failures on AVI files that worked flawlessly in the Win7 environment. The response I get is the same one the offered before: just convert your avi's to some other format. This is not a workable fix because I have TONS of avi's (that work fine under Win7) and don't feel I should have to convert them, and (2) Does not answer why they don't work in my Win 10 environment. The only difference in the two systems is the OS's and Win10 driver updates made as part of the OS switch. Is anyone else out there getting the same 'canned' responses to real questions? Sorry for the rant, but I'm getting no help from Cyberlink, which is holding up my actual switchover to Win10.

rickblaine, I've now seen many of your posts and can completely understand your frustration. I didn't see anywhere that you posted the DxDiag file for your machine and it would be great to see it - either here or on the thread you started. I know you did a clean install of Win10, but sometimes something will show up in the results that makes a difference.

Also it would really help to have a copy of one of the clips that is giving you problems. Again, I understand that you're not willing to convert all your clips to upgrade to Win10, and if we have an actual sample perhaps we can find an updated driver or codec that resolves the problem.

I also saw that you had trouble running MediaInfo. What you saw when you installed it is normal, but you then have to actually launch the program to configure it to display the info when you right-click on a clip. Just start typing mediainfo in the new "Search the web and Windows" box and click on the suggestion at the top when it appears.

There's still hope!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Thanks for the words of encouragement, Optodata, but it's difficult to be optomistic given the support I've been provided so far by Cyberlink. I'm attaching the DXDIAG report I regenerated this morning. I sent one to the Cyberlink guy that requested it early on, but I got no comment on it. I'm not sure how to provide the AVI files. They are quite long and it even took a while to upload them to Cyberlink's FTP site. I sent 5 test case AVI files along with the resulting error messages, and got NO feedback on them from Cyberlink. The problem, I'm certain, isn't with a single AVI file because I can't find any of the 10 or so I tried with the Win10 HD that did not generate a premature error message. As I said, all of them worked fine on the Win7/PWRD13 HD. As a retired computer professional, it appears to me that there's a problem with the interface between the Win10 system software (including video adaptor driver) and PowerDirector 13, but I can't seem to get Cyberlink to investigate that angle. The AVI files, by the way, play well outside of PWRD13, so I believe PWRD13 is involved in the problem. Again, thanks for the words of encouragement.