CPU at 100% when starting Premiere Elements 10

Hi,
When I start Premiere Elements 10 the program runs at 100% CPU usage. Even when I haven´t opened a project yet. So it is not caching media or something. On the screenshot below you can see my problem. There is no project open but the task "Adobe Premiere Elements.exe" is running at 100%.
This makes my system very slow and instable.
I have a 2GB Pentium D 3.0 GHz and my harddrives have lots of free space (They are not working very hard when using Premiere).
Can anyone help me with this?
Dimitri

No, it doesn't barely meet the tech requirements (regardless of Adobe's suggested minimums). It is not adequate to work with this program.
With only 2 gigs of RAM, the program is not only idling but also doing a lot of paging. And, if you've got less than 30 gigs of clean, free, defragmented space, it's also struggling with defragmentation.
It's also possible the Organizer is auto-analyzing your drive and if you've got other programs running in the background (like a live defrag program or an intrusive antivirus program like Norton or McAfee) that could be contributing to the problem.

Similar Messages

[..\..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

Error "Registration information is invalid" when you start Premiere Elements 7 (Windows)

Issue
When you start Adobe Premiere Elements 7 for the first time, Premiere Elements returns the error message "Registration information is invalid. Please reinstall Adobe Premiere Elements."
Solution
Do one of the following solutions:
Solution 1: Install Premiere Elements 7 using the Premiere Elements 7 serial number.
If you purchased Premiere Elements bundled with Photoshop Elements, you may have used the Photoshop Elements serial number included in the pack to install Premiere Elements. Uninstall Premiere Elements and reinstall Premiere Elements using the Premiere Elements serial number.
Note: The Premiere Elements serial number starts with the number set 1143. The Photoshop Elements serial number starts with the number set 1057.
Solution 2: Use a Company Name with 40 single-byte characters or fewer, or 20 double-byte characters or fewer.
When installing Premiere Elements, you are asked to provide a user name, a company name, and a serial number. While the company name field is not a required field for installation, if you choose to enter data, do not enter a name that contains more than 40 single-byte characters or more than 20 double-byte characters.
Note: A single-byte character is any character in the standard ASCII character set. English language characters are all single-byte characters. Double-byte character code uses two bytes to represent one character. The double-byte character set was developed for the Japanese, Chinese, and Korean characters sets. Many extended ASCII characters are also double-byte.
Solution 3: Install Premiere Elements to a location that does not contain extended ASCII characters in the file path.
Do not install Premiere Elements to a location that uses extended ASCII characters in the file path. Extended ASCII characters include characters such as , –, ›, †, ‡, ‘, Ÿ.
Note: The default installation path for Adobe Premiere Elements does not contain extended ASCII characters.

Thanks. I thought of that. But won't I get whammied for registration again? I just registered this at adobe last month after rebuilding a crashed system. In other words, will Adobe know that I've uninstalled it, and therefore have an available license? Thanks for the welcome. I've been a Studio premium user for 3 years, and now that my product is no longer supported....I need support!
Thanks.

On my Mac, after the installation i get this error when i start - Premiere Elements 13.0 has encountered an error. [/Adobe/pre/main/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283] any ideas how to fix this

On my Mac, after the installation i get this error when i start - "Premiere Elements 13.0 has encountered an error. [/Adobe/pre/main/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283]"
any ideas how to fix this, i don't know or haven't faound out how to contact Adobe supporet....

Here's the contact link for Adobe support. It's just three clicks from the site's home page.
Contact Customer Care

How to start Premiere Elements 11 with welcome screen

How to start Premiere Elements 11 with welcome screen

thank you
Date: Sat, 20 Jul 2013 06:02:36 -0700
From: [email protected]
To: [email protected]
Subject: How to start Premiere Elements 11 with welcome screen
    Re: How to start Premiere Elements 11 with welcome screen
    created by Steve Grisetti in Premiere Elements - View the full discussion
Are you saying that you want to see the menu screen when you launch the program?
If so, go to the Help menu and select Welcome Screen. When the Welcome Screen launches, click on the gear in the upper right corner and set Always Start On to Welcome Screen.
Or are you asking how to start the program from the Welcome Screen?
If so, you may want to check out my free 8 part Basic Training for Premiere Elements tutorials.
http://forums.adobe.com/thread/537685?tstart=0
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5522867#5522867
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5522867#5522867
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5522867#5522867. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Premiere Elements by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

When installing Premiere Elements I get an error with Shared Technologies

When installing Premiere Elements onto a Windows XP Service Pak 3, I get an error with Shared Technologies.

Hi,
Thx for the reply.
I had Bridge open in background and once I closed that Elements installed correctly.
Thank you.

I'm trying to start Premiere Elements and am getting an Error:1 message

I'm trying to start Premiere Elements and am getting an Error:1 message@

That's too bad.
If help is desired, try providing details of the situation or search the forums for the issue yourself.
We are not mind readers.

Starting premiere elements 11 adobe stops at exporter quick time host.bundle is there a fix?

starting premiere elements 11 adobe stops at exporter quick time host.bundle is there a fix

Think you are in the wrong forum.
This is the one you'll need.
http://forums.adobe.com/community/premiere_elements
A moderator will come along soon and move your post.

Installation OK but nothing happend when launching Premiere Elements 13

Hi everybody,
I have an issue when launching Premiere Elements 13.
Installation was ok, serial ok.
When launching
- i choose Premiere instead Organizer
- Pop up ask me to connect to my Adobe id account to activate => next
- i enter my id for connection => ok
- Software License Agreement => I agree
And then nothing happen, the dialog box close and ... nothing.
I work on win7 64bits.
I buyed both Photoshop Elements 13 and Premiere Elements together.
I install Photoshop on my job computer and i install Premiere on my personnal computer.May it come from here.
Thanks for your expérience.

Wombat_kio
Premiere Elements 13 on Windows 7 64 bit.
Does the problem exist with and without the antivirus and firewall(s) disabled?
Do you have the latest version of QuickTime installed on your computer with Premiere Elements? And are you running the programs as administrator?
Is your video card/graphics card driver version up to date according to the web site of the manufacturer of the card?
Please look at the hosts file and other considerations included in the following Premiere Elements 12 link and determine if any applies to your Premiere Elements 13 situation
ATR Premiere Elements Troubleshooting: PE12: Premiere Elements 12 Editor Will Not Open
Please review and consider, and then we will move forward based on your details in your reply.
Thank you.
ATR

Computer Crash when adobe Premiere Element 7.0 start

Dear all,
I'm the owner of an Adober Premiere element 7.0 sw (bundled into Sony handycam sw suite).
Unfortunatly, when launching the sw and during the loading of various module, the computer crash (meaning immediate hard reset with restart to bios...)
I'm using Windows XP SP3 on an HP M7449fr (dual core intel 3Ghz + 2GB ram + Ati radeon X1300 on PCiexpress)
i have updated all my drivers, windows XP is update to date.
I don't see what to do more, the crash is systematicall and doesn't let any trace at system level for debugging.
All help welcomed.
Thx by advance
René

For info: for user of HP product with Realtek audio componant:
i have found on HP site a driver update from 5.10.00.5211 to 5.10.005229
link here:
ftp://ftp.hp.com/pub/softlib/software7/COL14855/pv-39525-1/sp26726.exe
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-39525-1&lc=fr&dlc =fr&cc=fr&lang=fr&os=228&product=2510352
this update is announced as " Improves compatibility with Adobe Premier and Premier Elements video editing software."
Good candidate too ..
I will try this update first and if no improvement, then try the wave_warp.aex patch.
BR
René

Performance problems when using Premiere Elements for photo slideshows

Hello,
I had been using Premiere Elements 9 (PE9) to make a simple slideshow for my parents from their vacation trip and I ran into some serious performance problems. I had used it to create similar projects before, but not nearly as big. This one is like 260 photos, so basically it is 260 seperate clips. I have a POWERHOUSE workstation (see below) so it isn't my PC. Even when PE9 crashes, looking at my performance monitor my CPU and RAM aren't even halfway being utilized. I finally switched to Windows Movie Maker of all things and it worked seemlessly, amazing really. I'm wondering if I was just using PE9 for something other than what it was designed for since there weren't really any video clips, just a ton of photos that I made into video clips, if that makes sense. Based upon my experience with this so far, I can't imagine using PE9 anymore for anything really. I might have the need for a more professional video editing program in the near future, although it does seem like PE has a lot of features. How can I make sure it utilizes my workstation to its full potential? Here are my specs:
PC
Intel Core i7-2600K 4.6 GHz Overclocked
ASUS P8P67 Deluxe Motherboard
AMD Firepro V8800 Video Card
Crucial 128 GB SATA 6Gb/s Solid State Drive (Operating System)
Corsair Vengeance 16GB (4x4GB) Memory
Corsair H60 Liquid CPU Cooler
Corsair Professional Series Gold AX850 Power Supply
Graphite Series 600T Mid-Tower Case
Western Digital Caviar Black 1 TB SATA III Hard Drive
Western Digital Caviar Black 2 TB SATA III Hard Drive
Western Digital Green 3 TB SATA III Hard Drive
Logitech Wireless Gaming Mouse G700
I don’t play any games but it’s a great productivity mouse with 13 customizable buttons
Wacom Intuos5 Pen Tablet
Yes, this system is blazingly fast. I have yet to feel it slow down, even with Photoshop, Lightroom, InDesign, Illustrator and numerous other apps running at the same time. HOWEVER, Premiere Elements 9 has crashed NUMERUOS times, every time my system wasn't even close to being fully taxed.
Monitors – All run on the ATI V8800
Dell Ultra Sharp 30 inch
Samsung 27 Inch
HAANS-G 28 Inch
Herman Miller Embody Ergonomic Chair (one of my favorite items)

Andy,
There ARE some differences between PrE and PrPro w/ an approved CUDA-capable and MPE hardware acceleration-enabled nVidia video card, but those differences show up ONLY in the quality of the Scaling. The processing overhead is almost exactly the same, when it comes to handling the extra pixels.
As of PrPro CS 5, two things changed:
The max. size of Still Images went up from 4096 x 4096 pixels, to quite a bit larger (cannot recall the numbers now).
The Scaling algorithms have been improved, though ONLY with the correct nVidia cards, with MPE hardware support enabled.
Now, there CAN be another consideration, between the two programs, in that PrPro CS 5 - CS 6, are 64-bit ONLY, so one benefits from the computer and OS to run it. PrE can be either 32-bit, or 64-bit, so one might, or might not, be taking advantage of the 64-bit program and OS. Still, the processing overhead will be almost identical, it's just that the 64-bit OS can spread it around a bit.
I still recommend Scaling the large Still Images in PS, prior to Import, to keep that processing overhead as low as is possible. Scaled Still Images work just fine, and I have one Project with 3000+ Scaled Still Images, that edits just fine in PrPro, even on my older 32-bit workstation. Testing that same machine, and PrPro some years ago, I could ONLY work with up to 5 - 4096 x 4096 Stills, before things ground to a crawl.
Now, Adobe AfterEffects handles large Still Images differently, so I just moved that test Project to AE, and added another 20 large Images, which edited just fine. IIRC, AE can handle Still Images up to 10K x 10K pixels, and that might have gone up, as of CS 5.
Good luck, and hope that helps,
Hunt

Msiexec error when installing Premiere Elements

I had a very disappointing time with support and still cannot install my new copy of PS Premiere Elements.
I downloaded the softare. Installed the PS Elements. It was smooth.
I then tried to install Premiere Elements and it does not work.
When I started the .exe it asked for a place to extract files. I did this. Then it tried to install. But after a while I get this box with the msiexec commands listed in it. Eg.
Windows ® Installer. V 3.01.4001.5512
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
                </package | /i> <Product.msi>
                                Installs or configures a product
                /a <Product.msi>
                                Administrative install - Installs a product on the network
                /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
                                Advertises a product - m to all users, u to current user
                </uninstall | /x> <Product.msi | ProductCode>
                                Uninstalls the product
Etc etc etc.
And then finished with an error that it was not installed.
I then manually clicked on setup.exe I then got a screen asking for language, but then I get a windows showing again options for using msiexec command.
When I try using the Adobe Premiere Elements 10.msi then i get an error
Adobe Premiere Elements 10 - Setup
Install Adobe Premiere Elements 10 using the setup.exe in the root folder.
I called support. They had me extract files into a folder off of eg C:\PS
I did this. Started the setup.exe, Same error as above msiexec.
He then had me install it with the runas administrator. I tried same error.
He then told me to create a new account on the computer with admin privileges. I didn’t really like this, but I did this . And restarted the setup but still same msexec error.
The support person said it was an admin error. Sadly I think he is wrong, he just read the message and quickly gave the first thing he could think of. I asked him why he felt that, and he said based on the error. However sadly I don’t believe he is understanding the “error” He saw the words “Administrative install - Installs a product on the network” (see above) and quickly said oh its an admin problem. I didn’t realize at the time that this is not really an error message regarding the administrator, but just the output of a badly formed command, with a default output of a badly formed command.
Let me explain..
What I believe is that somehow the script that is running the install is trying to run the msexec program and the output is simply the output of the msexec program when the parameters are not right. In fact if you open a dos prompt and type msiexec you get the exact same output. The error is not really an error but just the output like any other of a command with no perimeters. Like if you type defrag or copy from the command prompt with out the right parameters. The command gives a response. For some reason the support person saw the word “administrator” and quickly jumped to the conclusion oh its an administrator issue that was the error. The support person kept asking me if that was all and was definitely trying to get rid of me. It quite frankly was very disappointing that he didn’t know this how to resolve the issue and just wanted me to go away.
Can anyone tell me how to install this program. I am on a domain and have both domain and local passwords. Im using windows XP.
By the way I tried using
ok, i fnally was able to extract the files, enter serial numbers, and run the program, I'm testing the program now
the problem is adobe's fault, a faulty script or something on the dvd.
in my situation, to get this program installed, i decided to do the following:
1) optional: copy the install dvd to hard drive.
2) locate the adobe premiere elements 10.msi file.
3) type in    msiexec /a "adobe premiere elements 10.msi" /qb TARGETDIR="C:\tempfolder"
to unpacked the msi archive.
4) go into the c:\tempfolder/programfiles/Adobe
5) optional: copy or move the Adobe Premiere Elements 10 folder into your c:\Program Files\Adobe folder so it sits with the rest of your adobe programs
6) you have to make your own desktop icon
7) when you go into the premiere elements folder click on Adobe Premiere Elements.exe to start the program
8) it may tell you to download the Adobe Application Manager from http://www.adobe.com/go/applicationmanager
so download it if necessary. the ApplicationManager2.0_all.exe file will silently install.
this does work HOWEVER, it doesnt really install it with all the registry etc. and doesnt integrate it into the PSE. So I dont think this is really the right option.
Oviously it should install properly. (thanks anyway)

Thanks Jeff for helping.
The version of the install software is definetely 32 bit. eg its PremiereElements_10_LS15_win32.exe with the corresponding win32 zipped file.
BTW the fact that I can extract the files and then run the program as a stand alone program means I think? that it is the right version and can run on this computer. Its obviously an install issue it seems.
The version of XP i have is XP prof sp3 version 5.1 build 2600.xpsp_sp3_gdr.101209-1647
Based on your comment regarding the install version, I found and downloaded the 4.5 version of the msiexec software. Tried to install the PE again and got the same error ... EXCEPT that now the output comes from the 4.5 version instead of the previous version. eg.
Windows ® Installer. V 4.5.6001.22159
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
etc etc.
So obvously the new installer got installed, but still the install process doenst work.
Any further ideas.

Help! Starting Premiere Elements 10: A problem has occured with the licensing... Error 213:11.

When starting the product, this error comes up:
I tried several reinstalls with/without admin rights, with/without diabled antivir software, as testversion and with a valid licence key. All under Windows 7 32bit.
What can I do?
Thx, Guenter

Configuration Error the steps should still be applicable for Premiere Elements 10. For the best assistance, I recommend our chat support at http://adobe.ly/tl8Vx7. Our chat representatives can provide a personalized experience to resolve the issue you have described.

CPU and Motherboard upgrade for Premiere Elements 11

Hi all. Been perusing the Premiere Elements and Pro forums but still have a few questions.
I’m upgrading Premiere Elements from PrE9 to PrE11 and am upgrading some of my desktop’s hardware at the same time. I could use some advice about choosing a CPU, graphics card, and motherboard. The goal of this upgrade is to considerably speedup transcoding without breaking the bank. The budget’s a bit flexible but I’d like to keep it at or under $500 for the motherboard/CPU combo.
The computer will be used for editing and transcoding AVCHD videos. The videos are shot in either 1080i or 1080p using a Panasonic HDC-TM700.
I’m processing about 2-3 hours of video per week and my current system takes a long time to transcode. For example, it takes well over 3 hours to convert 1 hour of AVCHD video to wmv. An Intel Core 2 Quad Q8300 with 3 GB of RAM was fine for the occasional video, but it’s too slow for what’s currently needing to be processed.
New CPU:
At this point I’m looking at the following processors:
i5 3570K
Ivy Bridge
No hyper threading
i7 2600K
Sandy Bridge
hyper threading
i7 3770K
Ivy Bridge
hyper threading
Questions:
) Does PrE11 make use of hyper threading?
) If PrE11 doesn’t use hyper threading is there much of anything to be gained by getting the i7? The i5 is about $90- $100 cheaper than the i7 CPUs and seems pretty quick.
New Motherboard:
I’ve had good luck overclocking Asus motherboards, so I’m leaning towards getting another one, but am open to alternatives.
The choice of board will depend mainly on Intel’s northbridge chip:
Ivy Bridge – Z77 chip
Sandy Bridge – Z68 chip
Question:
) Are there any other northbridge chip/CPU combos I should be looking at?
Current Graphics Card:
nVidia Geforce 8400 GS 512 MB DDR2
Drivers are up to date and downloaded from nVidia.
Question:
) Since PrE11 doesn’t use the graphics card’s GPU, will it be okay to continue using this card for the new build? I’m not a gamer and this card works just fine for the current build.
Additional hardware/software details:
PSU: Seasonic X660
HDD: Four 1TB 7200 rpm drives
Memory: 16 GB DDR3 RAM
OS: Win7 64 bit or Win8 64 bit (haven’t decided yet whether to go with Win 7 or 8)
Thanks in advance for your comments and help.

I have been going through the same process. Yes PE does support multiple threads and definatley go with the ivybridge i7 cpu. Asus is also the board I'm going with. They have made OCing much easier but be careful of high temps that leads to early failure of the cpu . Most of them let you have a maximum of 32 gig of ram and with memory so cheap check out upgrading to a higher grade memory. This can be overclocked as well. One of the ivy bridge cpus has 6 cores but cost $500 plus and requires a more expensive MB as well. too expensive for me though. I believe the built in graphics processor in the i7 k series the HD4000 is enough for PE. For about $650 I got an i7 at Microcenter for $229 and I think they just lowered the price to $200 an Asus MB at Newegg for $140 and 16gig ram for $70 also check out SSD drives in the 128 gig range are about $100 which you could use for you C: drive maybe take it up to 256 gig for more. They are getting pretty cheap
Good luck with your build.

CPU runs 100% when logging with DAQmx using card 6229

Hi!
When I start a logging using DAQmx Analog Input the computer CPU runs 100%. This causes the problem that the computer locks and the subsequent steps in the program are left without computer CPU recourse. After the logging is compleet, 1750 samples/10 channels at 250Hz, the program runs on, but the loggfile is at that point useles.
I have instaled LV 7.1.1 and am using DAQ 7.4.
Anyone that recognizes this problem?
Regards,
Idriz
Idriz "Minnet" Zogaj, M.Sc. Engineering Physics
Memory Profesional
direct: +46 (0) - 734 32 00 10
http://www.zogaj.se

Hello Idriz!
I just wanted to respond here as well so you know that we have read your post on this very forum. Still waiting for an answer from the US and after that I will forward that information to you.
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

CPU at 100% when starting Premiere Elements 10

Similar Messages

Maybe you are looking for