Skip to main content
Inspiring
July 9, 2022
Question

Photoshop Elements 2022 Organizer leaves files in Temp directory

  • July 9, 2022
  • 3 replies
  • 1447 views

When adding a tag to an image, Photoshop Elements Organizer 2022 makes a copy of the image file in C:>Users>[my user name]>AppData>Local>Temp and does not remove the file from this location when the Organizer is closed.  This results in a large accumulation of files in this Temp directory that can significantly affect the amount of available storage on the C: drive.  This problem requires the user to manually delete the file(s) from the directory.  If deletion is not done Windows 10 will eventually display a critical warning about low available disk space .This has been a problem with the Elements Organizer for many years.  I wish someone would fix it.

This topic has been closed for replies.

3 replies

Participant
December 7, 2023

In 2023 the problem still exist. And i'm pretty sure, it will be exist in 2045 too
Why?  Because Adobe doesn't care about users problems...

You hdd/sdd will filled up with unwanted/unnecessary files because the Photoshop is wrong. Also doesn't care where did you set working directories... And just leave its garbage on drive C

The only solution is add xx\username\AppData\Local\Temp directory to Quick access in your Windows and delete all the files manually, often.

Bill JunkAuthor
Inspiring
July 19, 2022

I recently received a generalized e-mail from the "Adobe Support Community" asking if any of the replies helpded me solve the problem I reported.  The basic answer is NO, but I did get one suggestion to use Ccleaner to delete unnecessary files from my C drive.  That did recover around 4 GB of space, but the Photoshop Elements Organizer continues to leave files in the AppData>Local>Temp directory.  One response was essentially telling me that I shouldn't expect Adobe to do anything since there aren't a lot of people reporting the same issue.  There was also another response that was a bit of an insult and chastised me fro even posting the issues since I had already found a workaround and no one else cares about the issue.

 

 

Glenn 8675309
Legend
July 9, 2022

I saw this other comment you made about something simliar 5 years ago--- your previous comment back in 2017 didn't yield any responses.    I would think that if some tmp files are causing you to get warnings about low disk space- then it's time to get another, or a new, bigger harddrive. 

The directory you pointed out, for me anyway, about 34 MB of temp files- nothing I'm worried out--- I could just sort them by file extension and delete them an be done with it. 

What's the total size of the temp files you are concerned about?





Bill JunkAuthor
Inspiring
July 9, 2022
Glen,
I've been deleting the unwanted jpg, tif, and nef files from that directory for years. I'm getting tired of doing that and I don't think that is something that a user should have to do - clean up after a program leaves stuff where it shouldn't. Most of my image files are in the range of about 40 to 50 MB each. I've had 10 to 20 GB of files accumulate there and one time it caused Windows to issue a serious warning that it was running out of space for the OS. That's when I spent a lot of time figuring out where all my C: drive space was going.

Bill
Bill JunkAuthor
Inspiring
July 10, 2022

Having over 40 years of experience in the hardware / software industry, I'd say this is a good example of what can happen when a developer just forgets to take care of removing files / data that's stored some place temporarily while the app is running.  Usually files / data are temporarily stored in a safe "working" place while some operation is being performed.  It could them be used for an "undo" operation or is there as a backup in case something failed.  Files stored deep in the operating system's temporary storage space should not be left there indefinitely.  Good programming practices whould ensure that when the application terminates, the program's design and implementation remove files / data that are stored for temporary purposes .  If the files / data are needed for a subsequent exection of the app, then they should not be stored in a "temporary" file storage location. There's and "Adobe" folder in AppData>Local that could be used for such purposes.  My C: drive is a 100 GB SSD supplemented by a 1 TB conventional data drive (D:).  I also have a 4 TB conventional drive that is used for image storage and a 5 TB conventional drive for backup.  Even if I did replace my computer with one that had a larger SSD, that wouldn't change the fact that Elements Organizer should not be leaving copies of my image files in places were I don't want them or I don't know they exist.  No matter how large the drive, eventually it will get filled up with copies of files that I have stored elsewhere.  As far as I know there is no way for a user of the Organizer to access the files stored in the Temp directory from a feature in the Organizer.  You might be able to argue that what the Organizer is doing won't be an issue for most users of Photoshop Elements who might have a few hundered to a thousand small jpg files in their collection.  I'm now approaching 100,000 images and a large percentage of them were made with Nikon digital cameras, the D700, D800, and D850.  While I could switch over to using Lightroom I've never really liked it and prefer the approach used in Adobe Camera Raw and the layered features of the full version of Photoshop CC.