If it's caused by a codec issue, then you can fix it by installing the latest version of Quicktime, per the installation instructions.
If that doesn't do it, go to C:/PROGRAM FILES/ADOBE/PREMIERE ELEMENTS 8/SETTINGS/SEQUENCE PRESETS and make sure that there is both an NTSC and PAL folder and that each contains project preset files.
If that's not the case, you have a problem.
If those files are there, click the New Project button and note which project settings appear on the lower left of the option panel.
The settings file is not there at all... What is the easiest way to get this?
If that file is missing, then I would definitely do a Repair Install. That might well lead to needing to update again. I am surprised that with an installation and then the update, this file did not make it into the proper folder.
You are running as Administrator, aren't you?
Yes running as administrator. There is no option to repair... I have uninstalled and reinstalled multiple times with no luck... Before running the patch we had another issue, got the message Premiere has unexpectedly quit, please try again but found a fix that said running the patch will stop this, which it did but now we have the premiere could not find any valid editing modes error...
Try uninstalling the program and then DELETING the entire folder C:/PROGRAM FILES/ADOBE/PREMIERE ELEMENTS 8.
Then reinstall the program.
If that doesn't work, it may be time to call Adobe Tech Support. You've got something very strange at work on your machine.
Here is a link to an Adobe TechNote about the same issue with an earlier (much earlier!) version of Premiere Elements and Windows XP.
I'll leave it to Steve and Bill as to whether the fix offered in the link for Premiere Elements 2 would still be applicable to your version of Premiere Elements.
Hope this is of some assistance.
Thanks for that Adobe KB Article. The second solution could certainly work, if solution 1 does not.
Many programs, like the K-Lite CODEC pack, can overwrite existing CODEC's. Normally, Adobe NLE's do a good job of "hiding" their installed CODEC's from other programs. This hiding, through the Adobe naming convention, is also why some utilities, like G-Spot and Sherlock the CODEC Detective, will issue a false-positive that there are issues with Adobe CODEC's. Maybe one day, they will be coded to recognize Adobe's naming convention, so as to not yield those false-positives.
Besides overwriting good, commercial CODEC's (often with hacked, or reverse-engineered versions), many of those programs can also alter the OS's priority for CODEC's. Even Adobe's naming convention will not prevent that, as those programs do this deed in the Registry. What happens is that instead of the OS looking to the good CODEC, it now first tries to work with the new one, which might not be useful
This is the main reason that I do not use any CODEC packs, and monitor what all new editing, or even player programs, do to my Registry. Before installing any, I do a manual System Restore Point, and keep copies of "known good" Registries handy.
The same thing can happen, when these programs "hook" file formats, for themselves, breaking the link to the programs, that we have chosen to Open those file formats in.
With the solution 1 - reinstalling, what will happen is that the Adobe product will usually correctly write the necessary CODEC's and links to the Registry, negating some of the nefarious actions of other programs.
Good luck, and thanks for that link.
PS - another thing that bothers me about CODEC packs, is that many will also install FFDShow, and that has proved to be a big issue with Adobe NLE's, going back to at least since Premiere Pro 1.0.
Thanks for your input, turns out it was a missing folder... During the install the "Settings" folder for whatever reason did not install on local machine for two users but did for the third... Copied the folder to the other two users resolved the issue...
Great news! Why the installation was not complete in 2/3 is a mystery, but that you found the issue is good.
Thanks for reporting, and good luck,
I have the same problem, how did you install the settings folder?
I was able to copy the settings folder off another machine that it had installed correctly on...