Workarounds for Lightroom crash on Import...

Issue description
When importing or synchronizing folders in Lightroom 4, the application becomes unresponsive and Windows reports it as not working.
Event Viewer logs the following detail.
Event  Viewer
Faulting application name: lightroom.exe, version: 4.4.0.11, time stamp: 0x514b016c
Faulting module name: wpdmanager.mox, version: 0.0.0.0, time stamp: 0x48a324a9
Exception code: 0xc0000005
Fault offset: 0x000000000001f885
Faulting process id: 0x24dc
Faulting application start time: 0x01ce745df5ec4da5
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.4\lightroom.exe
Faulting module path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.4\moxplugins\wpdmanager.mox
Report Id: 360e1014-e051-11e2-9613-fca983d8aa44
Workaround
The following items each prevented the issue from occuring.
Unplug phone (android - Samsung Galaxy SII) from USB port or
Unlock phone.
My guess is that the Import... and Folder synchronization operations invokes Lightroom to scan all storage devices including USB attached devices. Lightroom seems to choke on connected devices that has an empty volume list.
Workaround #1: Unplugging the phone removes the device from the list. Lightroom only has to deal with C:\ and D:\ partitions which are hard disk drives.
Workaround #2: In my case, unlocking the phone will allow Windows to list available volumes on the device. Lightroom probably does not know how to handle scenarios involving connected devices that has empty volume sets. Some devices may need more interactions to allow Windows to list available volumes. For me, leaving the phone unplugged was an easier workaround.
Phone lock state
Volume List Screenshot
Lightroom crash event
Locked
Issue reproduced
Unlocked
Issue not reproducible
Investigation
To investigate the issue, I reproduced the issue using procmon.exe and filtered the trace to include events with Process Name = lightroom.exe.
Scanning the trace from most recent events to oldest, I noticed a RegQueryValue operation that resulted in NAME NOT FOUND. The detail that caught my eye was that the path included "SAMSUNG_ANDROID" which indicates Lightroom is doing something that involves my Samsung Galaxy SII phone that was connected via USB -- I don't know what and why.
As a wild trial-and-error test, I unplugged the phone. As a result, the issue could no longer be reproduced -- workaround #1.The second workaround was discovered after a few minutes of trial-and-error. I don't remember what my thought process was and am currently too lazy to type any more.
If this write-up helped you, awesome. If you have a similar issue but a different workaround, please share it!

Great!
I had the same issue, that could be resolved by your suggestion.
Actually, I renamed the module wpdmanager.mox to kill it's activity.
Disadvantage of this is that you will not be able to import files from SD card, but I copy to HDD using explorer anyway.
I totaly agree with your conjecture.
Tak

Similar Messages

  • Workarounds for project crashing when exporting?

    I have developed a project in captivate 6 which is now crashing captivate when I export it.   I can preview it in 'Web Browser' and 'HTML 5 output'.  But when I export it as a SCORM package it crashes.  I was able to do that yesterday but today it's crashing.
    Any suggestions?  Any one?
    Slides contain nothing fancy except just mp3s, text and graphics.
    Specs
    Captivate 6 project
    Tested on both Mac and PC
    From,
    Luke L

    Hi Luke,
    In Project Preferences, Start / End there is an option preload startscreen.
    Best regards.
    Philippe
    Le 15 oct. 2012 à 21:48, Luke L PSA <[email protected]> a écrit :
    Re: workarounds for project crashing when exporting?
    created by Luke L PSA in Import/Export - View the full discussion
    thank you tchiboo.
    Which start screen is this?   Thanks for the help desperate to know.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4775908#4775908
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4775908#4775908
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4775908#4775908. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Import/Export by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Lightroom crashes on import with Samsung Android Phone plugged in USB

    I went to import some photos taken on a Samsung Galaxy S3 phone into Lightroom 5.5 via USB.  Plugging in the phone with import selected or selecting import with the phone already plugged in crashes Lightroom, every time.  Now, I can copy the pictures to the computer and then presumably import them, but Lightroom shouldn't crash when a smartphone is plugged in...

    Funny I should find this post on my first web search - I just updated from v5.4 to v5.5 only 10 minutes ago and *BLAMMO*  . . . Lightroom crashes as soon as I hit the Import button when my Samsung Galaxy S III is attached via USB.  This is on Windows 7 64-bit.
    Lightroom v5.4 has been happily importing files from the same phone all along, so something has regressed in v5.5, it seems.  Importing from a USB storage device should be relatively straightforward.
    EDIT: I uninstalled v5.5 and reinstalled v5.4 - it imports without problems using the same scenario that crashed v5.5 above.
    Little help, Adobe?  Please?  I'm willing to send logs, test various scenarios, etc.

  • Lightroom Crashes on Import

    I am using lightroom 2.2 on Windows XP and it crashes the instant it tries to import a file from a disk. What should I do?? It worked perfectly when I used Lightroom v1

    Hal
    The graphics card is a NVIDIA GeForce 7600GT
    The obvious recent change has been the inclusion of a 2nd 1TB HDD. Now the application sits on the original HDD and the photos and catalogue sit on the new 1TB HDD - everything has been migrated across. I can read all the old files from the new location I just cant load anything new. It was working with this set up previously however.
    As for the previous version of Lightroom - its deleted. I also dont use photoshop. Not sure how to get a 115MB file to anyone else - I am just a home user - I dont have a web page - and I am not a tech head - unfortunately all I can say is that it doesnt work simple as that.
    Cheers

  • Very Slow preview rendering for lightroom 5 on import

    I am seeing very very slow rendering of preview images only when using the import function in lightroom 5. By slow, I mean for a shoot of 60 shots in raw, it could take 30 minutes before I can preview them all in the pane to see which ones I want to actually import. This was not an issue with lightroom 4. It is not an issue when using lightroom. Previews are fast there, even for images I've never pulled up before.
    My hardware is a PC, with an intell i7 chip, and 16 gig of memory. My nvidia graphics card has the latest drivers.
    I've seen a few others reporting this issue, so I'm trying to log it as a bug. Even though the dial up support text on the adobe lightroom says available 24/7, it now plays a voice recording that says only available m-f.
    Brad

    I'm having the same problem using Windows 7 (64b). I just took a shoot over the weekend for a significant birthday event. Now I can't load the photos. The work-around doesn't work as the program freezes before I get the chance to select the camera under "files".
    I recently upgraded from 3.6 to 5 as I was also noticing a slowdown in the import function. That turned out to be a bad move I think. I also deliberately cleaned up the CF card and removed all my video recordings, as this seems to be reported as part of the problem, but to no avail.
    This seems to be a pretty major bug to have in a major release that's been around for a while now, that I'm expected to pay for, and no sign of a resolution to date!
    Cam. 

  • Lightroom Crash on Import with CS3 installed

    The last two days, I have been importing fairly large shoots from CF cards with Lightroom (Yesterday 147, today 79). In both cases I have received the Adobe Photoshop Lightroom has encountered a problem and needs to close.." message; twice today. I installed Photoshop CS3 Release yesterday and now I have Bridge trying to import the same set of photos. I noticed the Bridge import dialog today after LR crashed. By sending off the debug message and restarting LR I can finish the import eventualy. It shouldn't be this way and wasn't before I installed release CS3 (I had had LR and Beta CS3 on my machine with none of these problems.

    Hi Holley,
    Just back from a long weekend, hence the delay in replying..apologies.
    Since I have now fixed the problem, I cant remember exactly how I sorted it, because I just stumbled through the various menus until I found the right solution! But, heres what I think I did:
    Open TweakUI.
    Open the drop down menu next to My Computer.
    Click on Handlers.
    In the window next to the menu, highlight Open folder to view files using Windows Explorer.
    Click Edit.
    Tick whichever boxes/tasks you would like to add to this folder. Obviously, the last one, Digital Images, will be one of them!
    Click OK.
    Thats it!
    Note: There is no option to Take no Action. Once you have added any of the menu items, this option is added automatically by TweakUI.
    Now, when you put a card in your card reader, the window should open with the option, Open folder to view files.
    If this isnt working, reply and Ill try again.
    HTH.
    D.

  • Workaround for Mozilla Thunderbird users - importing contacts

    I use Thunderbird (Windows platform) for e-mail and contact management, and I did NOT want to switch to Outlook. I first tried exporting my contact list from Thunderbird as a .csv file then importing into Outlook 2000. When I found out that Outlook 2000 was not supported, I tried importing the .csv file into Outlook Express which is supported, but with no success. The final (not very elegant) solution was to first import the file with Outlook 2000, export a new .csv file and import using Outlook Express. I then went back to iTunes, changed the sync setting to "Windows Address Book" from "Outlook", and the sync worked. I am not sure if importing into later versions of Outlook could eliminate the need for the Outlook Express step. I know that this is nto a practical long-term solution, but for now I was able to get my contacts to the phone. Hopefully someone will find a more direct answer, or Apple will add Thunderbird and Firefox to the sync options.
    Windows Box   Windows XP  

    Having given up someone suggested a solution which works, albeit tediously. In summary the process for 10.3 (it was suggested 10.4 was different) is:
    Import messages into Mail from OE.
    Find imported files in Mail's Mailboxes folder. Make a copy and work on that.
    In turn control-click each .mbox file and choose 'Show Package Contents'.
    From window that opens move the file named mbox to your profile folder in Thunderbird's Profiles folder. (In practice it was simpler to rename each mbox with the name I wanted that box to have before moving it rather than rename it as soon as it was in Profiles.)
    Restart Thunderbird.
    Check structure against Mail (assuming you worked on a copy) or OE.
    Depending on any folder structure you used in OE you need to check exactly what it is you are moving. With hindsight it might have been better to move the mailboxes across in a flat structure then create any folders.
    Importing addresses failed again. I was pointed to a free utility called Address Book Exporter which creates a .txt file from Address Book, that was easy to import into Thunderbird but although cards were created all had some/all information missing. I have given up on that!
    Michael

  • Lightroom 4 crashes on import

    Windows 7, Home Edition, version 6.1 service pack 1
    Intel 7, with more than 400gb memory available
    I've now spent more than 32 hours trying to solve this problem, including two phone calls and three chat sessions with Adobe Help Desk.  The Help desk takes me through the same checklist of "fixes" as the previous calls and inquiries and has resulted only in wasting more hours of my time. 
    To date I have tried the following to fix this issue:
    - uninstall and reinstall with and without the LR 4.1 update
    - create a new administrator account on my machine and run LR off the new account instead
    - create a new catalogue for every import (which kind of defeates the purpose of having LR to begin with)
    - wipe out my old preferences file and allow LR to create a new one
    - completely wipe my hard drive and reinstall EVERYTHING all over again
    - rebuild my catalogues from scratch on a new, fresh install of lightroom
    - limit my cache size in LR preferences
    - limit my backups in LR preferences
    - change my 1:1 previews
    - attempt to import images from a Nikon 90, D3s and D800 only, each on a fresh LR install (in an effort to see if it was a particular camera model causing the issue)
    - attempted to only import directly from another hard drive, rather than an external or internal card reader
    Each time I have no more than a day of proper working conditions before the program hangs up and windows pops up a warning that the program has ceased to respond and must close.  Lightroom is rather useless if I can not import images.
    I'm out of solutions or fixes, and out of patience now too.  I'd really like to continue using Lightroom products because of how integral it is to my workflow.  At this point I'm ready to switch to a competitor if this issue can not be solved.

    Hi Dave lorde,
    Do you get an error dialog for Lightroom crashing?
    Also which version of Lightroom are you using? Have you tried with Lightroom 4.4 yet?
    You might also try downloading the Lightroom 5 beta that is available now on labs.adobe.com and see how it works on your system there.
    As for the current issues, my suggestions are as follows:
    0. Make sure you're up to date with LR 4.4 or LR5 beta
    1. Take a look through our performance optimization documents for Lightroom and see if any of these suggestions give you something to work with:
    Optimize LR performance
    http://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html
    Performance Hints
    http://helpx.adobe.com/lightroom/kb/performance-hints.html
    2. Try resetting Lightroom's preferences: http://helpx.adobe.com/lightroom/kb/recover-catalog-images-resetting-lightrooms.html#id_90 046
    3. Try Lightroom in a new administrator user to see if the hangs continue.
    Let us know how it goes,
    regards,
    Pete

  • 10.2 crashes when I try to convert old libraries for use in the new software. Is there a workaround for this? Or will i have to continue using the previous version to complete older projects?

    Final Cut Pro X 10.2 crashes when I try to convert old libraries for use in the new software. Is there a workaround for this? Or will I have to continue using the previous version to complete older projects? the only foreseeable solution is to begin any new projects on 10.2 or importing footage on 10.2 and starting form scratch--which is something i definitely don't want to do or have time to do. ANY advice, thoughts, or opinions would be greatly appreciated! Thank you!
    Running 10.10.3 // MacBook Pro (Retina, 15-inch, Early 2013) // 2.4 GHz Intel Core i7 // 8 GB 1600 MHz DDR3

    Exactly the same problem with me.
    Some other threads advice to remove fonts, clean the caches, remove add ins but nothing works consistenty, for some it looks like it works, for me it failed.
    What I did not try yet, was to move the Render files out of the malicious library to trash.

  • Any direct installer for Lightroom?  Adobe Application Manager crashes every time (Mac OS 10.9.4)

    I'm trying to migrate from Aperture to Lightroom.  Needless to say the existing help documentation assumes the installer software doesn't crash!
    When using this page:
       https://creative.adobe.com/products/download/lightroom
    The only download link I can access is:
       aam://SAPCode=LTRM?productVersion=5.6?passPhrase=dlC9juiw9Uf9g+Vks1IUflaugqLAqM2EyWucW2/M huZnOYOCur4ZPchERE/PxfIlqFF7/QWRqz+ih8+bvn+J39PlBZwWu33FApnWWqGJO6opmjCzfoFwO73gjpPwAh42tt vFTOwPE+BJB8N6wUFykA/PdAxD9Sn9L2OFSEge5I8=
    Which attempts to launch the Adobe Application Manager to perform the installation.  However, after displaying the loading screen for approximately one second, it crashes.  Is there any way to get a direct download for LightRoom?

    Downloads available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  12 | 11, 10 | 9, 8, 7
    Photoshop Elements:  12 | 11, 10 | 9,8,7
    Lightroom:  5.6| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5
    Contribute:  CS5 | CS4, CS3
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • Lightroom and Vista....Any workaround for memory? - Cause it's slow

    I've searched all over for a soution.   I can not tolerate the lack of responsiveness that Lightroom 3 has when it comes to working on my RAW files.   Here's my system info...bear in mind that I was working on 1 NEF file
    Lightroom version: 3.0 [677000]
    Operating system: Windows Vista Home Edition Service Pack 2 (Build 6002)
    Version: 6.0 [6002]
    Application architecture: x86
    System architecture: x86
    Physical processor count: 4
    Processor speed: 2.6 GHz
    Built-in memory: 3070.5 MB
    Real memory available to Lightroom: 716.8 MB
    Real memory used by Lightroom: 993.1 MB (138.5%)
    Virtual memory used by Lightroom: 1115.8 MB
    Memory cache size: 0.0 MB
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    That's a quad core with 3GB of memory however, Vista only makes 700mb of memory available for lightroom and as you can see, processiong one raw file puts me at over the allocated memory.   Lightroom 3 System requirements call for 2MB of available RAM.  I surpass that but the system requirements don't seem to take into account the Vista memory allocation issue.
    Is there a way, that anyone is aware of, to allocate more memory to lightroom 3?  I can not work at this pace.  I can't even export the processed image as a full size jpg because I get the "not enough memory" error message in lightroom.   I disable all uneeded processes when running lightroom by the way which includes turning off anti-virus.  I usually have my laptop running on the corner of my desk in the event I need to look something up on the web.
    This has become unusable in this current state.  Is this a Vista flaw, a lightroom flaw or a combination of both.  Is anyone aware of a workaround to this issue? 
    Thanks to all that respond.
    Fulvio

    As stated elsethread, 32-bit Windows operating systems can address 4Gb of memory.  In general, out of the box installs will allow user processes 2Gb of that.  So Lr has access to 2Gb for the static application and for the memory it uses at run time. This 2Gb also has to be shared by other processes, so the OS provides virtual memory to let applications grow as necessary, up to that 4Gb limit.
    There are tricks for giving user processes more memory, but there is often a trade-off because of the way Windows segments this memory. One of the trade-offs is that access to the other chunk of memory is much slower, though not as slow as paging. There are other gotchas, too.
    What other processes are using up real memory?  Which ones demand to be paged in from virtual memory (which could slow down other applications like Lr)?
    So, Lr will use memory if the memory manager can give it memory, but it really has to take what it gets.  And some operations are memory intensive, especially on larger raw files.  If the memory Lr is using is being paged, it can result in perceptually slow application performance.
    I'd start with firing up Vista with very little running.  Exit all user applications, and kill services you don't need when working with photos, like real-time anti-virus protection (most of which are nothing more than a panacea that eat up resources and slow down the entire OS) and the search index stuff (which is basically broken until Windows 7) and stuff like that.
    Make sure you make a large raw cache, and put the raw cache on a fast disk that is not the same as the one where your previews are. Buy a cheap drive and format it NTFS just for this purpose, if you have to.  Disk space is cheap, and it can act as a backup for your photos on import. Get rid of all the video/sound/whatever driver cruft that is not the just the drivers. nVidia, et al, love to install toolbar cruft that gives you nothing except higher CPU and memory usage.  You might want to create a new user account that is as clean a possible with all this stuff disabled or removed.
    Lr /can/ work ok in a limited 32-bit environment, but you might have to tune the system a little.

  • Help with Lightroom 5.7 crashing upon import

    Hi,
    I got Lightroom a few weeks ago and ever since I installed it, it has been crashing a few seconds after I open the Import screen. Interestingly, ONE time I was able to get it to import successfully, but the only thing I changed was running the program as administrator, and I've been able to successfully import again using the same technique. I read that this is a common problem, and commonly solved by unplugging one's phone, but I definitely don't have my phone or phone's USB cord plugged in, and I restarted my computer to make sure it didn't think I did have a phone plugged in, and I wasn't able to solve the issue. I unplugged all my other USB devices except for my external hard drive, which is where I'm trying to import my files to. The one time I did successfully import, I imported onto the same hard drive, so I don't think it's that either?gb
    Any help toward solving this issue would be hugely appreciated. Having to copy 30gb worth of files onto my PC and then manually moving them into another folder using Lightroom is a tedious and time-wasting extra step
    (edit: forgot to mention that if I turn off/unplug my camera (D5200), the program no longer crashes on import. If the camera is connected, even if I'm not trying to import from the camera folder and click on another drive, the program will still freeze after a few seconds)

    In Solution 5, I was able to verify that I have "Read & Write" priviledges,
    so that did not help.
    Solution 6 - I'm stuck. It suggests to Copy the Lightroom folder into a new user account or other existing account on your computer.
    Then, restart Lightroom. The Lightroom folder is in the following locations:
    Mac OS: [user name]/Library/Application Support/Adobe/
    I am not that computer literate because this procedure seems confusing to me. I have located the Lightroom folder, but I am lost beyond
    that. I don't know where the "new user account" is or the other "existing account".

  • Lightroom crashes when png fils is used for water mark

    When I use png files, lightroom 5.7 crashes (windows 7 64 bit). With the plug-in Mogrify it works, but not with lightroom itself.The dng fil can be imported into the lightroom catalog without problem. But it cannot be loaded for the identification table (lightroom crashes). I had this issue already in lightroom 4.
    Thanks for any ideas to solve this.

    I opened and resaved the PNG with Photoshop and it didn't crash LR, so it seems your scanner is producing PNGs that aren't quite compatible with Lightroom.
    Instead of me uploading files after editing in Photoshop, you can use an online editor like Pixlr to edit your own PNGs that won't crash Lightroom:
    I used the following steps in Pixlr to convert ABC.png to a transparent background PNG that had black writing then another with white writing:
    Open apps.pixlr.com/editor/ Online Photo Editor | Pixlr Editor | Autodesk Pixlr in a browser, I used IE 11
    Click Open Image from Computer
    Browse to and Open ABC.png
    Double click the padlock symbol in the Layers panel to convert Background to Layer 0
    Select the Magic Wand tool - over at the left
    Turn off Anti-Alias and Contiguous checkboxes up top if necessary because you want all the background removed and clean edges on this B/W PNG
    Click on a white area outside of the letters, notice that the insides of the A and B are also selected because Continuous is turned off
    Hit the Delete (Del) key, notice that the background turns from white to a checkerboard pattern indicating transparency
    Use File / Save... and save this black-letter copy with a new name (e.g.  ABC_black.png) to your computer, somewhere, as filetype PNG - Transparent, Full-Quality
    Use Adjustment / Invert to change the letters to white, notice that the transparency remains
    Use File / Save... and save this white-letter copy with a new name (e.g. ABC_white.png).
    That's it.
    Obviously you can do more things in this editor, but for the simple task of making transparent background PNGs from a scanned PNG that's all you need to do.

  • "Adobe has found a solution or workaround for the recent crash in Adobe Flash CC" ...not really.

    Hi guys,
    My Flash CC crashes all the time, it's always been doing it since when I started using it on CS4, and I've somewhat given up on this bug being fixed, it crashes at least 20-30 times every document I create. I'm using a Wacom Bamboo Fun Pen&Touch tablet and drawing a lot, I think the problem is that it can't handle this much drawing.
    Anyways, it just crashed and for the first time after reopening I found this nice message from Flash:
    "Adobe has found a solution or workaround for the recent crash in Adobe Flash CC.
    Please click here for further details."
    Excited, I clicked on it! At last, a solution! Amazing!
    ...but it just points to http://www.adobe.com/
    ... I don't understand.
    What's happening? I'm genuinely puzzled.
    Also, anybody else experiencing frequent crashes?
    Thanks!
    Ciao!

    Yes, this is not good -- you're already mad when it crashes, then "We found a solution!" But, for me clicking on the link does nothing - no link even to adobe, just a tease - nothing opens.
    It's bad enough crashing a couple times a day and losing work (I do save every chance I get), but then to get taunted with this bogus message, it's discouraging and exactly the best 'user experience' for a really expensive product from company that is all about helping professionals create good design/user experience ..
    I like the way this is headed though! it just doesn't work right now.

  • Lightroom 3.4 crashes when importing folders from local HD

    I'm running Windows 7 32-bit SP1 and have upgraded from Lightroom 3.3 to 3.4 but now when I try to import a folder from my C: drive Lightroom crashes:
    I click on the + sign next to Folders in the left hand panel and click on Add Folder
    I browse to the folder I want to import and select it
    Nothing happens and I then get a message "Adobe Photoshop Lightroom has stopped working" with a Close program button.
    I can see the contents of folders that have already been imported.  I have removed and reinstalled Lightroom but it doesn't fix the problem.
    Any help would be appreciated.
    Lawrence

    If it really failed in ntdll.dll it might be a system issue.  Make sure you disable all real-time anti-virus processes, and make sure your Windows system is up-to-date.
    Otherwise, it will be hard to know what is going on. If it persists, open a support ticket with Adobe. Take a look in the event viewer to make sure you have all the details of the crash.

Maybe you are looking for