No, it’s really the folder in Application Data. And it’s not hard-set to C, it’s hard-set to whatever paths you used in your previous installation. Thus if one reinstalls Windows after an HDD upgrade that brought about some relevant path changes, all PSE’s Application Data break. Unfortunately, the files don’t seem to be simply editable, so you’re likely to say goodbye to all your old preferences, presets etc., or so I expect. What a shame anyway.
No uninstall/reinstall necessary, just delete anything in the folder “Application Data\Adobe\Photoshop Elements”.
Thanks to all the posts - I had almost given up trying to install Photoshop Elements 5 on my 64-bit machine. I deleted the folder as described above, and was able to open and use Editor - Yeah!! In Vista, I found the application folder at: C:\Users\(your name)\AppData\Roaming\Adobe\Photoshop Elements\5. Just delete the entire 5 folder.
I still have an issue with the Organizer though. When I try to click on the Organizer icon from the Editor window, I get a solid, bright neon green blank screen covering my entire monitor. The app freezes and I can't even navigate out. A Windows message does appear in a bubble near the systray and says "The color scheme has been changed to Windows Vista Basic. A running program isn't compatible with certain visual elements of Windows." Does anyone know how to resolve this lovely?
CANNOT LOAD FASTCORE ROUTINES, MMX CORE ROUTINES,
MULTIPROCESSOR SUPPORT NOT FOUND
SUCCESSFULLY REPAIRED - STEP BY STEP
I made the repair for Elements 5 on an XP version Operating System PC by doing this:
I went to....
Start / All Programs / Accessories / Windows Explorer
My Computer / C:
which is my drive with its operating system where Photoshop is installed.
I then clicked....
Documents and Settings
Then - in each - of the three icons I found.....
All Users, Default User, and Owner
I went into....
Application Data / Adobe / Photoshop Elements
In that last file I removed ALL the contents.... IN EACH !
After rebooting, my Photoshop Elements 5 started to work.
I think with research and all I invested five hours. May this save you 4 1/2.
I was paranoid and put the contents of each file into a new file I identified
clearly in case it I have to replace one of the parts out in the future.
I hope this is of help to some future reader.
Other comments here seem to indicate that this solution has
worked in version 4 and up and fixed early versions of Vista.
This appears to be a common problem after a drive repair or partitioning.
Why they can't just tell us this is a mystery to me.
-- Bon Courage! --