Hi Carl,

I can see where you are coming from, but the SSD isn't the problem as the Temp folder is located in
\Users\[Userprofile]\AppData\Local\Temp
or this case
D:\Users\[Userprofile]\AppData\Local\Temp
which is the 1TB hard drive and not the solid state.

All of the PowerDirector working folders are contained on the 1TB hard drive - only the actual application is installed on the SSD.

If that makes sense...

I hope it works that way.

I have never had success with setting temporary files anywhere except on the OS drive.

Powerdirector will do strange things if it does not have enough temporary file space.

If you are using Windows 7 you can use 'Resource Monitor' to watch the execution of Powerdirector while it is working.
Resource Monitor will display the use of Memory, Disk, CPU and Network.

Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

Just to update you. I did a lot of testing yesterday and it looks like when you install Windows using Audit Mode and you script it to locate
C:\ProgramData -> D:\ProgramData
C:\Users -> D:\Users
it creates problems which causes PowerDirector 11 to crash when loading. It also stops Adobe Premier Elements 11 to crash when loading the installer file.

However, if you use the Audit Mode and only configure it as follows:
C:\Users -> D:\Users

And leave C:\ProgramData there, it is fine and works brilliantly.

I then created a Symbolic Link (mklink /J c:\Users d:\Users) on C:\ to point to D:\Users so any program which hard codes location of Users instead of the %USERPROFILE% variable, will still end up on D:\Users.

It means all of the workspace used will not be the SSD drive, but my 1TB hard drive instead. Yes, pain having ProgramData on the C Drive, but I don't think it will take up a lot of space there.

Anyway, this morning before work I installed Windows 8 Pro using the above method and... ALL IS WORKING NOW

So the problem has been resolved!

Final Thoughts:

Either PowerDirector 11 doesn't like ProgramData being on another drive (even if using the official Microsoft way of doing it ie on install of the OS) or Quicktime doesn't like that method. Using my above approach resolves this problem and still ensures that all the working directories are not on the SSD which will shorten it's lifespan - only the program files are on that to make it fast at launching.

Very good information.

I am glad you solved your launching problem.

Powerdirector is very picky about when it puts temporary files. By redirecting the files in Windows you avoid the problem of Powerdirector writing to another location.

I am bookmarking this post.

Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

Yesterday I formatted and reinstalled Windows on my test pc at work soooo many times to test where it fails, so I am pretty confident that the above should fix people's problems

Hi James,
Thanks for the feedback. I have passed on your input to CyberLink. Good to know you finally resolved the issue. Well done.
Dafydd

Can somebody please explain the above fix to me? I know a lot about computers, but I'm having troubles following what is being said in the fix.

I'm having problems after reinstalling Windows to an SSD. After installation, I moved the Windows temporary files to my 750 GB HDD as well as reduced the page file size and some other tweaks. Now, PD crashes everytime I try to use the Create a Disc function. There is about 20 GB left on my 128 GB SSD that is reserved for mostly programs.

Thanks to anyone.

Quote: Can somebody please explain the above fix to me? I know a lot about computers, but I'm having troubles following what is being said in the fix.

I'm having problems after reinstalling Windows to an SSD. After installation, I moved the Windows temporary files to my 750 GB HDD as well as reduced the page file size and some other tweaks. Now, PD crashes everytime I try to use the Create a Disc function. There is about 20 GB left on my 128 GB SSD that is reserved for mostly programs.

Thanks to anyone.

The final conclusion was that a Tweak of the Windows 7 operation System caused problems with Powerdirector operations.
Moral of story, do not tweak Windows 7.

Also the part about SSD drives not having enough space is serious. Powerdirector needs up to about 100 GB of free space on the OS drive to render AVCHD video and create BluRay disks. Do not attempt to move the Windows Temporary Files location.

Minimum specs for Powerdirector 11 Ultra:
http://www.cyberlink.com/products/powerdirector-ultra/specs_en_US.html

Look at the Hard Disk Section.

Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

I agree with Carl about not moving Windows Temporary Files location after Windows has been installed.

However, when you install Windows, you can use Audit Mode to install it before it actually creates the Users folder.

I would NOT move the ProgramData folder to a location that isn't on the OS drive - that was where my problem was.

This is the guide for Windows 7:
http://www.sevenforums.com/tutorials/124198-user-profiles-create-move-during-windows-7-installation.html


It covers the official Microsoft way of moving those files.

It is technical, but works. As I said, do NOT move the ProgramData folder though. Either PD11 hates it being moved, or Quicktime does.

Once you install Windows 7 using that guide, PD11 works fine (so do all the other apps).

I then change it so the pagefile.sys file is located on my 1TB HD.

I also then created a symbolic link on the C drive (SSD) to point to the D drive where Users is now stored

mklink /J c:\Users d:\Users

This basically forces any program that hard codes C: \Users into their install script, to actually write it to D: \Users.



Using this method, it means that when PowerDirector 11 starts, it loads the program off of the SSD, but all working files and folders ie your videos etc are actually loaded from the normal HDD instead.
The Temp folder is also located on the D: drive too.

Obviously, Cyberlink don't support this method, but it does work - and works very well once I figured it out

I have 68GB free on my SSD and 770GB free on my 1TB drive.

I fixed this problem on my computer! I found this forum by the error message "Cyberlink CLQTKERNELCLIENT32 Has stopped working" which I was getting after installing PowerDirector 11 Ultra. After reading posts saying QuickTime needs to be removed, I did that using the Windows 7 control panel, but it did not work. I tried running the Cyberlink cleaner and re-installing PowerDirector, and that did not work either. As an experiment I tried downloading the latest QuickTime from http://www.apple.com/quicktime/download/. When I ran the QuickTime installer, it first asked me if I want to remove QuickTime from my system. I clicked on remove. That worked!

Good call Thurston.. The obvious solution..

I hate to say it guys. BUT 99% of the information in this thread is pointless and nothing more than guessing and random shots in the dark.

VERY time consuming shots in the dark too for anyone who tries to follow it. Not to mention that its telling the average person to do things they should not be messing with. I feel awful for the original poster who installed PD like 5 times. The only reason he actually solved the problem is because his quick time was updated with win8 and he doesn't even know it.

In the interest of customer service and accurate information the whole thing(thread) should be deleted except for Thurston's post. The rest is just leading people on an insanely time consuming wild goose chase that has no relevance to the problem. .

Quote: Good call Thurston.. The obvious solution..

I hate to say it guys. BUT 99% of the information in this thread is pointless and nothing more than guessing and random shots in the dark.

VERY time consuming shots in the dark too for anyone who tries to follow it. Not to mention that its telling the average person to do things they should not be messing with. I feel awful for the original poster who installed PD like 5 times. The only reason he actually solved the problem is because his quick time was updated with win8 and he doesn't even know it.

In the interest of customer service and accurate information the whole thing(thread) should be deleted except for Thurston's post. The rest is just leading people on an insanely time consuming wild goose chase that has no relevance to the problem. .

Actually, my problem was nothing to do with Windows 8. I replicated it in Windows 7 too. The problem is when working with SSD and SATA drives and doing a custom install of Windows where you relocate (at install) Program Files AND Users folders to a seperate hard drive and not the default SSD drive.

I've worked in IT for 16 years - not your average Joe Blogs. I have access to lots of test environments and spent a long time testing the install and linked it to PD not liking Program Files being in a non-standard location

True yet you did do everything correctly. Your issue was quicktime. I also am a certified Microsoft systems engineer and administrator. This was not your problem.

But your up and running none the less. So that's good. But its new "consumer oriented" users that shouldn't be trying such impressive feats with the OS. a quitetime update generally will fix this in 2 minutes.

lol it wasn't quicktime. I had the latest installed

I also did an install of PD without Quicktime, downloaded it from apples site and tried again.

When I installed this system, I did exactly what I did before, but only moved the Users folder, and all was fine with the DEFAULT Quicktime that came with PD

Yes, some situations QT would fix the issue, but not this one

You hafto do the install with quicktime. Then update quicktime. This I've experienced on 3 seperate 64 bit systems of my own. As well as with 2 small production studios I work closely with. Thats all I can say is that an update fixed it eveytime on my end. And most likely would fix others.

*edited to correct my sloppy phone generated typo's

Sorry didn't have too much time earlier,

But just to offer some more information to those who are having the “simple” version of this issue.

One can trouble shoot it easily.

Typically it seems to stem from a corrupt install of “apple application support” (or some component of).
When I said “install PD with quick time”. And then “update” quick time. What I meant is actually install the full boat PD including QuickTime. Then go to apple, download the latest QuickTime install and allow it to “remove” the previous install and reinstall itself entirely (repair/modify will not work to solve the issue), where by reinstalling “apple application support”. I assume one could likely skip the PD QuickTime installation and just do their own QT installation after but this I have not specifically done.

So.

**To reproduce the issue on a PD installation that’s not experiencing the problem (assuming QuickTime was installed) one can go into the control panel and uninstall “apple application support” and you should receive the error from that point forward when starting PD.

If one is already suffering from the issue its easy to confirm the source of the problem by going to the control panel to see if “apple applications support” is installed. If not then there's your problem. If it is installed then uninstalling QuickTime completely should at least allow PD to start without error. This too will confirm the issue.

If that’s the case then you simply reinstall QuickTime in its entirety allowing it to remove the initial installation first.

This for me is 100% percent reproducible on windows 7 64 bit systems. (although I am not certain windows 7 or the fact that it’s a 64 bit system are relevant to the issue).

Im inclined to think that the QT install included with download version of PD is possibly corrupt and/or mildly damaged.. Either that or the qt install included with PD is just outdated and not handled well by 64 bit systems. I have not checked that personally. I have only solved the issue then moved on.

I myself am getting an error message "Cyberlink CLQTKernellClient32 has stopped working" and tried mybest everything to remove the problem , but nothing works. Searched google and found Cyberlink forums... came here and looking at all the threads and seeing the misery the Cyberlink customers are going through is ridicoulus. I mean the professionals haven't got a clue about the exact cause of the problem and are proposing one solution after another and the custumers have no option but to try whatever they say and in the end everyone says that the problem is still there. Its a circus ... I am giving up and going out of this SOLUTION room right now.... best of luck to all the sufferers including me....

Cyberlink get your act together , build a nice software and then sell it in the market... don't sell rubbish which is more irritating , time wasting and productivity reducing ( Just the opposite of what we install it for ). Thanks for wasting our days....

Quote: I myself am getting an error message "Cyberlink CLQTKernellClient32 has stopped working" and tried mybest everything to remove the problem , but nothing works. Searched google and found Cyberlink forums... came here and looking at all the threads and seeing the misery the Cyberlink customers are going through is ridicoulus. I mean the professionals haven't got a clue about the exact cause of the problem and are proposing one solution after another and the custumers have no option but to try whatever they say and in the end everyone says that the problem is still there. Its a circus ... I am giving up and going out of this SOLUTION room right now.... best of luck to all the sufferers including me....

Cyberlink get your act together , build a nice software and then sell it in the market... don't sell rubbish which is more irritating , time wasting and productivity reducing ( Just the opposite of what we install it for ). Thanks for wasting our days....

Other post removed from http://forum.cyberlink.com/forum/posts/list/15/27878.page :

Quote: I myself am getting an error message "Cyberlink CLQTKernellClient32 has stopped working" and tried mybest everything to remove the problem , but nothing works. Searched google and found Cyberlink forums... came here and looking at all the threads and seeing the misery the Cyberlink customers are going through is ridicoulus. I mean the professionals haven't got a clue about the exact cause of the problem and are proposing one solution after another and the custumers have no option but to try whatever they say and in the end everyone says that the problem is still there. Its a circus ... I am giving up and going out of this SOLUTION room right now.... best of luck to all the sufferers including me....

I had this error message a while back when I installed PDR11 onto a clean system, running W8. I did the QT update and the issue wasn't fixed. I then uninstalled PDR11 and reinstalled. The issue was fixed for me.

Sardar Abdullah, The members here answer issues and provide solutions. Had you posted your issue as a new topic, giving your diagnostic data you may have been helped. If you opt to add a new post then members will have the opportunity to answer you. For a novice, error messages can be scary. Most issues can be fixed, you just have to work through how members guide you.

Thread locked.

Forum Moderator

New topic link: http://forum.cyberlink.com/forum/jforum.page?module=posts&action=insert&forum_id=110
Version used and Diagnostic data: Part A, B: http://forum.cyberlink.com/forum/posts/list/24771.page
Guide for Sardar Abdullah to read: http://forum.cyberlink.com/forum/posts/list/24769.page