LightRoom 5 File move bug.

  • 3
  • Problem
  • Updated 4 years ago
  • (Edited)
Using LR5, In library module, I created a folder on my D drive. I then moved 5 folders from my C drive into the new D drive folder. After moving the folders, it left the original folders in place (but empty) on my C drive. Win7 x64.
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 3
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
Are there any hidden files in those "empty" folders?
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
Rob, I have just checked for hidden files in the folders. There are none. The folders are empty.
Photo of Pete Green

Pete Green, Customer Advocate

  • 721 Posts
  • 136 Reply Likes
Did your images get copied to the D Drive John?
Is the bug that the folders were left over? or was there any data loss?

If it's that the folder empty folder is left over, does this happen when you move between folders on the C: drive? or only when you move between drives?

Are they physically separate drives? or partitions of the same drive?
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
The images did get copied Pete, There doesn't appear to be data loss. The bug is that empty folders were left behind with an incorrect error message now I see.
The C drive is a 500Gb Samsung SSD.
The D drive is a raid 1+0 4 disk setup consisting of 4x1Tb WD red NAS drives.
I have now replicated the problem in the following circumstance and provided a screen grab showing the result.
I copied the White Balance directory from my C drive to my D drive. In LR5 I changed the develop settings in one image but did not save the metadata to disk. I then in library module moved the folder from the c to d drive destination folder. As can be seen, errors occurred, the original directory is empty and the target directory is full although the error message indicates it failed to copy them and as a result, leaves the empty original folders in place.

Photo of Pete Green

Pete Green, Customer Advocate

  • 721 Posts
  • 136 Reply Likes
Thanks for the screenshot John,

I wasn't able to reproduce the problem in my testing -- though I don't have the exact RAID setup that you describe, but I wonder if it would be any different if you ran Lightroom 5 as an administrator and tried again?

Right click Lightroom choose Run as Administrator...

The next step would be to see what happens if you create a new admin user account and try with that user.

blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-most-issues.html#Permissions
Photo of Bryan Pace

Bryan Pace

  • 3 Posts
  • 0 Reply Likes
I'm also getting file moving errors much like John. I upgraded from LR4 which worked correctly to LR5 and am experiencing the following:

When I drag and drop folders in LR5 from my Retina MBP running OS X 10.8.4 to a Drobo Gen 2 running newest firmware 1.4.2 connected via USB2 the image files and xmp files are moved correctly as are the folders, but LR5 gives me an error saying they could not be moved. Everything seems to work without error messages if I move just the images files, not the folders.

Worked with Adobe support last night and found that the bug exists even after resetting the LR5 preferences, using a new catalog and images imported with LR5.
Tried a Lacie Rugged drive on USB3 with the same issues.
Photo of Bryan Pace

Bryan Pace

  • 3 Posts
  • 0 Reply Likes
It also appears that even though the xml files are moved, the changes are now coming from the data in the catalogue, not from the xml files in the directory.

Any ideas?
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
Pete, I apologise for the delay in replying. Urgent business came up. I run my machine as an admin, no difference. I created a new user account called Adobe Test and gave it admin priviliges. I created a new catalog and imorted the white balance folder which was on the D drive. I then attempted to move it to the C drive using LR5. The folder on the C drive was created but no files were moved this time generating an unknown error message.
Photo of Bryan Pace

Bryan Pace

  • 3 Posts
  • 0 Reply Likes
John.. did you contact Adobe support for this issue?
Photo of Allan Olesen

Allan Olesen

  • 64 Posts
  • 6 Reply Likes
I have a somewhat similar issue.

In Lightroom, I move folders from a local drive to a network drive. After each folder is moved, Lightroom comes up with a dialog saying that some files could not be moved.

Every time it was all the non-raw files which could not be moved: .JPG, .XMP and any other files in that folder. The raw files were moved ok.

When I look at the destination folder, all files are there, and they have been removed from the source folder. But sometimes, the .JPGs appears corrupted, though I haven't yet looked into this further.

If I move the folders using Windows Explorer, there are no problems. To be sure, I have even created md5 checksums for all the files before the move and then checked them after the move.

This is LR 5.0 64 bit on a Windows 7 PC.
Photo of seanhoyt-dot-art

seanhoyt-dot-art

  • 283 Posts
  • 45 Reply Likes
This ever going to be fixed? Tired of these empty orphan folders being left behind when I move projects between drives via the LR file tree.