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.

To share a big AVI clip with the forum, just upload it to a cloud service like OneDrive or DropBox and post the link. If you don't have any of those you can upload to this OneDrive *folder* on my account. It will take a long time to upload a big file, but any of these options will likely be faster than what you saw with the FTP site.

Thanks very much for the DxDiag results. I'm concerned about all the errors listed at the end, especially because this is a clean install. You've had serious crashes with AVG, several internal Windows processes (like WindowsUpdate) and something called DipAwayMode, which is apparently part of the ASUS utility suite.

None of these are good, and in combination they point to some serious problems with this installation. If I were you, I'd remove the ASUS suite and AVG, at least temporarily, then right-click on the Start menu and choose Windows command prompt (Admin) or Windows PowerShell (Admin), whichever one you've got showing will work.

Type in sfc /scannow and let Windows try to repair the problems it finds. You may need to run it several times before it can clean up all the problems, but there's also a chance that it won't be able to resolve everything on its own. If that's the case, I'd try Reset this PC (Start|Settings|Update & Security|Recovery) and let that finish. Then run sfc again and make sure it reports no errors, then try running PD13 and see how it behaves.

At that point, you should also download and install the latest Intel graphics driver. The latest release was Aug 12.

Repairing Windows may or may not have an impact on the AVI crashes, but it's definitely something you want to fix now. There's a newer Win10 build available (10525) if you sign up to be a Windows Insider (see my earlier post in this thread for details), and you might want to install that once you have a fundamentally sound setup with build 10240.

So, if you could send us a clip or two first, we could try it out on defferent machines and see if there's anything we can find to resolve it while you're working on the installation problems with Windows.

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°

Thanks again for the suggestions, optodata. I uninstalled the Asus AI Suite III and AVG Antivirus program but got the same error indications, and am thinking the DxDiag reports past issues as well as current ones. I performed the system scan before but I did it again just to make sure. As before, it showed no system errors (see attachment). I'm hesitant to try a beta build of Win10 at this point (to reduce the number of 'moving targets'), but I may if nothing else works. Regarding the video driver for my Asus Z97M Plus MoBo, the Asus site says I've got the most current Win10 driver installed now. When I downloaded the latest Win10 driver form the Intel site and tried to install it, the install apparently completed without errors, but after the mandated reboot, I see I had the same Asus-provided driver as before. When I ran the Intel tool, it said it couldn't find any Intel video drivers on the system, adding that MoBo manufacturers supply their users with Intel drivers under the Asus auspices and it may not show up on their tool (which it apparently didn't). I've never used OneDrive before, but I think I'm uploading a test AVI file now. Please let me know if you get it in your OneDrive. Regards, Rickblaine

If you saw the uploader start for OneDrive, then it should be working. I'm going to be away from my computer for a few hours and I'll check for your clip when I get back.

It is possible that all those DxDiag errors were from the past and they may not be there now, although running the sfc tool will still help.

Weird about the Intel driver. We can work on that down the road a bit if that looks like a promising option...



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: AIS you are not old I programmed assember with punch cards

Thanks but I also started in Basic and Advanced Assembler on Burroughs computers, then Fortran, Cobol etc and worked on IBM 1401s and 1440s and then on to IBM 360's and 370s. I started with offline 80 col punch card sorters and collaters and the first MICR check readers. So I am getting old, cynical, and grumpy with Bill Gates who did not develop DOS (but sold it to IBM) and stole his Graphical User Interface (GUI) from Steve Jobs (Apple) and has produced more user headaches in the form of Windows rubbish than anyone in computer history - and somehow became a multi-billionare in the process - so please pardon my lack of faith in yet another new Windows release. Operating systems should be transparent to end users as we have seen with Android which is Linux based. The "experts" claim Win 10 will be the greatest relase in Microsoft history due to the fact that users will have it on their cell phones, tablets, and PC's - but Windows cell phones have been declining in market share since their release. Linux (Unix based) has always been able to run on everything from Smart Phones thru to the latest IBM mainframes - and it's free! Now Microsoft have offered Android users Microsoft Office for free - but we Windows users still have to pay for it! Go figure.

I have a Samsung Android tablet still running on Android 4.1 and have never had an update but continue to download and update Apps without a single hiccup or virus to date - but my Win 8.1 desktop is still downloading up 100MB per week of security updates and fixes and I still have to pay for an AntiVirus plus Malware Bytes and still have problems!

Everyone now knows that when a new version of Windows is released you should wait intil the first Service Pack before trying it. Windows 10, in spite of Beta testing, has once again proven this is the case so I symphasize with software developers like Cyberlink and am simply suggesting users wait until Oct. for the first Win 10 Service Pack. Not "Rocket Science" - just common sense.

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

Looks like I've got some kindred, i.e., elderly, spirits here. I can remember when my Penn State instructors told us we should be thankful for Assembly language, because it was not so long ago that he had to program in 'machine language'. Punched cards were a way of life even when I worked aerospace for TRW in the early 70's. AIS, I should have known better than to think I could switch my primary machine to Win10 prior to SP1. I personally think Win7 was the best and most stable Windows Microsoft ever produced. As I said earlier, my Win7 machine runs EVERYTHING, even PWRD13. I can't say that for my WIN10 installation.

Sorry no offense intended!
I used to write programs in assembler and then debug in machine language on the console and finally output programs in machine language on punch cards. We had mag tape and hard disks as well. I remember Bill Gates once said "personal computers will never need more than 64k memory" - and they called him a visionary!
Windows 7 was the best release ever but I think it was due to their total disaster called Vista. I have pals who were so frustrated they went back to XP and stayed there!
Our PDR13 forum is the best I have come across with experienced users taking the time and effort to help newbies with problems and how to use PDR13 effectively and suggest product improvements. Non-Linear Video Editing is a complex field of it's own. I think our focus should still be on PDR13 and not on Win 10 problems - but that's just my old grumpy cynical opinion! 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

Quote: Everyone now knows that when a new version of Windows is released you should wait intil the first Service Pack before trying it.

OK, but if we all waited there'd be nobody reporting back on the problems and this thread would be pretty darn quiet [aka crickets]

rickblaine, I did get your 1.2GB AVI clip and so far it's playing perfectly fine - even in Full HD preview quality - in both PD12 and PD13 on my Win10 system. It's only 720x480 30i so it's not really challenging my hardware, and I've attached the MediaInfo report with more details.

With some of the problematic clips on Win10, the editor would crash or the clip would be reported as having an error once the scrubber reached a specific point in the timeline. Is anything like that happening on your end? If not, can you list the specific steps that reliably cause a crash or error message?

Depending on how you want to look at this, it's good news that your clips are able to be played on Win10 without any conversions; but it's bad (for now) because your system currently isn't able to.

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°

Point taken Optodata - maybe we should start a new forum called Win 10 Pioneers!
rickblane - you are correct. Converting AVI files is a pain - not a workaround - and every time you convert a vid file you lose some quality. Codecs like Cineform can do "near loss-less" conversions when used as intermediate codecs - but we don't have it yet - but we are working on it. 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

LOL. I just had to chuckle when you asked me if I could "list the specific steps that reliably cause a crash or error message", Optodata. No matter what I do I can reliably cause an error message. Seriously, though, I bring up a canned test case project that does nothing more than import the video file. I then go from Edit to Create Disk. I then click 'Burn in 2D' then select either 'Create a Folder' or 'Save as Disk Image' (the results are always the same: an error message stating:
Media Source Error Report :

Error type : Audio cut
Material type : Audio
Error information : Unknown
Material filename : F:\DEBUG\AVI Video Files Test Cases\Test Case 2\T77S-GarySchoolPlay26Jul15.avi
Detailed information : EC_ERRORABORT ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:6805
Debug information : EC_ERRORABORT ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:6805
I have to admit, I never get a program crash, just the error message. Sometimes it goes to 35%, sometimes to 50%, but it always produces the same type of error message.

Ah, so you're NOT seeing crashes in the timeline, they're only coming when you try to create a disc. THAT'S a big deal! Are you able to produce to any formats (like for YouTube) or have you only been trying to burn discs?

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°