Skip to main content
Adobe Photoshop Family

195 Messages

 • 

3.6K Points

Sun, Dec 4, 2011 12:19 AM

Lightroom: Why do I get the "file could not be moved to recycle bin" error message when deleting pictures

Quite often when I press Ctrl Back space to delete images, there will be just one that gets left behind with the attached error message

there is no reason given, and no way to address the problem, so its a bit frsutrating to keep leaving images behind.

Any thoughts?

Responses

3 Messages

 • 

80 Points

8 years ago

This seems to happen on every one of my images the work around is fine but then what do I need LR for!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

3 Messages

 • 

80 Points

Up date and more info windows 7 64 bit just upgraded to LR 4.2 from 4.1 and CR 7.2 from 7.1 no change. It does work on my C drive but not F internal drive that's where I store all my photographs. Is there a setting to change somewhere?

3 Messages

 • 

80 Points

I have no idea what happened but suddenly no more troubles. Windows update maybe?

6 Messages

 • 

134 Points

8 years ago

When I have several pictures marked as ‘rejected’ I delete them all by pressing Ctrl + Backspace (Win7, 64-Bit).

Quite often – but not always – the last picture is not deleted.

Instead I get the message “The file xyz could not be moved to the Recycle Bin.” I hit Ctrl + Backspace again and this picture is deleted without problem.

The pictures and the Lightroom catalogue are on an external USB-Harddisk.

This reply was created from a merged topic originally titled
Lightroom: Last picture of several rejected pictures is not deleted.

2 Messages

 • 

70 Points

8 years ago

I've experienced this in LR 4 & LR 5 on Windows 7. I'm using an external USB drive.

Each time this happened I wasn't able to delete the file via Windows Explorer as well. I could edit files (I store metadata in side car files) but not delete.

I ran the Windows disk check tool and it corrected file descriptor errors. I was then able to delete files both via Windows Explorer and Lightroom.

So my suggested solution would be to run the Windows built in error checking tool.

19 Messages

 • 

320 Points

8 years ago

Yes, a side effect of running the disk check tool is that it forces all files handles to be closed ( and THAT is the problem: LR still has a file/search handle to the file or folder ). So yes, that might work but it's like using dynamite to kill a mosquito...

2 Messages

 • 

70 Points

8 years ago

Lambert, that is curious as I even have tried ejecting and remounting the hard disk and deleting other files that aren't under Lightroom's control via Windows Explorer and I get an error indicating the files are corrupt. The disk check/repair lets me delete those files too. So while that might be like using dynamite to kill a mosquito, it might also indicate to me that the problem is outside of Lightroom's control and perhaps they should be using better error messaging.

19 Messages

 • 

320 Points

8 years ago

If you can't delete a file using Windows Explorer after the disk has been mounted then the disk is indeed corrupt and then it is a good idea to repair it :-)

In my case, and I suspect in most cases reported here, however, that is not applicable.

1 Message

 • 

60 Points

8 years ago

This worked for me:

Close Lightroom and run it as Administrator. To do this, right-click the icon and choose "Run as Administrator"

Seems that some of the files needed Admin-level credentials in order to be deleted.

1 Message

 • 

60 Points

You are a savior!

5 Messages

 • 

124 Points

7 years ago

This is ridiculous. The bug, and it is a bug, has been around for at least 2 full versions and still occurs on 5.2. If I mark several photos as rejected and then "delete rejected photos" it normally fails to delete the first one with this "can't move to recycle bin" message. The photos are on an internal hard drive. I don't need admin privileges to delete the file. I can get LR to delete the offending photo via the delete key.

195 Messages

 • 

3.6K Points

7 years ago

It amazes me that the lightroom team think it more important to add all sorts of "bells and whistles" function that hardly anyone uses, but will NOT address long standing highly frustrating faults like this, even though they affect every single user day after day.

Adobe like to trumpet the fact that they listen to their clients but the evidence does not support it.

Champion

 • 

2.6K Messages

 • 

33.7K Points

7 years ago

LR is multi-threaded, meaning that it is doing several things at once.

The cannot-move-to-recycle-bin message happens when LR is busy building/retrieving a preview or checking/writing the metadata for one of the photos that you’re asking to be deleted.

If I remember, the delete-rejected-photos first filters for and selects all the rejected photos, and this change in focus causes the preview of the first selected photo to be retrieved and perhaps some thumbnails to be refreshed, which in turn causes the photos to be busy for a short while, and so the delete is blocked from at least one of them, depending on the speed of the computer being used.

The delete key appears to work because enough time has passed for whatever background operation was using the photo to have been completed so it is no longer blocked.

As a programmer, myself, but one who is not privy to any Adobe insider information, it would seem that there would be a way to fix this issue, at least the most common case where preview/metadata manipulation blocks a user-initiated delete operation.

5 Messages

 • 

124 Points

7 years ago

It may well be a threading issue. I was a programmer, retired now, and I wrote plenty multithreaded code over the years. I know what my users would have said if I'd had a bug like this and I'd said something along the lines of "It's multithreaded - what do you expect".

It's a bug, it affects day to day use of the UI and it needs fixing. This has been going on for years. If they can't fix it they're in the wrong business. If they can't be bothered to fix it their support is a disgrace.

Having said all that I remember from decades ago there was an explanation of an error in IBM's DLI database software which said something along the lines of "There are many millions of paths through the DLI modules. Sometimes one will cause an incorrect execution of the logic". IE - tough bananas.

Champion

 • 

2.6K Messages

 • 

33.7K Points

7 years ago

I would expect there is a solution, since the cause is known, but the task prioritization doesn't allow it to be addressed.

5 Messages

 • 

124 Points

7 years ago

That puts it in the "disgrace" category then ;) Don't forget,

(1) this "can't move to recycle" bug has crossed major releases and has been reported since at least 2007, admittedly in slightly different guises. It has been reported on Macs and Windows versions.

(2) it affects, in a very visible way, the library functionality of LR, one of it's major selling points.

I can live with the thing, as I have too much effort invested in LR, but it annoys me every time I process new batches of photos and clear out the non-keepers. I also think that it's indicative of very poor customer support.

1 Message

 • 

60 Points

a year ago

SOLUTION: 

This fixed my issue, but there may be many causes.  

    CAUSE:  Lightroom was opened with user account  (BOB) permissions, but the photos were owned by the 'root' account. 

    FIX:    open terminal,  navigate to folder with photos.    run these two commands. 
               sudo chown -R BOB:staff *
               sudo chmod -R 777 *

From LR's perspective the OS function to delete files fails, it would be possible for them to add different error messages based on the return code given.