Windows 10. How do you mean I should back up my presets? I have presets from Photoshop, Lightroom, Luminar and Topaz...    ... View more

Akash, its not resolved. Well, this issue just keeps spiraling down a vast tunnel. Somehow with the update- all my files 20k in images got renamed to untitled 001,002,003.Nef, and some got renamed to.dng-why? Why would an update revert everything to a completely different file name? ...  so now there's no way to re-link without opening each and every raw file- and visually relinking to each individual image impossible-because I also can not see NEF thumbnail. My original files were named _DSC6791, _DSC6792 etc. All the metadata of edits - is gone. And that supervisor is now on leave. Adobe really needs to rethink their technology-because having everything linked to a source doc- if something happens to the drive where the source doc is located you are screwed.- then what? I am a photographer not a tech geek-this stuff is killing me.  Its too friggen complicated. And to boot, can't find my back up file-I'm up shoot's creek without a paddle.I spoke with my photo club last night and found out that at least 5 other people have had this happen to them- mixed Mac & PC so its not PC related issue-its definitely an Adobe Lightroom glitch- - totally detrimental. I've used these programs since inception, I've never experienced anything like this- it is enough for me to leave Adobe. For being down for 3 weeks talking with different support people-most of whom do not know enough to even be on the phone-placing you on hold for an hour then coming back to say their shift is over is madness and very unprofessional.  I might as well call A T & T for an answer. .. trying to get to the root of the issue- Adobe owes me software for life. Each call it takes 2 hours before you get moved up to a supervisor-then another 2 hours to try and explain it- and the part that pisses me off the most is that Adobe knew something or they wouldn't have " built in a fix" (which is still messed up) in 8.3.1. --Note to ADOBE: Adobe really needs to rethink their technology-because having everything linked to a source doc- if something happens to the drive where the source doc is located you are screwed.- then what? I have back ups of the files but not of the edits!  You should be able to do your edits.The edits xmp should remain with the raw file where ever you need to move it.  You should be able to change the name of the file in Lightroom or outside of lightroom. It shouldn't be a one way path. You should be able to move the edited raw file to a new drive without consequence of breaking a link -you should merely have to point to the folder and be done---(not have to go to the source folder-move it to the new location and then relink file by file) and you should be able to update without having the system default to "Rename" being checked and untitled..."   that is blatantly wrong.  I am a photographer not a tech geek-this stuff is killing me! Not happy. Not happy at all. Too stressed out from all this. this is totally horrible. I am now trying to clone the original drive that got corrupted because it also had my Lightroom Catalog on it- and I am going to try to restore from that- but I have been cloning now for 3 days and still have another 8 hours to go before I will even be able to see if this idea works. BTW Western Digital has a fail safe in it that if any file gets corrupted it changes to a read only drive to protect the data. Problem was that "Lightroom" Permissions changed to read only- and that is what corrupted my Drive-not the other way round. Adobe owes me a phone call from their best technician. ... View more

Just to let everyone know, after 4 hours on phone with Adobe support- the problem resides within the Permissions of Adobe, not within your computer. And it is very easy to do it incorrectly- The supervisor told me if you do things wrong could damage everything severely. Highly recommend contacting Adobe Support and asking for the Supervisor Dhanush to assist with the fix. He is knowledgable ... View more

also the previous drive that was totally writable up until yesterday- something happened. making it unwritable. Interestingly enough I can open the images in Camera Raw in Photoshop- but NOT in Lightroom. That drive was exFat not NTFS. But, now the drive itself is now not even possible to change a file name. And so the problem is happening again- because it started with that issue in Lightroom and it is doing it again- today! with an entirely new clean slate- new SD card, new Hard drive, new updated Lightroom and updated Camera Raw as well. So that is why I say its a Lightroom glitch. My system shows that the older drive is "healthy" free from viruses, and no errors...  read my response to dj_paige ... View more

external drive, I don't have room on my OS drive for all my images-spent an hour on phone with Western digital also-their stock answer is to wipe the drive (4tbs of images) and reformat it. Dumb. ... View more

I am using Lightroom Classic 8.3.1- and camera Raw 11.3.   just updated the other day- as it says that fixes this issue that so many people are having. My OS is Windows 7 Home Premium, Service Pack 1. I also got a new drive, and uploaded images from my shoot this past week to it- the new drive is read /writable and NTFS. Uploaded images, imported into new lightroom, worked them yesterday and everything was fine. HOWEVER, today, I went back to pick up where I left off, and I am getting the same error messages that I had started getting last week when all this crazyness started. It won't let me change the file name, it says there's an error with Metadata and I just got another error message saying that Lightroom had an unexpected error and needs to quit.  This is exactly the same scenario that was happening the other day before all hell broke loose. I am concerned there is a major issue here. Plus it goes without saying that I need to spend time editing and selecting images for my deadline this wednesday and not playing teck cuz I am not a tech. PS I spent 2 hours on phone with Adobe support, and 4 hours with Windows support, ruling out everything else -no virus, etc. Came to conclusion the 4 tb drive has an issue- even though my system shows it as "healthy".   I really would like someone to look into this. ... View more

Hi, see above 5-29-19 from Akash... (copied in below this new information) Lightroom Destination Folder not writable issue. He says that Lightroom Classic 8.3.1 contains a fix for this very issue. This indicates that Adobe is aware of "an issue"  and some incompatibility was being caused-causing several folks to incur this problem suddenly. The fact that they wrote in a fix- means its not necessarily my drive but a bug of some sort. Regardless, something happened where my drive was working fine one minute and suddenly LR couldn't import from it.  Nevertheless,  I updated to 8.3.1 Lightroom Classic- that version- with help of Adobe support online to make sure it was done correctly. Yesterday I uploaded new images to a Brand New Drive that is read/writable. Double checked the files and they uploaded properly. worked on several images- everything is fine. Now ...Today, went back to the same folder to pick up where I left off on edits and now I am getting an error message "The file named "untitled-1334.NEF" could not be renamed. This was same issue that started a few days ago with the previous drive of images. + Also there is a problem with the metadata status... "There was an unknown error while writing metadata to this photo. Retry?"  Options are Import settings from Disk or Retry Metadata Export. .  hence the reason I don't think they fixed this bug.With all due respect,  I think something still not quite right. 19. Re: Lightroom Destination Folder not Writable Akash Sharma May 29, 2019 3:58 AM (in response to shannonm86447340) Hi All, We are happy to announce that Lightroom Classic 8.3.1 was released today and contains a fix for this issue. Please update to 8.3.1 and verify that you are no longer seeing the issue. See Keep your Lightroom version up to date Thanks, Akash ... View more

Guys this problem is still an issue. And I think when you updated Lightroom, it turned on a switch making an entire drive Unreadable-where, this morning they were reading just fine.. And now it is not letting me change the Drive to Readable-so I've spent 4 hours online support trying to fix, and I have work to get out and I can't import the darn images into lightroom ... View more