Have you ensured your downloaded the Windows 7 64-bit version?
How fast is your processor, how much RAM do you have and how much free, clean, freshly defragmented space is on your C drive?
Have you gone manually to Windows Update and ensured you have even the non-critical updates (which sometimes includes important drivers)? Have you ensured you have the latest version of Quicktime?
I checked the system requirements before I purchased and I exceed all the requirements.
Intel 3.0GHZ core 2, 8gb RAM, over 200gb free clean defragmented space Windows 7 Pro 64
All the latest updates, Quicktime 7.7.3 and yes I have the 64bit version of PE 11
I have created a new profile and installed there with antivirus disabled, ran sfc /scannow, ran check disk and no errors.
Not sure what else to do.
Thanks for any help you can provide.
Me neither. Something is up with your computer, but it's hard to say what without actually sitting down at your computer and looking around.
You may need to contact Adobe Tech Support.
Okay, thanks anyway. It's been running fine for two years with no problems whatsoever and this is the first app I have issues with to this degree. I will repost if I figure it out beforehand.
One of the main causes of PrE to not launch is an obsolete video driver.
What is the make and model of your video card?
What is the date and version number of your installed video driver?
Is that the latest version, from the mfgr.? Do not trust Windows, or any utility to tell if you have the latest. You MUST go to the mfgr's. Web site, and check that for yourself.
One other cause of PrE not launching is VST's, usually from audio-editing software. See this article, if you DO already have the latest video driver: http://forums.adobe.com/message/3077222#3077222
Thank you for the inquiry. I am currently using an NVIDIA GEForce 9400GT and I have the latest drivers dated 10/2/12 which I manually downloaded and installed from their site. I had also rolled back to an earlier version just to make sure it wasn't the drivers. I will look into the VST issue described in your follow up reply.