Premiere Elements 12 on Win8.1 x64 isn't starting

Hi,
I'm using Win8.1, x64. After slecting new project for Premiere Elements 12 I just get the waiting bar and nothing more.
I already activated DirectPlay in the windows features.
What do i have to do to get it working ?
Thx so much,
Dirk77
<moved by mod from downloading,installing, setting up - kglad>

From the Premiere Elements Information FAQ http://forums.adobe.com/thread/1042180
•Have you installed any recent program or OS updates? (If not, you should. They fix a lot of problems.)
•What kind(s) of image file(s)? When talking about camera raw files, include the model of camera.
•If you are getting error message(s), what is the full text of the error message(s)?
•What were you doing when the problem occurred?
•What other software are you running?
•Tell us about your computer hardware. How much RAM is installed? How much free space is on your system (C:) drive?
•Has this ever worked before? If so, do you recall any changes you made to Premiere Elements, such as adding Plug-ins, brushes, etc.? Did you make any changes to your system, such as updating hardware, printers or drivers; or installing/uninstalling any programs?
And some other questions...
•What are you editing, and does your video have a red line over it BEFORE you do any work?
•Have you viewed the tutorial links at http://forums.adobe.com/thread/1275830 page?
•Which version of Quicktime do you have installed?
What is your exact brand/model graphics adapter (ATI or nVidia or ???)
What is your exact graphics adapter driver version?
Have you gone to the vendor web site to check for a newer driver?
For Windows, do NOT rely on Windows Update to have current driver information
-you need to go direct to the vendor web site and check updates for yourself
ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

Similar Messages

I am on my mac and have os x yosemite. i am trying to install adobe premiere elements 10, but every time it starts downloading it stops and says it encounter 8 errors?

i am on my mac and have os x yosemite. i am trying to install adobe premiere elements 10, but every time it starts downloading it stops and says it encounter 8 errors?

you mean when it starts installing (not downloading), you see errors?
if yes, attach a screenshot of the errors.

Premiere Elements 10 64 bit won't start

My issue:
When I try to start Adobe Premiere Elements 10 64 bit the program will start to launch and then windows will announce "Adobe Premiere Elements 10 has stopped working"
My System:
HP Elitebook 8540w
Intel i7 M640 CPU
8GB Ram
64bit operating system
Nvidia Quadro FX 880M
I have tried: (I'll try to remember everything)
Uninstalling/Reinstalling
Restarting after every uninstall mentioned in the I have tried section
Uninstalling antivirus
Stopping all programs and unneccessary services I could find
Updating video and sound card drivers to the latest version
Updated to latest version of Quicktime 7.71.80.42
Clean up hard drive and temp files
Uninstalled NVidea 3D Driver, PhysX System, nview and HD Audio Driver, leaving only the primary display driver
Checked event viewer looking for any logged issues. It always fails on display.dll. Details below
Faulting application name: Adobe Premiere Elements.exe, version: 10.0.0.0, time stamp: 0x4e791009
Faulting module name: Display.dll, version: 6.0.0.0, time stamp: 0x4e78fee0
Exception code: 0xc0000005
Fault offset: 0x00000000000230bc
Faulting process id: 0x874
Faulting application start time: 0x01ccaba6fa61d433
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Elements 10\Adobe Premiere Elements.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Elements 10\Display.dll
Report Id: 3c543fc1-179a-11e1-ad00-68b599f767d3
Any ideas?

The error message seems to be pointing the finger at your display drivers. You say:
MMerck wrote:
Updating video and sound card drivers to the latest version
Uninstalled NVidea 3D Driver, PhysX System, nview and HD Audio Driver, leaving only the primary display driver
Are these the mobile drivers from the nvidia site or from HP? Whichever ones they were, try the other. It's also possible that your windows updates applied a graphics driver update - that's usually a bad thing. Always get the drivers from HP or nvidia.
Cheers,
Neale
Insanity is hereditary, you get it from your children

[..\..Src\DirectoryRegistry.cpp-283] error when starting Premiere Elements

This error only happens when the laptop is disconnected from our domain. When trying to start Elements I receive error:
Premiere Elements 8.0 has encountered an error.
[..\..Src\DirectoryRegistry.cpp-283]
Then program will not start unless I connect the laptop to the network - which makes a portable laptop useless.
I have uninstalled and re-installed the program with the exact same results.
Anyone got any dieas?
Thankyou in advance.
Crash log file has been included
<?xml version="1.0"?> <!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown"> <time year="2009" month="11" day="19" hour="11" minute="51" second="20"/> <user guid="323c9019-64a6-4b68-8502-a51259f444ab"/> <system platform="windows" osversion="5.1.2600 SP 3.0" applicationlanguage="English (United States)" userlanguage="en_AU" oslanguage="en_AU" ram="2035" machine="Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" model="x86 Family 6 Model 23 Stepping 10" cpuCount="2" cpuFreq="2394 MHz" busFreq="" locale="English (Australia)"/> <crash exception="EXCEPTION_BREAKPOINT" instruction="0x0097df10"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x0097df10" symbolname="dvacore::debug::DVA_DebugBreak"/> <stackStatement index="1" address="0x00a0123a" symbolname="dvacore::utility::ThreadSafeMessageDialog"/> </thread> </backtrace> <registerSet> <register name="EAX" value="0x00000000"/> <register name="EBX" value="0x00000000"/> <register name="ECX" value="0x00000000"/> <register name="EDX" value="0x00000000"/> <register name="ESI" value="0x00a0103e"/> <register name="EDI" value="0x00000000"/> <register name="ESP" value="0x00000010"/> <register name="EBP" value="0x00000008"/> <register name="EIP" value="0x00000000"/> <register name="EFL" value="0x00000246"/> </registerSet> <binaryImageSet> <binaryImage start="0x00400000" end="0x00519000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements 8.0.exe"/> <binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/> <binaryImage start="0x7c800000" end="0x7c8f6000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/> <binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6001 .22319_x-ww_f0b4c2df\GdiPlus.dll"/> <binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/> <binaryImage start="0x7e410000" end="0x7e4a1000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/> <binaryImage start="0x77f10000" end="0x77f59000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/> <binaryImage start="0x774e0000" end="0x7761d000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/> <binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/> <binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/> <binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/> <binaryImage start="0x77a80000" end="0x77b15000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/> <binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/> <binaryImage start="0x773d0000" end="0x774d3000" type="__TEXT" path="C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_ 6.0.2600.5512_x-ww_35d4ce83\comctl32.dll"/> <binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/> <binaryImage start="0x10000000" end="0x1013c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/> <binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcp80.dll"/> <binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcr80.dll"/> <binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/> <binaryImage start="0x00350000" end="0x00361000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/> <binaryImage start="0x00370000" end="0x003f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/> <binaryImage start="0x7c9c0000" end="0x7d1d7000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/> <binaryImage start="0x00530000" end="0x005d3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/> <binaryImage start="0x771b0000" end="0x7725a000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/> <binaryImage start="0x77120000" end="0x771ab000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/> <binaryImage start="0x005f0000" end="0x008fb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/> <binaryImage start="0x5b860000" end="0x5b8b5000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/> <binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/> <binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/> <binaryImage start="0x4d4f0000" end="0x4d549000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/> <binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/> <binaryImage start="0x00910000" end="0x0091f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/> <binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/> <binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/> <binaryImage start="0x00930000" end="0x0093f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/> <binaryImage start="0x00950000" end="0x00aa4000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/> <binaryImage start="0x00ac0000" end="0x00b4c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/> <binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/> <binaryImage start="0x00b60000" end="0x00b66000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/> <binaryImage start="0x00b80000" end="0x00b96000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/> <binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/> <binaryImage start="0x74720000" end="0x7476c000" type="__TEXT" path="C:\WINDOWS\system32\MSCTF.dll"/> <binaryImage start="0x01a20000" end="0x01abd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/> <binaryImage start="0x01ee0000" end="0x01f17000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/> <binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/> <binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/> <binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/> <binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/> <binaryImage start="0x01f30000" end="0x01f50000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/> <binaryImage start="0x01f60000" end="0x01f6b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\WS.en_US.DLL"/> <binaryImage start="0x02080000" end="0x02103000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeUpdater.dll"/> <binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/> <binaryImage start="0x605d0000" end="0x605d9000" type="__TEXT" path="C:\WINDOWS\system32\mslbui.dll"/> </binaryImageSet> </crash> <reproSteps> </reproSteps> </crashreport>

Where, and how, is PrE installed? When you launch it, are you running as an Administrator?
First, PrE wants to be installed competely on the C:\ and wants direct access to the My Documents folder. It also wants to be both installed and then launched from an Administrator account.
It is not designed (nor is the big-brother PrPro) to function in a fully networked environment. It will extract media, etc. from an NAS, or from a mapped networked drive, but it does not like to run under most networked environments.
It's my guess that there is something in this installation that it is not comfortable with. More details will likely help.
Good luck, and looking for the answers to the questions above.
Hunt

I click on the Adobe Premiere Elements icon and it doesn't do anything, How do I fix that?

I am trying to open my Premiere Elements 12 and it isn't responding. How do i fix this?

z00mz00mgirl
What computer operating system is your Premiere Elements 12 running on?
Have you ever opened the program and created a project with it? In other words, is this a "it worked before but not now" or "it never worked before" issue?
1. Determine if the problem exists with and without the antivirus and firewall(s) disabled.
2. Right click the desktop icon, then from the drop down menu, select, click on, apply Run As Administrator.
3. Do you have the latest version of QuickTime installed on the computer with Premiere Elements?
4. Have you installed and are running the program in a User Account with Administrative Privileges?
Let us start here and then decide what next.
Thanks.
ATR

How to burn my Video to a DVD in Premiere Elements 7?

I have a
video of my son's Basketball team and I save it
on my Hard Drive thru Premiere Elements.I did make it a
project. I now want to burn it onto a DVD and don't want
anything more such as timelines and or screen lines.
Can someone step me thru the process?
Thank You

THEVIDEOKID
We have a lot of details to sort through systematically to get your the DVD-VIDEO that you want, but let us try some preliminary questions and answers to get started:
a. The file that you clicked on to open your video in the Premiere Elements 7 Timeline...did it have a file extension of .prel? That is the file extension of a Premiere Elements project.
b. When you started that project, did you set it up for NTSC DV Standard or Widescreen or the PAL counterpart?
c. If you are working with the project.prel, when you open the project.prel, do you see your video on the Timeline? Does it play back in the Edit Mode Monitor if you hit the Play button of the Edit Mode Monitor?
d. When you get to Share/Disc/Disc, what preset did you set...NTSC Standard or Widescreen or the PAL counterpart?
e. After you have hit Burn in the Burn Dialog and during the encoding burn, the image in the Monitor stays at the image where you left the Timeline indicator back in the Edit Mode....nothing changes there, except maybe the image will dim during the encoding/burning process.
f. IMPORTANT...do you get a message saying the the burn to disc has been successfully completed, followed by the DVD burner tray opening?
g. If so, put the DVD back in the burner tray, go to My Computer/DVD drive. Right click the DVD drive and select Explore. Do you find content of two folders, one named OpenDVD and the other VIDEO_TS?
Where are you trying to play back the DVD-VIDEO that you believe that you created?
ATR

Premiere Elements 4 auto analyze off

Help. I tried to install Premiere Elements 9 on my old Vista machine and got the dreaded error 1935 CE3230AC-E72E-3EDF-8A57-87FCE1CF2629 HRESULT: 0x80071A30. Searching for help, I came to the conclusion that it is a registry cash screwed up and reinstalling Vista is really the only way. So I went back, reinstalled Premiere Elements 4 and came here for help with: Auto Analyze, scene detect seems to be on and I can't turn it off??? Capturing video from DV leaves me with 100 files instead of the 1 I want. Impossible to find help/support for PE4. Anyone know now to turn this make many files on capture off????
Tom Pears tpearsATaol.com

Hello Steve
I have attached a couple screen shots. Let me know if you have any trouble seeing, I can always post them to another location.
You say
You can launch the Elements Organizer from the Premiere Elements Welcome screen when you first start the program.
I have attached the welcome screen where I see no way to launch Ele organizer. What am I missing? The top menu items are all unaccessable.
You say
The option to break scenes by content is on the the Capture screen, which opens when you select the DV Capture option under the Get Media button under the Premiere Elements Edit tab.
I can find no such option except one grayed out under clip back at the project screen. Again I have attached a couple screen shots to show you what I see.
There must be something obvious that I am missing or that is different about my APE4 instance.
Happy Sunday
3.
Steve Grisetti
Feb 15, 2013 5:16 AM in reply to tompears
Report
In order to turn off the background Auto Analyzer, you need to be in the Elements Organizer program. Not Premiere Elements. You can launch the Elements Organizer from the Premiere Elements Welcome screen when you first start the program.
The option to break scenes by content is on the the Capture screen, which opens when you select the DV Capture option under the Get Media button under the Premiere Elements Edit tab. This will only affect how the program performs with freshly captured DV video, of course.
Was this helpful? Yes No
Tom Pears
Applying Appropriate Technology to Education

I am unable to open premiere elements 11 PDapp.exe (0xc0150002)

Also I had to reinstall Adobe aplication manager, I reintall the hole program too. and do not work

Adryah
Thanks for the follow up information.
The first thing that is of concern is the 2 GB of installed RAM. But, that should be enough to get at least Premiere Elements 7 installed.
When you started the reinstall of the program, did you do so with the antivirus and firewall(s) disabled? The typical scheme would be
a. uninstall (Control Panel route)
b. ccleaner run through (regular cleaner and registry cleaner parts)
c. reinstall with antivirus and firewall(s) disabled.
What was your source for the Adobe Application Manager? Have you confirmed that your Premiere Elements 7 is installed or not via its presence or absence in Control Panel/Programs?
Please explore
Local Disk C
Program Files (x86)
Common Files
Adobe
then in the Adobe Folder is the OOBE Folder. Rename the OOBE Folder from OOBE to OLDOOBE.
Does the issue disappear?
We could also look at deleting the Adobe Premiere Elements Prefs file and the whole 7.0 Folder in which the Adobe Premiere Elements Prefs file exists.
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
7.0
and in the 7.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 7.0 Folder in which it exists.
Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
Please review and consider and then we will decide what next accordingly.
Thank you.
ATR

Premiere Elements 8.0 crashes

I just downloaded the 30 days trial version of Premiere Elements 8.0.
The program starts with the welcome screen.
After pressing the button 'new project', the program loads a lot of stuff and crashes every time while trying
to load "sytrus vsti.dll".
Sytrus is a plugin for FL Studio, but i've never installed FL studio or sytrus on my computer
Any ideas, how to start premiere?
THANKS!

Sytrus is a plugin for FL Studio, but i've never installed FL studio or sytrus on my computer
I'd do a system search for the Sytrus VST. Many times these VST's are common amongst several other programs. A good example is Sample Tank2.dll, which I have from Magix Music Studio. It is also in several other audio programs (not by Magix), that have instrument VST's.
Before just deleting it, I'd look to see which program is installing it, and decide how you wish to proceed. There are three things that happen with VST's:
1.) PrE loads and uses them
2.) PrE loads, but cannot use them (in PrPro there is a one-time message to that effect)
3.) PrE crashes trying to load them
Both PrE and PrPro will try to load and use all VST's that it finds.
Good luck,
Hunt
PS - I agree 100% with Steve on the free space. The normally recommended min. is 30GB of defragmented free space. I like much more, as the working files that an NLE creates are big, big, big.

Premiere Elements 11 "stops working" on first run

When I run Premiere Elements the first time it comes up with the message "Premiere Elements 11 has stopped working". On starting the second time, it starts ok until the system is booted again. This is from the Event log -
Log Name:      Application
Source:        Application Error
Date:          06/02/2015 11:35:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Rog-PC
Description:
Faulting application name: Adobe Premiere Elements.exe, version: 11.0.0.0, time stamp: 0x5041d27e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x531599f6
Exception code: 0xc0000005
Fault offset: 0x0000d709
Faulting process id: 0x98c
Faulting application start time: 0x01d04200fd8a8739
Faulting application path: P:\Program Files_W7\Adobe\Adobe Premiere Elements 11\Adobe Premiere Elements.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 47999bbb-adf4-11e4-b21e-0023545cca31
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-06T11:35:42.000000000Z" />
    <EventRecordID>23032</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Rog-PC</Computer>
    <Security />
</System>
<EventData>
    <Data>Adobe Premiere Elements.exe</Data>
    <Data>11.0.0.0</Data>
    <Data>5041d27e</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18409</Data>
    <Data>531599f6</Data>
    <Data>c0000005</Data>
    <Data>0000d709</Data>
    <Data>98c</Data>
    <Data>01d04200fd8a8739</Data>
    <Data>P:\Program Files_W7\Adobe\Adobe Premiere Elements 11\Adobe Premiere Elements.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>47999bbb-adf4-11e4-b21e-0023545cca31</Data>
</EventData>
</Event>

skatingdodger
On what computer operating system is your Premiere Elements 11 running?
Let us start with the video card/graphics card on this. Assuming Windows, what does the Device Manager/Display Adapters show for
video card/graphics card? How many cards? And, is the card driver version up to date according to the web site of the manufacturer of the card?
(We may come back to this later and ask for a roll back of the driver version to determine if that makes any difference/)
Does the problem exist with and without the antivirus and firewall(s) disabled?
Are you using a pen and tablet device or mouse?
Did you install the program to the default location on the Local Disk C? If not, then consider, with save to Local Disk C default according
to the following sequence
uninstall of the program using the usual Control Panel way
then..free ccleaner run through to get rid of leftovers from incomplete installs/reinstalls
CCleaner - Download
and then reinstall with antivirus and firewall(s) disabled.
Please review and consider, and then we can decide what next based on your results.
Thank you.
ATR

Premiere Elements 11 will not open Projects

I had to rebuild my Win 7 PC. Now Premiere Elements 11 will not open Projects saying that the file types are not supported. It will not open raw DV files either.

Henry Clayton
Along with Premiere Elements 11 on Windows 7 (presumed 64 bit), do you have the latest version of QuickTime installed? Are you running Premiere Elements 11 as Run As Administrator or from a User Account with Administrative Privileges?
Can you open a new project?
When you rebuilt your Window 7, did the source media that went into the existing projects remain in the same save locations with the same file names as before the rebuild?
How are you opening these project.prel files that I am understanding that you created in version 11 before the Windows 7 rebuild?
What is the nature of these "raw DV files" to which you refer? Are these DV AVI standard or widescreen files from a capture firewire into the Premiere Elements Capture Window?
Let us start here and then we can decide what next.
Thanks.
ATR
Add On...I did not see SG's and your posts until after I had posted mine.

Premiere Elements 11 start up error - Windows 7, 64 bit

Premiere Elements 11 was working fine until 1 week ago. Now I get an error on start up that says "Display Driver Intel HD Graphics is out of date. . . ". Then it loads very slowly. Once loaded, Premiere does not show the video though appears to be running it. I checked the Display Driver and it is up to date - latest version. I "restored" PC back to a date when Premiere was working well to no avail. I then unintstalled and re-installed Premiere 11 and still get the error. I have run diagnositics on the PC - no problems reported with display or any other function. I also have Premiere 9 and tried it - it runs just fine - no display problems at all. Where should I look next? Any suggestions?

In cases, such as these, I try to look for variables, in hopes of explaining the changes.
As most users have their OS Updates set to fully automatic, those are installed, fairly frequently (depending on OS, and version), and usually without any knowledge of the user.
However, the failures of video drivers seem to come after several OS Updates have been issued. MS just issued many for XP-Pro and Win7 (do not know about Win8), and we then see an increase in video driver issues. For users who employ their particular Adobe programs often, most video driver issues come immediately after Windows Updates (though not ALL Windows Updates).
I have all of my OS Updates set to notify me of availability, and then I can manually download, and manually install what I want. Taking my nVidia Quadro FX-4500 as one example, the only times that I have needed to update its video driver, have come immediately after Windows Updates - and I mean immediately. As I download and install my Windows Updates manually, I am ready for the possibility of video driver issues - most times, things work just fine afterwards, but not always. When some changes occur with the Windows Updates, a video driver update has, almost always, fixed them.
Why does this happen? I cannot tell you, but then not all Windows Updates are created equally, such as the recent one, that broke WMV display.
Do the video card/chip mfgrs. think that there is a need to update the video drivers? Observing AMD/ATI, and especially nVidia, it appears so, with a new driver coming about once per month. There ARE often features that get added, or tweaked, and especially when the card/chip is used in extreme gaming, but why every month? I would assert that it is to accompany changes in the OS with the Windows Updates, but we will need an engineer from nVidia to comment directly. As an aside, Matrox is a great card/chip mfgr. Their cards were cutting edge, and were the first to allow for multiple monitors. However, their concentration was on business machines, and not so much on Adobe products. They were slow to update their drivers, and Adobe users were often left out in the cold, for up to 6 mos. Matrox cards fell out of favor, due to the lack of video driver updates, with Adobe users. Business users, who only needed to use spreadsheets over 4 monitors, or were using software, that did not need to interface so closely with the video driver, were unaffected - not so for those in the 3D, or video-editing community.
If one were to try to draw coorelations between Windows Updates and video driver compatibility, I think that they could look to this, and a few other Adobe product forums for data. Now, most computer users do not have programs, that interface with the video driver much at all. They would never notice anything amiss. However, if one is an extreme gamer, or they work with programs, such as heavy-duty 3D, CAD *, or several Adobe products, like Premiere Elements & Pro, After Effects, Photoshop (PsE ?) or Encore, they encounter problems with video display, and often immediately after a Windows Update. In nearly every case, updating the video driver fixes things. Circumstantial evidence? Sure, but it is so common, as to almost be a "given."
Why does one not see so many video driver issues on a Mac? The video drivers, in most cases, ARE updated, when one updates their OS, as the OS updates, also update the video driver. The exceptions come from some of the recent nVidia CUDA cards, for the Mac, that will usually require a CUDA driver update - and that fixes things.
Just some observations,
Hunt
* Most serious CAD applications will require a special CAD video driver, and not the general ones that most folk use. In the CAD community, the CAD drivers are also released quite often, to fix changes in the OS.

Know why Premiere Elements 3.0 won't start when I double click the icon?

I have Windows Vista 32 bit. I have Premiere Elements 3.0 and the 3.0.2 patch. When I double click the icon, it won't load. I uninstalled and reinstalled the app but it still won't load. It worked as recently as last week. I had some virus issues so I took my laptop to Geek squad and they "fixed" the issues.
I never had this problem with Premiere before. Anybody know what might be causing it not to start?
I have been considering an upgrade. I see that they are up to version 9. Will version 9 even work on Vista?

It depends.
What do you mean by "I never had this problem before"? Do you mean Premiere Elements worked fine until the Geek squad restored your computer?
Unless they totally wiped your hard drive and reinstalled your operating system, they may have patched but not totally fixed your problem.
Or it could be that your computer just needs a good cleaning and defragging. Assuming you've got adequate power and a good 30-50 gigabytes of free defragmented space on your C drive.
But there's a very good chance that, if you've re-installed version 3 and it still won't run, then version 9 won't run either. After all, if you still haven't remedied yoru core problem, a new vehicle isn't likely to make any difference, right?
Still, there's no harm in trying. Why not download free trial and see?

Premiere Elements not starting

Hi
I purchased (and starting to get some serieus regrets) premiere elements 9.0 and running it on WIN7 x64
When I start it the welcome screen starts, when I chose New Project it tries to launch Premiere, but it stalls first for a long time at
the stage of ExporterQuickTimeHost.prm it takes a really long time and then the welcome screen looks again like I never clicked anything.
If I now click again on New Project , the welcome screen disappears completely.
I read some stuff about GPU settings and all, but I never get to that stage. Since I bought PE9 one week ago I never got to stage of even seeing the damned program!!
I noticed that 2 processes are started
Adobe premier elements.exe
and
Adobe premier elements 9.exe
They keep running, but there is no GUI
I updated the graphics drivers to the latest, I updated Quicktime to the latest, my WIN7 is fully up to date with the latest updates....
HELP!!!!!!!!!!! I'M GETTING REALY FRUSTRATED!!! WHy is there no LOG anywhere to be found!?!?!?!
this is my system:
    Number of cores        4 (max 8)
    Number of threads    8 (max 16)
    Name            Intel Core i7 720QM
    Codename        Clarksfield
    Specification        Intel(R) Core(TM) i7 CPU       Q 720 @ 1.60GHz
    Package (platform ID)    Socket 989 rPGA (0x4)
    CPUID            6.E.5
    Extended CPUID        6.1E
    Core Stepping        B1
    Technology        45 nm
    Core Speed        2376.5 MHz
    Multiplier x FSB    18.0 x 132.0 MHz
    Rated Bus speed        2112.5 MHz
    Stock frequency        1600 MHz
    Instructions sets    MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x
    L1 Data cache        4 x 32 KBytes, 8-way set associative, 64-byte line size
    L1 Instruction cache    4 x 32 KBytes, 4-way set associative, 64-byte line size
    L2 cache        4 x 256 KBytes, 8-way set associative, 64-byte line size
    L3 cache        6 MBytes, 12-way set associative, 64-byte line size
    FID/VID Control        yes
    Turbo Mode        supported, enabled
    Max turbo frequency    2800 MHz
    Max non-turbo ratio    12x
    Max turbo ratio        21x
    Max efficiency ratio    7x
    TDP Limit        45 Watts
    TDC Limit        37 Amps
    Core TDP        37 Watts
    Uncore TDP        8 Watts
    Power @ 7x        15 Watts
    Power @ 8x        18 Watts
    Power @ 9x        23 Watts
    Power @ 10x        29 Watts
    Power @ 11x        36 Watts
    Power @ 12x        45 Watts
    Max bus number        63
    Attached device        PCI device at bus 63, device 2, function 1
    Attached device        PCI device at bus 63, device 3, function 4
    Attached device        PCI device at bus 63, device 2, function 1
Chipset
Northbridge            Intel DMI Host Bridge rev. 11
Southbridge            Intel PM55 rev. 05
Graphic Interface        PCI-Express
PCI-E Link Width        x16
PCI-E Max Link Width        x16
Memory Type            DDR3
Memory Size            4096 MBytes
Channels            Dual
Memory Frequency        528.1 MHz (2:8)
CAS# latency (CL)        7.0
RAS# to CAS# delay (tRCD)    7
RAS# Precharge (tRP)        7
Cycle Time (tRAS)        20
Row Refresh Cycle Time (tRFC)    59
Command Rate (CR)        1T
Uncore Frequency        1980.4 MHz
Memory SPD
DIMM #                1
    SMBus address        0x50
    Memory type        DDR3
    Module format        SO-DIMM
    Manufacturer (ID)    Samsung (CE00000000000000)
    Size            2048 MBytes
    Max bandwidth        PC3-8500F (533 MHz)
    Part number        M471B5673EH1-CF8
    Serial number        617BF7E1
    Manufacturing date    Week 40/Year 09
    Number of banks        8
    Nominal Voltage        1.50 Volts
    EPP            no
    XMP            no
JEDEC timings table        CL-tRCD-tRP-tRAS-tRC @ frequency
    JEDEC #1        6.0-6-6-18-24 @ 457 MHz
    JEDEC #2        7.0-7-7-20-27 @ 533 MHz
    JEDEC #3        8.0-8-8-23-31 @ 609 MHz
DIMM #                2
    SMBus address        0x52
    Memory type        DDR3
    Module format        SO-DIMM
    Manufacturer (ID)    Samsung (CE00000000000000)
    Size            2048 MBytes
    Max bandwidth        PC3-8500F (533 MHz)
    Part number        M471B5673EH1-CF8
    Serial number        617BF77F
    Manufacturing date    Week 40/Year 09
    Number of banks        8
    Nominal Voltage        1.50 Volts
    EPP            no
    XMP            no
JEDEC timings table        CL-tRCD-tRP-tRAS-tRC @ frequency
    JEDEC #1        6.0-6-6-18-24 @ 457 MHz
    JEDEC #2        7.0-7-7-20-27 @ 533 MHz
    JEDEC #3        8.0-8-8-23-31 @ 609 MHz
Graphic APIs
API                NVIDIA I/O
API                NVIDIA NVAPI
Display Adapters
Display adapter 0
    Name            NVIDIA GeForce GT 230M
    Revision        A2
    Codename        GT216
    Technology        40 nm
    Memory size        1024 MB
    PCI device        bus 1 (0x1), device 0 (0x0), function 0 (0x0)
    Vendor ID        0x10DE (0x103C)
    Model ID        0x0A28 (0x363C)
    Performance Level    Default
        Core clock    135.0 MHz
        Shader clock    270.0 MHz
        Memory clock    135.0 MHz
    Performance Level    2D Desktop
        Core clock    405.0 MHz
        Shader clock    810.0 MHz
        Memory clock    324.0 MHz
    Performance Level    3D Applications
        Core clock    500.0 MHz
        Shader clock    1100.0 MHz
        Memory clock    790.0 MHz

If you can get it working in diagnostic mode, try adding the various items back. Either do this one at a time or by halves.
Halves - say you have twenty items loading:
add back half (ten) and see if it still works.
If it does then the problem is in the half you removed.
If it doesn't then the problems is in the half you left starting.
If it does (2) then add back half (five) and see if it still works. Repeat the halving until you get to the last item - that should be the problem one.
If it doesn't (3) then take out another half (five) and see if it now works. Repeat the halving until you get to the last item - that should be the problem one.
Cheers,
Neale
Insanity is hereditary, you get it from your children

Getting the message Adobe Premiere Elements could not start after silent install

I am getting the following message after running a silent command line installtion. The coomand line I am using is
setup.exe" /S /UL1033 /V"/qn COUNTRY=244 SERIALNUMBER="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" the x64 on Windows 7 64-bit.
After manually running the set-up.exe installer located in the ElementsSTIInstaller folder, Premiere elements launchs.
What is the cause of the error after running a silent installion?
JmFrx

Hi jam62m,
Please follow the steps mentioned in kb article : http://helpx.adobe.com/premiere-elements/kb/silent-install-instructions-premiere-elements- 4.html
and command to install Premiere elements silently is : start/wait OEM.exe /UL%LangCode% /V“SERIALNUMBER=%Adobe volume license serial number%”
Example : C:\ Adobe Premiere Elements 10/Adobe Premiere Elements 10 - 64 Bit> start/wait OEM.exe /UL1033 /V"SERIALNUMBER=1111-1111-1111-1111-1111-1111"
Regards,
Jatin Dembla

Premiere Elements 12 on Win8.1 x64 isn't starting

Similar Messages

Maybe you are looking for