Images getting corrupted in Lightroom 4.2

I have experienced this aswell. As mentioned in:
http://forums.adobe.com/message/4138626
and http://forums.adobe.com/thread/948417?tstart=0
My lightroom has after two weeks of playing with a fully working raw file corrupted it.
This is what the photo looked like originally http://500px.com/photo/14737987
As of today, I tried to reexport it with a diffrent watermark, the raw file corrupted. It exports a corrupted jpg and when I delete the .xmp metadatafile and try to import it again (same happens with it now when trying to import it to photoshop) the raw file now renders as corrupted in all software.
I have tried every possible way to reimport it, its just plain broken. If this should happen to my whole portfolio I would cry.

Here's evidence that LR is rewriting an entire JPEG file when I add metadata and do Save Metadata To File, just as Rob has described.
First, I imported a JPEG in which all the metadata had been stripped using Exiftool. Exiftool's dump shows that the image data starts at around hex offset 10:
Immediately after importing, I did Save Metadata To File, and the image data now starts at around hex offset 0cf0:
Next I added a short caption and did Save Metadata To File, and the image data now starts at around hex offset 0dd0:
I used the Microsoft Sysinternals' Process Monitor to trace file reads and writes to the JPEG file while LR was doing Save Metadata To File, and that confirms it is writing the entire 1 MB file:
Obviously, if there's a hardware fault anywhere in the path from the disk to memory and back, the contents of the image data could get corrupted.
And just as Rob has patiently explained, the fact that the file could get rewritten doesn't constitute any criticism of LR.

Similar Messages

Images getting corrupted in Lightroom

When review a shoot in Lightroom, I've noticed a bunch of images are getting corrupted, maybe 1 in 500 and end up looking like the enclosed example.
What's even wierder is that if I delete the file and then import the same file from a back up drive, it is corrupted in the same way.
Weirder still is that I then take the raw file off another backup and place it on the desktop, bypass Lightroom and open the raw in Bridge, I end up with the same corruption.
It does not seem to be inherintly corrupted from the original capture because whe I originally imported the file into Lightroom, the preview looks fine. Then, I click on the file to enlarge it or something and it turns like this.
Anyone have any ideas what is going on here? I could almost buy the theory of a corrupted drive but, replacing the files frmo another drive still results in the corruption so, not sure what to think. Scary though becasue if this problem accelerates, I could lose my whole archive theoretically.

Keith,
Yeah. I've seen them, but I've yet to see compelling evidence that Lightroom is at fault. My mind isn't closed on the issue, but I'd put the probability heavily in favour of LR's innocence. I'd be glad to see proof that LR is destroying files, because then Adobe would be able to plug the leak, as it were, and we all could feel a little safer.
The thing is, a very few people are seeing a fraction of a percent of their images becoming corrupt, and the people who have the trouble don't just lose one, but at a steady (if very slow) pace. That kind of situation sounds like classic hardware problems. It seems to me that if there was some bug in Lightroom that was eating files, it would affect more people. Bugs become pretty obvious after a while.
To oneword: Those backups that are also corrupt. How did they get to their backup locations?
Hal

Images get corrupted

When I drag images from the clips pane to the timeline they look fine. After playing them with some audio they develop vertical bars over most of the time the image is displayed.
Is it because they're jpegs dragged into the clips area and not imported from iPhoto? I don't keep my images in iPhoto and would like to just drag them as needed from their folders. (You'd think iMovie would have a browse function)
I've got 42 gig of free disk space.
thanks

When is it safe to remove the placeholder?
When you are finished adding stills.
Can I export to QT safely without it being there?
Yes.
Will images get corrupted again once the placeholder is removed?
Only if you add new images.
Have subsequent versions of iMovie have solved this problem?
Yes, I think so.
Message was edited by: Lennart Thelander

Nikon D4s images get corrupted

When I work with my D4s raw images in Lightroom 5.4 (latest update), they seem to get corrupted.
Images are imported and while browsing them, I sometimes get a notification that there is an unexpexted end of file for certain images. Also some images look completely corrupted. They are very bright and have vertical color bands.
Once I have this message on my images, Photoshop CS6 can't open them anymore with the same kind of message.
If I take the CF card with the original raw files and I open them with another software such as Nikon NX or photomechanic, I can work with these images and nothing goes wrong. So the current work around is converting to TIFF in either of the previous mentioned softwares and then importing in LR.
But is there a permanent solution? I would love to have my raw files in LR!
And what about the files that have been corrupted? Is there a way to recover them? I don't have all the original raw files anymore
Thanks,
Jerome

JeromeG wrote:
Once in lightroom and working with the images, some of them suddenly showed as corrupt.
Theoretically, Lightroom is bullet-proof, and just like it says on the wrapper: won't write raw files and so can't corrupt them. The cause of such behavior is therefore hardware.
That said, and at the risk of suffering a spanking from Jeff Schewe, it sure does seem like there is an inordinate number of such reports - there's either a lot of bad hardware out there, or Lr has a nasty bug that's currently being denied (publicly anyway).
I hope Jeff Schewe is right: such bug is impossible (virtually, essentially, for all practical purposes anyway..), and if such bug were being investigated by Adobe, they would make sure it was well known by all users via the forums & journal etc. (uh-huh).
Anyway, even if there is a bug in Lightroom, many (probably all) of these problems are caused by failing hardware (or other system problem), so that's the first thing to assume/check.. - disk & ram are perhaps the most common source of such anomalousness.
Beware: initial image in Lightroom is from jpeg preview NOT raw rendering. So, it could be these images were corrupt before they reached Lightroom (even though they looked fine in Lightroom initially) - depends on what you were able to do with them in Lightroom before the corruption became apparent.
Cheers,
Rob

Images getting corrupted?

Many of my images appear to be getting corrupted - and I do not know what is happening!
When I look at a folder in the browser view all the images appear OK - but, when I try to open some of them into the viewer or split view then suddenly the image appears either half grey, all grey, distorted or with various colours streaked across.
This is alarming - especially as the same thing is happening with images on my back up copy on another drive!
There does not appear to be any logic to this - except that most are in the folders that I imported from iPhoto a long time ago. But, it is also happening with some Aperture folders also.
I have tried rebuilding the library (on both drives) but this did not resolve the problem.
I am afraid to open any more thumbnails - can anyone please help????

Hello Alan, sorry, I can't help - me too.
Does this look familiar to you?
I found several similarly corrupted versions in my library - all were images I cropped or straightened previously. The images looked o.k. when I imported them; I tagged them, used them in albums and web galleries, but when I cropped them recently, they started to disintegrate before my very eyes - really scary
Since only my images marked with 5 ***** were effected* and these pictures are very valuable to me, I tried to restore the versions from the master files and found the masters corrupted too. It seems, I have always been viewing the previews generated by the camera, but the master files were corrupted from the beginning. And when I edit the images new previews are computed from the defective masters, and now the previews are also damaged.
I tracked down the original masters from backup and found the backed up master files also cannot be displayed correctly on any of my macs. For good measure I tried to display them on a Linux system and a Windows system, hoping for some weird bug in the Mac libraries, but no luck.
What I did to save some of my images was to rescue the previews before any further editing was done. Then replace the damaged masters by the previews.
And I bought new cards for my camera. Since the problem occured with three different cameras and the only common factor were the cards, I found it safer to use new cards. No more problems since then.
Regards
Léonie
* I did not believe in a five-star-virus

Uploaded Image gets corrupted after upgrading jre from 1.3.0_02 to 1.3.1_15

We were running jre 1.3.0_02. The image upload functionality was working fine with this version. But after upgrading to jre1.3.1_15, the uploaded image shows correct file size but it gets corrupted.
Please help.

I found that the problem with encoding. If wrote a sample application which read gif file and print the value.
Here is sample application:
import java.io.FileInputStream;
public class TestCopy {
public static void main(String[] args) {
String filename = "/home/appliance/data/frontpanel/logo.gif";
StringBuffer sb = new StringBuffer();
try{
// System.setProperty("file.encoding", "ISO-8859-1");
FileInputStream f = new FileInputStream(filename);
System.out.println("<SaveOnAllServlet> autoSaveArgs :"+filename);
int c;
while((c = f.read()) != -1){
System.out.println(c+"->"+(char)c); // This is problematic for me
sb.append((char)c);
System.out.println("Copy complete...");
System.out.println(System.getProperty("file.encoding"));
f.close();
// System.out.println(sb);
catch (Exception e) {
e.printStackTrace();
when I run this program on jre1.3.0_02 get value of file.encoding as 8859_1 and on running same application on jre1.3.1_15 I get encoding value ANSI_X3.4-196
Please let me know how can I set desired encoding... I wants to set default encoding of jre1.3.0_02 to default encoding of jre1.3.1_15
thanks in anticipation.

Photos keep getting corrupted in Lightroom Catalog - Help!

Photos in my LR Catalog (usually over a year old) keep getting corrupted. When I go to a dated folder, a strip comes up with the photos. Some of them are fine, some of them have an "!" on the photo saying "An error occured when working with this file." So I try to "EDIT IN PS." It will allow me to choose "Edit a Copy" and so when PS tries to open it, the error message says "The document may be damaged. File may be truncated or incomplete." I open anyway, and it shows fine 2/3 or 3/4 of the way down, then it gets chunky....like someone cut off the bottom of the photo and bumped it up a bit. I will attach a photo. HOW can I keep this from happening??? I have my catalog on a Seagate external drive because my laptop can't handle all the space it would take up. I always wait until it says I can eject, although it almost NEVER says that, even after being left for HOURS, so I shut down the computer, then unplug the hard drive. I would love some help, because this keeps happening!!!

I tried opening one of the affected photos directly into Photoshop without using LR first. It looks like this.

Files get corrupted in Lightroom 4, through 4.4

So I was going to comment on one of the other posts about the corrupted files but it was soooo long I decided to start a new one.
This should give me a hint that it is not HARDWARE....
To start with I am shooting a Canon 5d mkIII and RAW(.CR2) files
A slight kink in everyones generic answer that it is a hardware issue; I reproduced this on two computers using the same .cr2 files copied from the same original downloaded files. Lightroom corrupted files on import on both computers.
Also to test the answer it was corrupt before it went into Lightroom. I always copy the raw .cr2 file to my laptop and then to a external drive from the laptop directory, not from the compact flash. I looked at a .cr2 file with Photoshop and it was fine. Then I imported that same file with all of the other .cr2 files in the directory into Lightroom 4 and it was corrupt along with many others.
My disappointment is that when I tried to open the same .CR2 file, that was fine a moment earlier with Photoshop, it too was corrupted. I thought Lightroom was non-destructive to the original file.
I deleted that .cr2 file and restored the backed up file that was a copy of the original and imported that single file into Lightroom and it was now fine.
Sorry but not acceptable.

Replying to myself:
I digged into some reverse-engineered CR2 specifications on the net and found 5 things:
Canon uses a lossless compression in their CR2 files. So that suspicion was confirmed.
The algorithm does not seem to have changed substantially in later models. So that suspicion was not confirmed.
Before doing the compression, the raw photo is divided into vertical slices. Usually 2 or 3 slices, it seems, though I am not sure). This seems to explain why we sometimes see a corrupt lower quadrant of a Canon photo.
According to one source, the image is "interlaced" before compression, so all lines with RG information are kept together, as are all lines with GB information. Based on that, I would expect to see photos with every second line corrupted, if we could see the photo prior to demosaicing. But since we only see the photos after demosaicing (which involves combining information from several lines), that is not really relevant.
The compression algorithm used is Lossless JPG which uses Huffmann encoding for compression. This seems to me like a method which has good corruption potential.
The long version of my reasoning for the corruption potential of Lossless JPEG + Huffman encoding (just skip it if it is too boring):
I have heard about Huffman encoding many times before, but I have never bothered to find out how it works. This thread was a good reason to bother, so I finally did it.
Lossless JPEG works by predicting the value of each pixel based on the pixels above it and to the left of it. The difference between the actual pixel value and the prediction is then stored as a prediction error. The original pixel values can then be thrown away because the raw decoder can precisely reconstruct them from the prediction errors and knowledge of the prediction method used.
This means that it is only necessary to store the prediction errors in the file. Even though the original pixel values will be very different, a lot of pixels will have the same prediction error (close to zero). This makes it easier to compress the prediction errors than the original pixel values.
The prediction errors are compressed using Huffman encoding which works sort of the same way as international dialing prefixes (this is a comparison I have come up with myself):
There are more than 100 countries in the world, so we sometimes have to use a 3 digit prefix. But we don't use 3 digit prefixes all the time. For example, USA is +1 and Denmark is +45. So when you punch for example '+4512345678', how does the phone system know that the international prefix part of the number is exactly +45 and not +4 or +451?
The answer is that one international prefix is never used as the first digits in another international prefix. So +10, +11 ... +19 and +100, +101 ... +199 are never used as international prefixes because USA already have used +1, and +451, +452 ... +459 are never used because Denmark have already used +45.
Huffman encoding works in the same way. Instead of having a lookup table with dialing prefixes of different length and their corresponding countries, it has a lookup table of bit codes of different length and their corresponding prediction error. Each bit code can never be used again as the beginning of a longer bit code so the encoder will always know where one bit code ends and the next begins, even though they are of different length.
This means that the well predicted pixels can be stored with just a few bits instead of storing them as a full 14 bit value. Just like USA can be dialed with +1 instead of using full 3 digit code of +001.
But it also means that decoding will fail miserably if just one bit is switched. Switching one bit in a bit code will usually mean that the length of that bit code will be misinterpreted, and that means that the decoder will look for the start of the next bit code in the wrong place. So from that point in the bit sequence, we can expect everything to go wrong.
(Sorry to be so long winded. But reading about Huffmann is like getting a new tool - I just have to use this knowledge for something.)

My RAW images get corrupted after downloaded HELP

Hey anyone, and if you do not know why this is happening, please pass it on.
attached in an image I was looking at in LR, this same problem has occurred in Bridge. while looking at images all of a sudden part or all of the image goes into psychedelic colors as seem in the lower rt side. anything from a line thru the middle of the picture to the total image with all sorts of mosaics of color this has been happening for may years. a forum told me I had a corrupt card reader, another said something to do with the computer. so to put this in perspective. i have used many different card readers, two different computers. two different operating windows systems. original was XP and new one is windows 7. this image was not copied from one computer to another so it is a new image downloaded into the newer computer. Once in a while when I open the image it reverts back to the image without the wiierd colors in it. If I bring it into bridge the same things happen in corruptions . I have lost images from many years ago in bryce canyon to this issue .
Once the image is saved in a different formate , JPG< PSD, Tiff. etc it never corupts. ONLY the RAW files corrupt and DNG. for a while I started shooting in both JPG and RAW just to have a back up. two different cameras, many different card readers. many cards. still happening. any help would be appreciated , have not found anything on the adobe forums. if you have no idea could you pass this one to friends , need a solution, for a while I backed up all the images when downloading directly to a hard drive without going thru LR or photoshop just to have a replacement. that just gets crazy to do after time.
As you can see on the lower left there is crazy stuff going on. sometimes it is the total image corrupted.
PS , if the two forums , fred miranda, and lumosity landscapes , do not have an answer, please help me find one. it is horrible to loose images from years ago much less last wk to this issue.
BTW this does not happen on my old Vista laptop, thanks for helping in advance. steve

thanks,
last option not viable, LR or PS really can not be replaced, I could live
without LR , have had it since version 1 release think 2007ish. It was
mainly a way to keep track of ones images via search words . good idea,
since this was difficult pre-digital with tons of negative.
I use it for down and dirty qucik editing to post something on G+ or FB
but not for final editing. RAW thru PS is where I do that and then into
PS .
If my wife would not leave me I would switch to Mac. not happening as a
hobby at this time. my guess is a freaking RAM issue or operatting system
that maybe when I transfered my images from the old computer to the new I
carried some type of bug with the transfer to the new computer. but that
is reallllly reaching.
Adobe has not been helpful in the least, but that is not new.
you are only one of two people to give some advice, very appreciated and I
am about 98% that your suggestions are correct.
steve

JPG images get corrupted during import to Premiere CS5.5

I'm doing time lapse movies, and import a series of images by choosing the first file, and checking "Numbered stills". After the import (of about 420 JPG files), one of them was being corrupted. It now has a discolored break in it:
The corruption was not present before the import, so it was definitely caused by Premiere CS5.5. Unfortunately, I no longer have the original file (from my memory card). So I essentially lost this image (although the embedded thumbnail is still intact).
Is this a known issue? Will there be a fix?

Thanks for your comments and links, everyone. I've read them, and want to clarify a few things:
John T Smith wrote:
>about 420 JPG files
Have you already read this?
Photo Scaling for Video http://forums.adobe.com/thread/450798
-Too Large May = Crash http://forums.adobe.com/thread/879967
Too many of too large pictures can cause problems
Thanks for posting these. I find it disappointing, that large pictures are not being handled well by Premiere. I mean, the images that I'm using are 3648x2736. If that is considered too large, then I would need to batch resize them, e.g., to 1920x1440. But then I would not be able to get high-quality panning and zooming...
Jim Simon wrote:
I no longer have the original file
You must have it. PP doesn't do anything to imported assets other than show them to you. If the image wasn't exactly where it was when you imported it, Premiere Pro would simply see it as offline.
That's not correct, I'm afraid. Each time I import one or more images, Premiere edits the file(s). I believe it is related to the XMP ID. You can even "watch" it do the edits because every JPG file briefly gets rewritten with ._00_ in front of its original file name, e.g., IMG_1234.JPG briefly becomes ._00_IMG_1234.JPG. Afterwards, the original file is being replaced with the new one (which apparently contains the XMP ID tag now).
On a sidenote: I've had several files stay with the ._00_ file name but the original was removed. Meaning that Premiere somehow "forgot" to rename them back. This happened on 8-12 images (out of 600). Very weird.
Powered by Design wrote:
I dont know if this is your problem but do you have "Write MXP ID to files on Import" on ?
Maybe something went wrong.
http://forums.adobe.com/message/3009053
GLenn
I'm assuming that's what's causing it. And yes, that option is enabled on my computer. So while the XMP ID tagging went fine for the other 419 images (and frankly for thousands of others before that), it somehow went wrong on one of them. (I should say two because it did happen twice to me so far.)
I will disable the option "Write XMP ID to files on import" from now on, and hope that I can avoid image corruption by that. But from what I understood, this will have other consequences (performance degradation).
The only alternative would be to keep a backup copy of all images before importing them to Premiere...
In any case, I believe this is a bug that should be fixed - together with the above mentioned bug on large images.

Firefox images sometimes get corrupt

hello im having a issue with firefox
sometimes when i switch tabs or just view images the images get corrupt
some of them are getting black things covering most of the images and rarely some crap (like a upside down blue triangle)
and when i was seeing many pages on file extensions and saw wikipedia the image got somehow corrupt, again, the black thing but in the bottom some white with some random blue
im using windows 10 build 9926
here is troubleshooting info
"application": {
"name": "Firefox",
"version": "36.0",
"buildID": "20150222232811",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0",
"updateChannel": "release",
"supportURL": "https://support.mozilla.org/1/firefox/36.0/WINNT/en-US/",
"numTotalWindows": 1,
"numRemoteWindows": 0
"lockedPreferences": {},
"graphics": {
"numTotalWindows": 1,
"numAcceleratedWindows": 1,
"windowLayerManagerType": "Direct3D 11",
"windowLayerManagerRemote": true,
"adapterDescription": "NVIDIA GeForce G100",
"adapterVendorID": "0x10de",
"adapterDeviceID": "0x06e6",
"adapterSubsysID": "00000000",
"adapterRAM": "512",
"adapterDrivers": "nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um",
"driverVersion": "9.18.13.4144",
"driverDate": "2-3-2015",
"adapterDescription2": "",
"adapterVendorID2": "",
"adapterDeviceID2": "",
"adapterSubsysID2": "",
"adapterRAM2": "",
"adapterDrivers2": "",
"driverVersion2": "",
"driverDate2": "",
"isGPU2Active": false,
"direct2DEnabled": true,
"directWriteEnabled": true,
"directWriteVersion": "10.0.9926.6",
"webglRenderer": "Google Inc. -- ANGLE (NVIDIA GeForce G100 Direct3D9Ex vs_3_0 ps_3_0)",
"info": {
"AzureCanvasBackend": "direct2d",
"AzureSkiaAccelerated": 0,
"AzureFallbackCanvasBackend": "cairo",
"AzureContentBackend": "direct2d"
"javaScript": {
"incrementalGCEnabled": true
"accessibility": {
"isActive": false,
"forceDisabled": 0
"libraryVersions": {
"NSPR": {
"minVersion": "4.10.7",
"version": "4.10.7"
"NSS": {
"minVersion": "3.17.4 Basic ECC",
"version": "3.17.4 Basic ECC"
"NSSUTIL": {
"minVersion": "3.17.4",
"version": "3.17.4"
"NSSSSL": {
"minVersion": "3.17.4 Basic ECC",
"version": "3.17.4 Basic ECC"
"NSSSMIME": {
"minVersion": "3.17.4 Basic ECC",
"version": "3.17.4 Basic ECC"
"userJS": {
"exists": false
"extensions": [
"name": "Adblock Plus",
"version": "2.6.7",
"isActive": true,
"id": "{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}"
"name": "Flash and Video Download",
"version": "1.68",
"isActive": true,
"id": "{bee6eb20-01e0-ebd1-da83-080329fb9a3a}"
"experiments": [],
"modifiedPreferences": {}
}

You can try to disable OMTC and leave hardware acceleration in Firefox enabled.
*about:config page: layers.offmainthreadcomposition.enabled = false
You can open the about:config page via the location/address bar.
You can accept the warning and click "I'll be careful" to continue.
*http://kb.mozillazine.org/about:config
You can try to disable hardware acceleration in Firefox.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
You need to close and restart Firefox after toggling this setting.
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
*https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

When editing an image in Photoshop from Lightroom then saving it back to Lightroom, how do i get the image to go back and sit next to the original? Mine is going to the end of the folder. Thanks Karen

When editing an image in Photoshop from Lightroom then saving it back to Lightroom, how do i get the image to go back and sit next to the original image? Mine is going back to the end of the folder. Thanks Karen

Hi Karen
You may the sort set to Custom. Click the dropdown menu on the toolbar (to the right of the word sort) and change to capture time.
If you can’t see the toolbar above the filmstrip press the T key. Press T again to hide.

Why do I get corrupted JPEGs when saving images in Camera Raw, CS6, Mac 0S Mavericks

I occasionally get corrupted JPEG files when processing RAW files in Camera Raw. The images will have lines of pixels that ar out of line, and or whole sections will be truncated and show white or black. I'm using PS CS6, Camera Raw 8.6 on a Mac with OSx Mavericks. Not sure, but it might have something to do with the Bridge Cache, which also acts up when it's getting full. Anyone else have this problem, or any advice.
Thanks!

right click on the jpeg (the other mouse button then you use to click with) or on trackpad, hold down control and click, in the menu that pops up, click on "get info" next, if the box labeled "locked" is checked, uncheck it. Down at the bottom, there should be a box with your user name, "staff" and "everyone". to the right of this are options to change these you may need to click the small padlock icon and enter in your password. then change all of the permissions to read and write.

On receiving jpegs via email, sometimes they get corrupted, and there are horizontal blocks appearing on the image

On receiving jpegs via email, sometimes they get corrupted, and there are horizontal blocks appearing on the image that distort the image. Help???

Hi Bruce523,
Let's get to the bottom of this, your efforts are greatly appreciated! What is the software version on your device:http://vz.to/ZVhZsh ? I look forward to hearing from you soon.
Thanks for your contribution to our community forums,
AyaniB_VZW
Follow us on Twitter @VZWSupport

Dock gets corrupted on Iintel machines/10.4 after restoring from disk image

Hi all,
I run a script at home that creates an image of my boot disk every night (it reboots into another volume, runs SuperDuper! and boots back into boot volume. I also use master disk images to deploy Macs at work. Every time an image is restored the dock becomes a mess, it looks something like this:
http://a-world.net/files/dockmess1.jpg
...random icons pointing to random files, example, this is what used to be a Firefox icon, not:
http://a-world.net/files/dockmess2.jpg
This only happens on Intel Macs and started to happen recently after one the system updates. It wasn't happening under 10.4.6 I think but it started some time after.
What's even weirder is that restoring com.apple.dock.plist from backup (Retrospect) doesn't seem to help, the prefs get corrupted anyway. Is there any other prefs file responsible for maintaining links betwen items in the Dock and originals? By the way desktop shortcuts do not get messed up, only the dock.
Any ideas? This is very annoying. Thanks.

This behavior is happening to quite a few of our computers. What they all have in common is that they are Intel Macs that have been upgraded to 10.4.10. I have verified on our test boxes that the problem does not occur with 10.4.9, then appears in 10.4.10. Don't know why.

Images getting corrupted in Lightroom 4.2

Similar Messages

Maybe you are looking for