When you attempt to start Premiere Pro, it returns the error message, "Adobe Premiere Pro could not find any valid editing modes. Please reinstall Premiere Pro and try starting again."

Possible SolutionsEdit

Do you have the Nimo codec pack installed? If so uninstall it, because I've seen it cause that problem.
Try this: check to see if you have any codecs listed as installed. Open the Windows Control Panel and choose Sounds and Audio Devices. Select the Hardware tab and select video codecs from the list and then click the Properties button at the bottom of the page. From the Video Codec Properties tab, check to see if you have any codecs listed. If you get a message that says "You have insufficent privledge to add or remove a driver", then you've got a permissions problem.
You should be able to correct the problem by making a change in the registry. Open the registry editor (Start > Run > Regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32. Right-click the Drivers32 folder and select Permissions. Select each user and group one by one (Administrators, Creator Owner, Power Users, System, Users, Everyone) and change the current permissions to allow both Full Control and Read. Click the Apply button and OK. You should now see a list of files appear in the right column of the registry editor that wasn't there before.

and also

This is a codec problem. Honest. I swear. Although there are several causes for this problem, it still comes down to the same thing. Either the VFW codecs on a system can't be accessed at all or an individual codec or group of codecs are messing up access to DirectShow. If you're getting this message, you should also be having trouble with Windows Media Player. If you can't find the codec that's causing the problem, and Premiere worked before, try using XP's system restore to roll the system back to a date when everything worked. You could also try running the DirectX diagnostic to see if it can detect the cause of the problem (Start > Run > Dxdiag). This isn't an AMD problem and it isn't an SP2 problem. It's definitely something that was installed on the system. Probably something that was downloaded either on purpose or inadvertently from the web.
Naamtallah and Astralworker, you guys can also try dowloading the latest version of Windows Media Player and reinstalling the latest version of DirectX (9.0c). One of those tricks might also resurrect DirectShow on your system.
I have a ATI 9600 video card and when I installed the software for it, it whacked a registry entry that prevented Premiere Pro from getting digital editing services it needed from Windows.
The registry entry whacked was at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Drivers32
In this registry directory look for an entry named VIDC.DRAW. The value for mine says DVIDEO.DLL. The problem was there was an offending space preceding the dll name. Once removed everything worked fine.
I had exactly the same problem and tracked it down to incomplete installation of my ATI graphics card drivers for my All-In-Wonder card. It appears that the installation of ATI drivers requires access to the internet to complete the installation. My firewall stopped this and although it appeared to install OK there was something missing. I reinstalled the ATI drivers with the firewall closed and after that Adobe Premiere Elements worked fine.
  • Andrea G. said:
I confirm it's a codec problem : use GSpot to list installed codecs (system -> list codecs and other filters) find the missing ones and simply reinstall them. In my case it was ffdshow wich was missing after I installed matroska.
  • "American Dragon" Bryan Danielson said:
It certainly is a codec problem, I too had matroska and ffdshow installed, after uninstalling both, Premiere worked fine.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.