Skip to main content
Participant
December 26, 2013
Question

Photoshop Elements 12 has stopped working

  • December 26, 2013
  • 29 replies
  • 14911 views

When I click on the photo editor the main screen comes up and then I get the following error. "Photoshop Elements 12 Editor has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I am running Windows 7 Home Premium, 64 bit.

    This topic has been closed for replies.

    29 replies

    Participant
    November 7, 2016

    mine is with photshop elements 13, installed for first time and same problem- Adobe Photoshop elements 13 has stopped working...

    beansterbean
    Participant
    August 27, 2015

    I'm on a MAC and Photo elements also continus to kick me off.  The only way I can continue to use this program.

    Close out of photo elements, right click the picture you want to open and then select photo elements and it should work.  If I open photo elements first and then the picture I want- it will shut me out.

    Participant
    July 30, 2015

    I had the same problem, but this fixed it immediately. Worth a try. Since upgrading to windows 10, my photoshop and lightroom refused to load too, but reinstalling the suggested software shown solved the issue with all 3 pieces of software. Hope this helps

    Participant
    September 12, 2015

    How do I find the files to re name them? To see if that will work. I'm having the same problem.

    beansterbean
    Participant
    September 12, 2015

    Jackel,

    I nomally just drag the photo I am working on to my desk top and left click photo and them right click and open with photo elements. (never open photoshop app first it will open

    when you chose it from your "open options"

    If I am not able to find a photo I search using finder (I own a MAC) I find the picture I want. DO NOT OPEN PHOTO SHOP ELEMENTS FIRST.

    I click mouse over the file (left click mouse and it will darken) I then right click mouse and it gives me options. Go to: "open with" click mouse on top and then click right click

    on photo elements.

    This will open photo elements in a different way and for whatever reason, it allows me to work on that photo. If you want to open more than one photo while in photoshop,

    You must continue to open ALL other files in the same manner.

    To open another one while photoshop is open, you will need to hide photoshop.

    To do this:

    Above tab: Click photoshop, It will offer "hide photoshop" Click that option. Repeat above.

    Save work as you go a long just incase it shuts down on you.

    If you have a lot of photos in one file, darken them all and "open with photoshop" and open them all up at the same time.

    Just never open with photoshop while you are within the program or it WILL shut down.

    Does this make any sense?

    miked0808
    Participant
    July 2, 2015

    Just had the problem. Came here because i had some poor experience with Adobe chat, twice over a known issue which affected registry entries ... anyway, renaming the two files as suggested worked for me so i figure reinstalling will also work but renaming is faster. FYI programdata is a hidden folder so go to root directory C: then search for the two files manually then rename to *.old ifn case you rather avoid unhiding the folder first

    carlosb50573339
    Participant
    June 25, 2015

    Sorry, dont have time to read this whole thread, but I rmoved microsofts malware software (sorry forgot the name) because I imagined it conflicted with Avast. Reinstalled Photoshop and everything seems to be fine for now.I hope you get the idea and that it helps. I now must rush away to do something else. Good luck.

    marruizsolanes1
    Participant
    June 23, 2015

    I have the same problem since yesterday...its not even opening...

    Participant
    June 18, 2015

    Hi,

    Maybe not solution to your problem but following worked for my Adobe Lightroom, part of the latest Photoshop CC, which continually failed to open during first month of my subscription.

    The Photoshop worked fine. An update for PS failed to worked recently and having googled it , I saw that someone suggested disabling McAffee Realtime scan and firewall during setup. This finally solved both problems and voila, all's working great !

    Best of luck, in any case.

    PMcm

    Participant
    May 7, 2015

    Just recently started having the same problems with Elements 12 under Windows 7. Tried the fix suggested by Dina's Forum, where she renamed the two files,

    C:\ProgramData\Adobe\Photoshop Elements\12.0\ThumbDatabase.db3

    C:\ProgramData\Adobe\Photoshop Elements\12.0\Locale\en_us\MediaDatabase.db3

    and let it rebuild them and so far it is working with no problem. It was shutting down ever 5 minutes or so. As a bonus, Elements also seems to start up faster.

    Participant
    June 11, 2015

    Renaming those files didn't work for me. The app crashed immediately after rebuilding the files, just as it was doing before at startup.

    golddawg
    Participant
    December 14, 2014

    Hi dldc2 - I did roll back my Windows 7 updates a couple of times and that fixed the problem temporarily.  The problem with that approach is it really isn't practical to stop taking Windows updates - you'll be missing out on key security fixes etc. and there is no way to tell which update is (if any) causing the problem.  It does however, seem like the problem is a conflict between Windows and PSE12.  I was able to get my PSE 12 to work once again by removing and re-installing (twice!) and it finally worked.  I also found there was a PSE12 update that I needed to manually install from the Help/Updates menu in PSE12.  At least for now, it's working fine.  But I've thought that before too so we'll see how long it will continue to work.  Good luck to everyone - it's great software when it's working!

    December 13, 2014

    Did you have a Windows update?  Our Photoshop Elements 12 stopped working after one, showing the same message.  We restored the computer to a point before the updates (and made sure to turn off the automatic updates).  That took care of the problem