Are you saying that a tryout of Premiere Elements 13 is crashing on you after you select Video/New Project from the Welcome Screen?
What computer operating system is the program running on?
1. Did you install the program with Windows Firewall(s) disabled? (Assumed on antivirus was ever installed).
2. Are you running the program from a User Account with Administrative Privileges?
3. Do you have the latest version of QuickTime installed on your computer with the Premiere Elements13 tryout?
4. Is your video card/graphics card driver version up to date according to the manufacturer of the card?
If you have not already, please do the uninstall/reinstall in the following scheme
1. Uninstall, routine Control Panel way.
2. Free ccleaner run through (regular and registry cleaning parts) to get rid of leftovers from all incomplete uninstalls and
3. Reinstall the program with firewall(s) disabled. (Assumed no antivirus installed).
Let us rule in or out the above and then decide what next.
1. I did not install it with the firewall disabled. I will try that
3. I don't have quick time installed at all. Is that a requirement?
4. As indicated in my original post.
Before any ccleaner and uninstalls/reinstalls, please download and install the latest version of QuickTime, and determine
if that completely or partially resolved you issue.
QuickTime is a requirement (among other things, you will not have QuickTime presets in the program without it).
It, like Premiere Elements (any version), requires that it be run from a User Account with Administrative Privileges.
Please let us know the results. Then we can decide what next if the problem is not solved yet.
installed quick time
run ccleaner (several passes of course)
details from crash:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Elements.exe
Application Version: 18.104.22.168
Application Timestamp: 54065543
Fault Module Name: libcef.dll
Fault Module Version: 3.1750.1738.0
Fault Module Timestamp: 539860dd
Exception Code: c000001d
Exception Offset: 00000000020f3553
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 1849
Additional Information 2: 1849c65267ce2967d89f315e1c3c4b82
Additional Information 3: 4bd2
Additional Information 4: 4bd2aa1900d8927bd0f22b0bbfeb6f46
Thanks for the reply with details.
I have never come across a problem with a faulty module = libcef.dll.
So, I am going to offer a bit more generic troubleshooting.
Let us try deleting the Premiere Elements 13 settings file
Local Disk C
and in the 13.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 13.0 Folder in which the Adobe Premiere Elements Prefs file 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 remind me, in all this have you remembered to disable the antivirus as well as the firewall(s) - that is including and downloading and installing related to program installation?
Let us see if PRE_help or Adobe Staff steps into your thead to offer new product troubleshooting suggestions. If not, we will evaluate your report to this post and then decide what next ourselves..
Please provide following information :
- Try to launch PRE 13 from main EXE (l C:\Program Files\Adobe\Adobe Premiere Elements 13) please check are you getting the PRE editor splash screen or not?
- Do you have other Adobe application installed on system like Photoshop or Any previous version of PRE and are you able to launch them ?
- Is the computer is member of office network domain or is it a home computer ?
I have also send you a PM please reply.
Many thanks for your Adobe presence in this thread dealing with a Premiere Elements 13 issue with faulty module = libcef.dll.
We will be looking forward to the outcome.
I have the same problem with libcef.dll. APR 13 crashes after start.
I am not sure where the faulty module "libcef.dll" issue stands at this point.
There has been no follow up by Adobe Staff Adhishek Kapoor in this 2014 thread or elsewhere. I have no insider information at Adobe.
So, I do not know if Adhishek Kapoor is still with Adobe.
This same "libcef.dll" matter came up in a recent thread here. There was no solution for the user reporting
the issue. I will see if I can find the thread. It was posted within the past month, if I recall correctly. Brett N Adobe Staff
person did enter that thread. You may be interested in his and other comments in that thread.
Add On..This the most recent thread on libcef.dll that I remembered