Premiere elements 10 crashes on startup error DirectoryRegistry.cpp-283

  • 1
  • Problem
  • Updated 4 years ago
  • Solved
I bought premiere elements 10 yesterday on mac app store and until now i wasnt able to use it.
It crashes on the startup and this error apears.

[/Users/ramyadav/perforce/premiere/elements/molecules/pre10-bullseye/m olecule-17/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegist ry.cpp-283]

Need help with this!
Photo of Pedro GONÇALES

Pedro GONÇALES

  • 4 Posts
  • 0 Reply Likes
  • very mad!

Posted 4 years ago

  • 1
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Chief Customer Advocate

  • 10757 Posts
  • 809 Reply Likes
That's a strange error. One thing to try, to make sure it isn't a permissions issue, is to create a new admin user account and try to run from there.
Photo of Pedro GONÇALES

Pedro GONÇALES

  • 4 Posts
  • 0 Reply Likes
I did what you said and it worked!
What should i do to make it work on my account? any idea?

thanks!
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Chief Customer Advocate

  • 10757 Posts
  • 809 Reply Likes
Correct the user permissions for the user "ramyadav" - i.e. make sure you have read/write access for everything in the "ramyadav" directory and below.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Chief Customer Advocate

  • 10757 Posts
  • 809 Reply Likes
Photo of Pedro GONÇALES

Pedro GONÇALES

  • 4 Posts
  • 0 Reply Likes
Have no ideia of what "ramyadav" is and how to make read/write access for it!
Photo of Chris Cox

Chris Cox, Sr. Computer Scientist

  • 20280 Posts
  • 674 Reply Likes
According to the OS, that's the name of your user account on your computer.
Photo of Pedro GONÇALES

Pedro GONÇALES

  • 4 Posts
  • 0 Reply Likes
weird cuz thats not the name of my user account!
Photo of Chris Cox

Chris Cox, Sr. Computer Scientist

  • 20280 Posts
  • 674 Reply Likes
Ah, my mistake -- that's the name of the user who was compiling the software, and they baked in the source code path in the error string. The message isn't telling you where the error is, it's telling you what source file the error occurred in. We'll have to follow up with the Premiere Elements team to get their build process cleaned up and provide better error messages.