Lightroom 4.4 64-bit won't start-up; preview cache error

the error message is "Lightroom encountered an error when reading from its preview cache and needs to quit.  Lightroom will attempt to fix this problem the next time it launches"  But it never gets past this screen regardless of now many times I try!

Delete your preview cache. It is a folder whose name ends with Previews.LRDATA, it is in the same folder as your Lightroom catalog. Do not delete anything else. Do not delete the LR catalog.

Similar Messages

  • I get an error that says that LR5 encounterd a preview cach error when trying to start LR5 and that it will try to fix it the next time it starts. What can I do to fix this error?

    I get an error that says that LR5 encountered a preview cache error when trying to start LR5 and that it will try to fix it the next time it starts. What can I do to fix this error?

    Go to the folder with you Lightroom Catalog (usually in Pictures) and delete the folder ending in .lrpreviews
    This contains the previews for the files Lightroom has linked to. They will need to be rebuilt which can be done while working or selecting an amount you want to rebuild and accessing the rebuild command in the Library Dropdown menu...

  • Lightroom 3.2-64 Bit. will not start -It said-opening Catalog:DSC0024.then shuts down

    I have downloaded Lightroom 3.2-64 Bit . When i start the software it gives me the message" Lightroom-opening Catalog:DSC0024.JPG.Ircat"
    Then a window opens and said " Adobe Photoshop lightroom 64-bit has stoped working. A problem caused this program to stoped working correctely. Windows will close the program and notifiy
    you if a solution is available"
    I have a Windows 7 - 64bit
    Any help getting Lightroom started would be appreciated.

    Seems to be the following "classic" LR 3.x problem: http://feedback.photoshop.com/photoshop_family/topics/lightroom_3_4_1_64_bit_doesnt_work
    In short: You tried to create a new catalog with the name of an existing JPEG file ("DSC0024.JPG"). Perhaps you wantet to open/import that file and accidentally used the wrong command (create new catalog). Solution: 1) Rename the file. 2) Start LR, let it create the catalog in a folder named as the original file, 3) close LR, 4) delete the newly created folder containing the new catalog, 5) Start LR again - it will probably ask you for your catalog (select the catalog you are really working with). 6) Re-rename your JPEG file again.
    Edit: P.S: LR 3.2 is a rather old version. The latest update for 3.x is 3.6 (free of charge), download it here: http://www.adobe.com/support/downloads/product.jsp?product=113&platform=Windows (Note: This bug is not fixed in LR 3.6. It is fixed in LR 4).

  • Lightroom 4.2 64-bit does not start. How is 0xc000007b error resolved?

    System is Windows 7 Home Premium SP1 build 6701, Intel Core 5-750, 8GB RAM.
    Installed Adobe Photoshop Elements 11 then Premier Elements 11 64-bit then Lightroom 4.2 64-bit. Photoshop Elements, Organizer, Premier run just fine. Lightroom 4.2 refuses to start, stating The application was unable to start correctly (0xc000007b). Click OK to close the application. Ran Raxco Perfect Registry to eliminate registry errors. Performed full scans w/Notron Internet Security, Spybot Search & Destroy, and Malwarebytes Anti-Malware. Removed any/all threats. Lr continues to repeat 0xc000007b issue. I'm running out of options. I want to run Lr 64-bit, not 32-bit. Any ideas please?

    This has nothing to do with registry errors or any of that. It's simply a generic crash. As to what's the specific cause, noone can tell. Usually this is a missing system DLL or a flakey driver. Could of course also be a permissions issue where LR fails to load some components due to insufficient user privileges or your little tools blocking stuff. Norton is known to bury itself so deep in the system, it does more damge than good at times. Verify your device manager, turn off your security stuff, run as admin. And pick out the actual crash info from your system event viewer.
    Mylenium

  • Firefox won't start, there is no error message and it is not already running.

    Hi,
    When I try to click on firefox, the little wait icon appears and then disappears. Nothing opens, not even safe mode. I've looked at the "Firefox won't start and there is no error message" help section and looked at my task manager processes. It seems that when I click firefox, it briefly appears on my processes and then disappears. This happened yesterday while I was in the middle of using it. At the same time, my Skype also crashed, which makes me think the two are correlated. The two programs still don't work. The only way that I can open firefox is if I install it all over again with the "launch firefox now" option checked at the end. When I have a firefox window open, I can open other firefox windows just fine. When I close it, nothing opens. Thanks for your help.

    1) Start Task Manager
    2) Open Processes (make the description area large enough to see)
    3) look for a description that says ''firefox''
    4) Select it and press End Process
    '''Now Firefox should work properly.'''

  • Safari won't start after showing an error message: Safari can't use the extension "Omnibar" because the extension is no longer valid.

    Since yesterday evening (19-01-2015) safari won't start. After clicking the safari application it shows an error message: Safari can't use the extension "Omnibar" because the extension is no longer valid.
    This message almost directly disappears whereupon the Problem Report opens. I've tried to find a solution on the web but without succes.
    I'm running OS X Yosemite version 10.10.1 and Safari version 8.0.2 on a:
    MacBook Pro (Retina 13-inch, Mid 2014)
    Processor 3 GHz Intel Core i7
    Memory 16 GB 1600 MHz DDR3
    Graphics Intel Iris 1536 MB
    Since I updated to Yosemite I've been having multiple problems. I already read a clean install will solve most of them. But till then I would love safari to work again.
    Thanks!

    There is no need to download anything to solve this problem.
    If Safari crashes on launch and you don't have another web browser, you should be able to launch Safari by starting up in safe mode.
    You may have installed the "Genieo" or "InstallMac" ad-injection malware. Follow the instructions on this Apple Support page to remove it.
    Back up all data before making any changes.
    Besides the files listed in the linked support article, you may also need to remove this file in the same way:
    ~/Library/LaunchAgents/com.genieo.completer.ltvbit.plist
    If there are other items with a name that includes "Genieo" or "genieo" alongside any of those you find, remove them as well.
    One of the steps in the article is to remove malicious Safari extensions. Do the equivalent in the Chrome and Firefox browsers, if you use either of those.
    After removing the malware, remember to reset your home page in all the web browsers affected, if it was changed.
    If you don't find any of the files or extensions listed, or if removing them doesn't stop the ad injection, then you may have one of the other kinds of adware covered by the support article. Follow the rest of the instructions in the article.
    Make sure you don't repeat the mistake that led you to install the malware. Chances are you got it from an Internet cesspit such as "Softonic" or "CNET Download." Never visit either of those sites again. You might also have downloaded it from an ad in a page on some other site. The ad would probably have included a large green button labeled "Download" or "Download Now" in white letters. The button is designed to confuse people who intend to download something else on the same page. If you ever download a file that isn't obviously what you expected, delete it immediately.
    In the Security & Privacy pane of System Preferences, select the General tab. The radio button marked Anywhere  should not be selected. If it is, click the lock icon to unlock the settings, then select one of the other buttons. After that, don't ignore a warning that you are about to run or install an application from an unknown developer.
    Still in System Preferences, open the App Store or Software Update pane and check the box marked
              Install system data files and security updates (OS X 10.10 or later)
    or
              Download updates automatically (OS X 10.9 or earlier)
    if it's not already checked.

  • AE won't start and has this error

    My After Effects CS6 won't start on my iMac and shows this "alert" message:
    <140735302083328> <AppDirs> <5> Required Dir =
    /Applications/Adobe After Effects CS6/Adobe After Effects CS6.app/Contents/Required
    how do I fix this?s

    Hi C Thomas,
    See this post: Re: After Effects doesn't open on Mavericks
    Thanks,
    Kevin

  • Xorg won't start - gives Connection Refused error

    I'm trying to use Xorg, I have it configured with Xorg -configure and all that, but when dtlogin tries to start it reports these errors in it's logfile:
    XIO: fatal IO errors 146 (Connection Refused) on X server ":0.0"^M
    (the ^M is part of the message as well)
    Any ideas?

    Hi Reasons,
    Your problem seems to appear atfer loading the libglx module:
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    Maybe you're having this issue described in nouveau's wiki: http://nouveau.freedesktop.org/wiki/InstallNouveau
    9. Now start Xorg and run for cover. If you used the the nvidia blob before, the X server may possibly not start because NVIDIA overwrites the libglx.so which the X server provides with it's proprietary libglx.so. If that happens, install the X server package from your distribution again to resetore the original libglx.so and make a backup copy of it in case you install the blob again.

  • Lightroom preview cache error- can't start

    "Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches."
    Cn't fix it

    Moving to light room.
    You can refer to
    lightroom encountered an error when reading from its preview cache and needs to quit
    Error Reading Preview Cache - LR keeps crashing or quitting. - Lightroom Forums
    They can be useful.
    Regards
    Rajshree

  • Lightroom 5 preview cache error

    Hi,
    I have a new problem with an old issue. I have read as many threads as I could on it and cannot seem to fix these issue.
    I had been using LR4 and added new drives to my Mac Pro 2009 OS 10.6.8 w/48RAM
    I started getting the the "LR encountered an error when reading the preview cache and needs to quit" message.
    I have since installed OS Yosemite and installed LR5.2
    I followed the instructions to delete the Previews.Irdata and then get this message
    I have older catalogs from LR2,3 and 4 on another drive. Please don't laugh, I have no idea what to do.
    There are .Irdata files in most of those folders too.
    What do I do first?
    I appreciate any suggestion and support.
    Thanks RPT

    Looks like a general Mac problem rather than particular to Lightroom. A Google search for that exact error message shows a bunch of possible solutions.

  • Lightroom preview cache error messge

    hello, I keep on getting an error message "Lightroom has encountered an error while reading the preview cache and must quit". can anyone tell me what the problem is and help me solve it?
    thanks in advance
    abel

    As the message says.....the preview cache has a problem, probably there's a corruption in there somewhere, and this is preventing Lightroom from working. Easiest solution is to delete the existing preview cache, and on next start of Lightroom a new cache will be created. The downside is that initially there'll be no previews available although Lightroom will start to build new ones automatically, but only for images as they are brought on screen in the Grid or Filmstrip. Alternatively you can instruct Lightroom to build new previews (for ALL or just selected images) using the Library>Previews options, but if doing ALL you may want to set that going overnight as it can take a while depending on the number of images in the catalog.
    The previews cache is contained in the sub-folder ending in "Previews.lrdata" which is adjacent to the catalog......just make sure you delete this folder, and NOT the catalog file ending in ".lrcat".

  • Lightroom is crashing every time I open it with a "preview cache" error.

    Says "Lightroom encountered an error when reading from its preview cache and needs to quit." and then it forces it to close.  I've tried uninstalling/reinstalling, restarting my computer (which is only a few months old).  As a photographer in the middle of the busy season, this is EXTREMELY frustrating!!  Help please!

    john beardsworth wrote:
    In the same folder as your catalogue is a previews.lrdata folder. Delete this (in Finder or Explorer) and restart LR.
    Nice work, John. That seems totally random but I've not had this issue. How did you figure it out?

  • "lightroom encountered an erorr when reading from it's preview cache and needs to close"

    I can't get rid of this error message.  I have moved/deleted the preview cache..did not help.  I then deleted all the other files in the "Lightroom" folder...doesn't help.  Please help!!  thank you in advance

    Thanks everyone. Just for future people who may read this... Turns out..LR had created another catalog on my C:/ drive that I didn't know about.  (My main catalog is located on a separate drive.) So, when I was doing all of these steps to my main catalog, it didn't work.  Problem was on the C:/ drive.   I still wasted a ton of time talking to support and the person was not knowledgeable.  He/She kept telling me that my catlog was corrupted even though the error message clearly stated it was the preview cache.  All of these software companies need to a) bring their support desks back into this country, b) train the people to actually know the product inside and out.  I've had to contact 3 different companies for support over the past few weeks and all of them gave me useless generic answers that you can find on their websites.  Frustrating.  Sorry for the rant and thanks again everyone.

  • HELP PLEASE!!!!  Lightroom Preview Cache Error

    Hi There,
    Has anyone ever experienced the following error when trying to open Lightroom:
    " Lightroom encountered an error when reading from it's preview cache and needs to quit "
    It then says below that in smaller writing:
    " Lightroom will attempt to fix this problem the next time it launches "
    But unfortunately it hasn't :-(
    I have uninstalled, reinstalled, restored etc etc.......
    Does anyone know anything about this??
    Any help greatly appreciated
    Thanks in Advance :-)

    Oh My Goodness!!!!
    Thankyou so ver very much!!!! I have been trying to work this out thinking my computer was buggered an everthing.....
    It's just opened!!!!!
    Thankyou Thankyou Thankyou

  • Premiere Elements 10 64 bit won't start

    My issue:
    When I try to start Adobe Premiere Elements 10 64 bit the program will start to launch and then windows will announce "Adobe Premiere Elements 10 has stopped working"
    My System:
    HP Elitebook 8540w
    Intel i7 M640 CPU
    8GB Ram
    64bit operating system
    Nvidia Quadro FX 880M
    I have tried: (I'll try to remember everything)
    Uninstalling/Reinstalling
    Restarting after every uninstall mentioned in the I have tried section
    Uninstalling antivirus
    Stopping all programs and unneccessary services I could find
    Updating video and sound card drivers to the latest version
    Updated to latest version of Quicktime 7.71.80.42
    Clean up hard drive and temp files
    Uninstalled NVidea 3D Driver, PhysX System, nview and HD Audio Driver, leaving only the primary display driver
    Checked event viewer looking for any logged issues.  It always fails on display.dll.  Details below
      Faulting application name: Adobe Premiere Elements.exe, version: 10.0.0.0, time stamp: 0x4e791009
    Faulting module name: Display.dll, version: 6.0.0.0, time stamp: 0x4e78fee0
    Exception code: 0xc0000005
    Fault offset: 0x00000000000230bc
    Faulting process id: 0x874
    Faulting application start time: 0x01ccaba6fa61d433
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Elements 10\Adobe Premiere Elements.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Elements 10\Display.dll
    Report Id: 3c543fc1-179a-11e1-ad00-68b599f767d3
    Any ideas?

    The error message seems to be pointing the finger at your display drivers. You say:
    MMerck wrote:
    Updating video and sound card drivers to the latest version
    Uninstalled NVidea 3D Driver, PhysX System, nview and HD Audio Driver, leaving only the primary display driver 
    Are these the mobile drivers from the nvidia site or from HP? Whichever ones they were, try the other. It's also possible that your windows updates applied a graphics driver update - that's usually a bad thing. Always get the drivers from HP or nvidia.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

Maybe you are looking for

  • A problem using importFileInto

    Hi, I'm trying to import a flash file (swf extension) for a Director project (MX 2004) but when it is within the "cast" sometimes appears with the original extension ("width." 595, "height" 842) and others with 320x240 (in particular it always). I ha

  • Nokia Suite 3.8 does not recognize my 6233 with bl...

    Hello Last year I had made some pictures with my Nokia 6233 and I transferred those pictures via Nokia Suite to my PC. Since then I had a couple of updates installed for the Nokia Suite and now I have the latest version on my PC. But the newest versi

  • I am accessing iCloud from my Mac and want to know where I find my iMessages in my Mac.  Thank you!

    I am accessing iCloud from my Mac and want to know where to find my iMessages within iCloud.  Can anyone help me out with this?  Thank you so much!

  • Change material BOM / item / Class Recursion

    I'm looking for a way to change the "recursiveness allowed" flags in the "Class Recursion" tab of a BOM item in transaction CS02. The flag corresponds with the fiels REKRS in table CLRK. No BAPI or FM found after half a day of searching. The CSAP_* f

  • Strange Behaviour of Abap Report

    In my report , I am displaying the page number in the top of the report in the format page 1 of n . The code i am using is ... DATA l_page_count(5) TYPE c. FORM   page_display .   WRITE sy-pagno TO l_page_count LEFT-JUSTIFIED.   DO sy-pagno TIMES.