It would seem that your Windows version of LR is seeing the upper and lower case K as two different letters like a Mac would do.
Not sure how to fix this...
Thanks for replying. I also suspect that there are two Karen/karen folders in LR. I think this is a LR path problem and have no idea how to fix this. When I look at my paths in my computer C drive, all is well. There is no karen with a small k, only one Karen (capital K) folder under users. But, in LR, all my library photos show up in their folders only in karen (small k). Do you know anyone who might be able to assist?
Your old computer was probably under karen and the new one is Karen. Right click the Pictures folder under karen and do"hide parent folder". Then right click it again and do "show parent folder" and Lr should resolve the problem. I am not sure if this will work but past threads have offered this as a solution.
Bob, I tried it, but didn't have success--or at least did not know what to do next. But I think you are on the right track for fixing this problem. I just stumbled across this LR Forum Thread which "appears" to contain the solution to my problem. It has to do with the capitalization issue. The resolution, I think, is contained in a "Discussion in 'Managing your Photos & Video' started by Amos Thunder, Sep 28, 2015."
On page 2 of the discussion, Jim Wilde, Lightroom Guru, sums up the problem and resolution in a message to Johan Elezaga:
Johan (Elenzga), I keep thinking that we ought to do a write-up on this problem in our Tips & Tricks section. As you've seen, the fix is relatively simple but the trick is in identifying the problem. The root cause is that the OS is (usually) case-insensitive, whereas Lightroom unfortunately isn't. So when something such as changing the case of just a single letter on an existing file-path happens, e.g. correcting the case of the first letter of the username during an OS upgrade/change, Lightroom will continue to process the existing folders/files...because when talking to the OS about an existing file/folder with a file-path including, for example "tore", the OS quite happily processes that file-path even though in reality the current correct spelling is "Tore". The problem arises when doing an import after the case change....the import dialog shows the destination with the current case (Tore), so the case-sensitive Lightroom sees the file-path as a totally different path to the existing one, and so shows the folder outside the existing one....but the OS doesn't see anything different, so the files are physically stored in the existing folder hierarchy.
I am such a beginner with respect to "paths," that I can't really follow the directions--and am not even sure that I have the same problem--but I think I do. Bob, are you able to walk me through it? Or, is there a way to contact Jim Wilde?
Thank you for your help
Hi again...Just realized the thread I sent was from Lightroom Forums.
Is this the solution from Jim Wilde you are referring to. He is a member of the Forum and recently logged on so you could send him a Personal Message from this link. https://forums.adobe.com/people/Jim%20Wilde
I have seen this problem discussed on several occasions but don't remember in detail the solutions.
1 person found this helpful
BTW, here is a link to the entire thread that I got the Jim Wilde screen clip from which may help explain his solution to this problem. LR imports into a "shadow" copy of the folder | Photoshop Family Customer Community
Yes, you have the right thread in your earlier comment. I just sent (I think) a message to Jim Wilde, explaining my problem. I also found an updated (and more complex, to me) solution in Tips and Tricks: Volume / Folder appearing several Times in Folder Panel | Lightroom Forums This whole thing is causing me (and my husband) great anxiety.
Thank you for the link to Jim
1 person found this helpful
Just to update any watchers, I've provided Karen with the steps to take to correct the problem in the Lightroom Forums thread that she started: Problem with Duplicate Folders | Lightroom Forums
Hopefully that will close the issue.