Skip to main content
Known Participant
June 20, 2010
Question

Lightroom 3 freezing when using import

  • June 20, 2010
  • 25 replies
  • 29912 views

Whhen attempting to import images from an external USB hard drive Lightroom 3 freezes.

The import bar goes across and Lightroom import about 3 images before freezing.

If I close Lightroom and re-start the import it'll import a few more images and freeze again.

Any ideas?

    This topic has been closed for replies.

    25 replies

    Participant
    July 25, 2010

    I have no issues with 2.7 and thought it was a great product. Import works fine. I purchased 3 and now, Import freezes regularly and Lightroom crashes with an unexpected application error. I'm running XP SP3. I have norton [I notice people suggest in may be a firewall issue] - I am going to revert to 2.7 and seek a refund on the upgarde to 3.0.

    Known Participant
    July 25, 2010

    And still no official response from Adobe.

    If Adobe cared for their customers they would at least say something.

    They've got our money and that's all they care about.

    Ian Lyons
    Community Expert
    Community Expert
    July 25, 2010

    Richard4911 wrote:

    And still no official response from Adobe.

    If Adobe cared for their customers they would at least say something.

    They've got our money and that's all they care about.

    Post 54 of this thread has a link to another related thread. The OP for that thread resolved the problem and was contacted directly by Adobe.

    http://forums.adobe.com/message/2981433#2981433

    July 13, 2010

    SOLVED ! (at least for me...)

    Rule of life: Some of the easiest solutions are often the harder to find.


    Here how I did to correctly import all my photos in one shot:

    1- Disconnect from internet

    2- Shut Down Anti-virus and Firewall

    3- Import.

    4- Restart Anti-virus and Firewall.

    I'm using BitDefender2010.

    Participant
    July 16, 2010

    i've the same import problem as others - you can watch the program labouring flicking through folders and drawing the import grid.  i just tried the disabling firewall and antivirus and didn't help me (although i'd already put my photo folders in the 'miss list').  Perhaps this is just adobe's way of telling us all to slow down. ho hum.

    Participant
    July 13, 2010

    I had this same problem as have a lot of other folks on a camera forum that I use.  I resolved the problem three times on my Win XP SP2 setup.  I use an internal multi-card reader connected to a USB2.0 root hub.   I never had any issues with LR2.x.  I went through and disabled all the USB devices in hardware manager and then re-enabled the one to which the card reader was attached.  I could then import photo's just fine, but still a little slower than previously (15 minutes for 4GB CF card as opoposed to 10 minutes).  After rebooting ... problem returns since windows tries to re-enable the USB hubs.  Problem manifests as very painfully slow rendering of previews, and then seemingly hung on import process .. perhaps one or two images load in a 60 minute run.  I have tried tethering the camera to the PC via a separate USB port (USB 3, USB 2, and USB 1 were tried) and it makes no difference.  Copying files directly works fine - so long as I have not tried to use LR3 to read the cards on import.  After trying to use import the card reader is stuck in snail mode, even for Windows usage.

    July 13, 2010

    Does anyone have a clue to what Adobe support is doing? Are they on Summer break?

    The loyal followers of their products have been shat on and they don't know what to expect......just damn.

    TheDigitalDog
    Inspiring
    July 13, 2010

    Charbinjr wrote:

    Does anyone have a clue to what Adobe support is doing? Are they on Summer break?

    The loyal followers of their products have been shat on and they don't know what to expect......just damn.

    The team may have taken a few days or so to decompress after the release but I can assure you they are working their little tails off as usual. And the bit about being shat on is not at all fair. While some are having issues, the vast majority of us are importing with no such issues. Gathering as much information about your system, files, procedures that produce the issue will go farther in getting this resolved than being insulting.

    Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
    Participant
    July 13, 2010

    It sure seems to me that Adobe has screwed up

    big time. I was using LR 3 beta without a problem importing my images from a portable harddirve

    . I just loaded up LR 3 and I have had the same horror story as in this thread. Can't Adobe

    re-establish their beta version and provide it to all of us fools who spent their dime to

    buy the new and improved LR 3?? I like others would like to be able to process my images, particlularly those previously uploaded via LR!!

    Come on Adobe....you have a loyal (??) following waiting for a solution!!

    ERR

    Participating Frequently
    July 5, 2010

    On July 4, I imported and edited some photos. Upon closing down, Lightroom asked and I granted it permission to back up my catalog-- first time ever. Today, when I tried to import additional photos, the import bar appeared upper left but no actions ensued. The import window didn't appear-- just nothing. I clicked the "X" and received the message that the import was cancelled. This is similar to some other posts here. I deleted the backup, but that didn't help. I created a new catalog and tried to import photos-- no dice. I reinstalled Lightroom-- repair installation without deleting the program-- and restarted my computer (as requested) and now import works fine.

    I suspect that something went wrong when Lightroom backed up my catalog. Try reinstalling the program and that may help you as well.

    Participating Frequently
    July 6, 2010

    Hi PhotoSteve,

    Try reinstalling the program and that may help you as well.

    Yes perhaps that will help and I will try it, but your import may be working as a result of the re-boot as well. Please advise iof Import works after a day of normal activity on your computer. Thanks...

    Michael

    July 6, 2010

    Various problems with the Import function have been documented in these forums since LR 3.0 was released about a month ago. Adobe has certainly taken note and are undoubtedly working hard on the problem.

    A few related questions for Adobe staff:

    - Does Adobe have enough bug reports and user data to identify the issues?  Should we keep sending more reports in (and spend time developing ways to get around the bugs), or should we be patient while a patch is prepared? I don't mind helping to debug the issue, but don't want to waste my time if Adobe has a handle on it.

    - Is there a time frame where we can anticipate a patch?  I recently moved from LR2.6 (which was working great) to 3.0; should I reboot my comuter every time I want to import images (almost daily occurence), or do I go back to LR2.6 until the patch comes out?  i.e. should we expect an answer within a week or so, or is this a month (or more) away?

    rob

    Known Participant
    July 5, 2010

    I've now noticed a new problem with the import function...

    I had moved some images that were in a folder within another folder in my collection and showed up in Lightroom 3.

    I then amalgamated all of the images to the main folder.

    Lightroom then couldn't find them and as per Lightroom 3 I chose to tell Lightroom 3 where they were now. This function doesn't work at all and I ended up going in circles until I gave up.

    I then decided the best option might be to remove the images Lightroom couldn't find and chose to remove (not delete) them.

    Went to the import function to re-import the images and Lightroom can't see them. I've checked with 'My Computer' and they are there but Lightroom now doesn't see them.

    I'm now left with about 50  (or so) images that I can't get back into Lightroom 3.

    I think I'll go back to using Lightroom 2.7 as (obviously) no one did any checking if Lighroom 3 worked correctly prior to it's launch.

    This perhaps the worst product launch ever and I''m not amused one little bit!

    And no word from an official Adobe source either; customer service eh?... NOT

    July 5, 2010

    I've noticed this "feature" myself in my newly-purchased Lightroom 3. I tried to upgrade my LR2 catalog, which apparently worked at first. Then I tried an import, and LR3 suddenly decided to not do anything else. I tried to exit LR3, which then beachballed. Force quit, and suddenly my catalog is entirely corrupt.

    Created a new catalog, fresh. Ran an import in Add mode. Went about 95% of the way. Stopped. Same thing -- import halted, and any attempt to close the app corrupts the catalog.

    I've lost a bit of work here with all of this, and I am supremely disappointed in Adobe's software at the moment. Locking up a catalog file so that it has to be deleted?? Not swift.

    I've logged a bug report with Adobe, but if anyone knows of a workaround for this, I'm all ears!

    TheDigitalDog
    Inspiring
    July 5, 2010

    G. Sowrey wrote: Same thing -- import halted, and any attempt to close the app corrupts the catalog.

    Any possibility you can figure out what file it was trying to import just before it took a dump? If you remove it, can you import? Might have to split the import into two or three groups too. I seem to recall the issue I had was a file that was somehow flaky that LR didn’t like which stopped the import process in its tracks.

    Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
    Participant
    July 2, 2010

    I just bought 3 and have not imported yet.  I did use the beta and noticed that it seemed to lock when you imported and renamed files at the same time.  Only work around I found was to import the files without renaming.  Then after they are imported rename them

    July 2, 2010

    I must ring in with the same complaint/observation. Ever since upgrading to LR3, I have had to restart import routines multiple times if not everytime.

    On another note - why can't I see a cursor in this Reply document. That makes editing a real challenge!

    Participant
    June 29, 2010

    Just installed Lightroom 3 after using Lightroom 2.6.  Using the old Lightroom 2 catalog files, no problem.  When I tried to import other image files, Lightroom 3 freezes requiring a hard shutdown.  I thought that maybe I didn't wait long enough, so I tried again and let it set for 4 hours.  When I came back, it was still non responsive.  I have been able to get it to give me a list of files to add, but when I tried to select one, it would freeze.  It appears that the Import function is totally broken.  Anyone have any suggestions?

    Participant
    June 30, 2010

    I have today had success with importing the dngs created with camera raw

    4.6. When I export a dng from LR2 using camera raw 4.6 I am able to import

    the files into LR3. Crazy but its the only work around I can find at the

    moment. I am looking forward to the fix for this....

    Am 29/06/2010 02:57 schrieb "tigerhorn" unter <forums@adobe.com>:

    Just installed Lightroom 3 after using Lightroom 2.6.  Using the old Lightroom

    2 catalog files, no problem.  When I tried to import other image files,

    Lightroom 3 freezes requiring a hard shutdown.  I thought that maybe I didn't

    wait long enough, so I tried again and let it set for 4 hours.  When I came

    back, it was still non responsive.  I have been able to get it to give me a

    list of files to add, but when I tried to select one, it would freeze.  It

    appears that the Import function is totally broken.  Anyone have any

    suggestions?

    >

    Inspiring
    June 30, 2010

    I was able to import two sets of images today - one of about 500 .dng files, the other about 600.

    It APPEARS that as long as my catalog is not hitting any corruption or trying to import an image that's already there, it works ok.

    For whatever reason, it seems like my problem was somehow related to the synchronize.