Lightroom Classic 8.3: Issues exporting photos to a Network Drive

  • 24
  • Problem
  • Updated 15 hours ago
  • In Progress
  • (Edited)
Since I upgraded to V8.3 of Lightroom Classic I can no longer export my files to our Synology Network System, I get the following error message "The specified folder in not writable"

After contacting support they were not able to resolve my issue, they maintained that it is a network issue on my side. I could not find any answers here or anywhere on the internet and decided to report this issue.

Because I share my processed photos with the rest of the office, my only solution was to un-install V8.3 and go back to V8.2.1, by doing that it resolved my problem.

So yes Adobe you have network issues in V8.3 as version 8.2.1 works perfectly when saving files to a network drive.
Photo of Chris

Chris

  • 6 Posts
  • 1 Reply Like

Posted 4 days ago

  • 24
Photo of Roelof Moorlag

Roelof Moorlag

  • 158 Posts
  • 49 Reply Likes
Do you work on Apple or Windows?
Photo of Chris

Chris

  • 6 Posts
  • 1 Reply Like
I work on Windows 10 and all my files for all my applications are saved and stored on our Synology NAS System. The only files stored on my local drives are the Lightroom Catalogue files.
Photo of Nikolaj Christensen

Nikolaj Christensen

  • 1 Post
  • 6 Reply Likes
This seems not to only affect exporting to network drive. I have the same problem after updating to 8.3 and I can't export to local folders.
This is not a windows issue, since I do only have this problem with Lightroom.

 I found a work around, in the export box you can select in the top "select folder later". I you use this, you are allowed to export.
Photo of Daniel Zuppinger

Daniel Zuppinger

  • 1 Post
  • 0 Reply Likes
same issue here! I can no longer export to my folder on the C drive and I have DEFINETLY not changed anything in the Windows system! It renders Lightroom USELESS!
Photo of Laura Shoe

Laura Shoe, Champion

  • 76 Posts
  • 49 Reply Likes
I'm sorry to hear that you have the same issue, Daniel. While Adobe is working on this there is an easy workaround: Instead of choosing  "Export to: Specific folder", choose "Export to: Choose folder later (useful for presets)" - regardless of whether you are creating a preset - and Lightroom will prompt you to choose a location after you click on Export. 
Photo of Poyen Huang

Poyen Huang

  • 1 Post
  • 0 Reply Likes
Just for the record. While this workaround works for Export, it doesn't for existing Publish Service.  And that impacts the workflow a lot. 
Photo of Yvon Daigle

Yvon Daigle

  • 4 Posts
  • 2 Reply Likes
Same issue with my NAS, I can only save my files to the original location. I try on the the C drive it is not working also.

Photo of Smit Keniya

Smit Keniya, Employee

  • 219 Posts
  • 99 Reply Likes
Hi,

We have not been able to reproduce this issue with a local folder, network location or an NAS.

Could you share the screenshot of the securities tab from the folder properties for the folder where you are facing this issue?

Thanks,
Smit
Photo of Chris

Chris

  • 6 Posts
  • 1 Reply Like
Hi Smit Keniya I have attached a screen capture of the folder properties as requested. I'm user "ChrisFourie". As a matter of fact I cannot write/export files to any of the shared folders on our NAS when using Lightroom Classic v8.3

I can assure you that its not a write issue on our NAS. We do not experience any issues writing to any of the shared folders on our NAS using any application including all the other Adobe Creative Cloud Applications we use.

I have removed ver 8.3 and re-installed ver 8.2.1. This older version works perfectly.

Hope this helps, if you need me to perform any other tests, please feel free to ask, I'm a qualified Network Administrator
(Edited)
Photo of Thomas Hendel

Thomas Hendel

  • 5 Posts
  • 2 Reply Likes
I've got the same problem after the latest update yesterday. The export fails with a "Folder is read-only" error message. It used to work pretty fine in for all LR versions that I ever had (from 5 up to the version before the last update).
My system: Windows 10, target export folder a mounted folder from a NAS. It is *NOT* an issue with the network folder itself. While LR complained about the "read-only" folder, I could create sub folders and files there as usual.
The export into a local folder worked fine.
(Edited)
Photo of Jason Huang

Jason Huang

  • 1 Post
  • 0 Reply Likes
same issues, this is really bad, my network export folder is mapped for auto cloud backups, I can't just CHANGE drives.  I'm rolling back to 8.2.1 as well
(Edited)
Photo of avpman

avpman

  • 115 Posts
  • 82 Reply Likes
I think this was a bug in an earlier version and was subsequently fixed. Looks like the bug is back again.
Photo of KP Yletyinen

KP Yletyinen

  • 1 Post
  • 0 Reply Likes
I had the same problem. I could export to a memory stick, though. "Select folder later" workaround worked.
Photo of Thomas Hendel

Thomas Hendel

  • 5 Posts
  • 2 Reply Likes
One addition: I have several export presets. And one of them has a fixed target folder (located on a NAS), that is used to feed my tumblr account.
After the first error message, I opened the common export dialog and did a "select folder" operation (just to be sure, that the preset has correct settings).
After selecting that folder on my NAS - the export dialog was still open and no export was started yet - I got the "read only" message again.

Photo of Andrew David Cox

Andrew David Cox

  • 1 Post
  • 0 Reply Likes
I'm having the same issue. Can export to desktop just fine. Can't export to the network drive. Am on Windows. 
Photo of Yvon Daigle

Yvon Daigle

  • 3 Posts
  • 1 Reply Like
I can't export on my PC drive. The only place I can export files is on the NAS drive where where the original is.
Photo of Francois Hendrickx

Francois Hendrickx

  • 10 Posts
  • 1 Reply Like
I'm having the same issue after yesterday's update. I can only export to the root directory of any of my drives. It is a Lightroom problem as any othe aplication can save to any folder on any drive just fine.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5353 Posts
  • 1113 Reply Likes
Is everyone experiencing this issue on Windows? I don't see a single Mac User here yet.

Photo of Francois Hendrickx

Francois Hendrickx

  • 10 Posts
  • 1 Reply Like
Windows 10.
Photo of Thomas Hendel

Thomas Hendel

  • 5 Posts
  • 2 Reply Likes
Windows 10
Photo of Linda Alschuler

Linda Alschuler

  • 9 Posts
  • 0 Reply Likes
I've seen two Mac users report it in the Facebook groups.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5353 Posts
  • 1113 Reply Likes
@Linda - can you find out from those users if they mount the NAS with SMB or AFP?
Photo of Yvon Daigle

Yvon Daigle

  • 4 Posts
  • 2 Reply Likes
It is not the NAS, I cannot exported files on my PC drive.
Photo of avpman

avpman

  • 115 Posts
  • 82 Reply Likes
Respectfully, Rikk why doesn't Adobe test this themselves? Instead of relying on wasting the time and patience of PAID users who have the right to expect a working product. Doesn't Adobe do any regression testing before a new release?
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5353 Posts
  • 1113 Reply Likes
@apvman, please see Smit's post above. Since we are, as of yet, unable to reproduce the bad behavior, we are gathering additional data. 
Photo of Chris

Chris

  • 6 Posts
  • 1 Reply Like
I see this issue has been reported on another forum as well: https://forums.adobe.com/thread/2621939
Photo of Roelof Moorlag

Roelof Moorlag

  • 158 Posts
  • 49 Reply Likes
I can not reproduce it on my mac, can export to both local and network locations. I don’t want to try it already on my main (Windows 10) system
Photo of Cris Strange

Cris Strange

  • 2 Posts
  • 1 Reply Like
I'm having this same issue on a Windows 10 PC.  I was on the phone with Adobe for 2 hours this morning an they can't seem to fix it either.  They escalated the issue.  Waiting to hear back. 
Photo of Cris Strange

Cris Strange

  • 2 Posts
  • 1 Reply Like
I still haven't heard back from Adobe regarding this issue.  I switched the user to another computer because he was out of commission.  Installed Adobe CC and Lightroom Classic and he is now able to export.  Not sure what got corrupt on the computer under his profile but he is now working. 
Photo of Diego Terzano

Diego Terzano

  • 1 Post
  • 0 Reply Likes

i am experiencing the same issue. 
If I choose a network drive directly on the export path I get the "The specified folder is not writable". However, if I choose a subfolder from where the image is located, even if the image IS in a network folder, then it will allow to export it there. 
It appears to happen when the Export folder is in fact a network folder using a UNC path.

All my Export profiles used to work perfectly under 8.2.1

 

Please address asap.
Photo of Jay McConnell

Jay McConnell

  • 1 Post
  • 0 Reply Likes
Happening on Windows 10, all local drives, I can't export anything except to my desktop.  NOTHING on my PC has changed except updating the Lightroom.  No NAS, no file permissions, I can make a folder on the drive, I can copy on the drive, Lightroom just can't write to anywhere.  It's a bug, not user error.
Photo of Jason Byrne

Jason Byrne

  • 1 Post
  • 0 Reply Likes

I too am having this exact same problem since the update.  I cannot export images to any folder except my Desktop.  It keeps telling me "The specified folder is not writeable"

 It worked fine yesterday before the LR Classic update Version 8.3.  Once exported to the Desktop, I can cut and paste to any folder (which LR will not export to), but this is not an ideal solution, especially when it worked fine yesterday.

This has really slowed up my production work, so please Adobe, get a fix sorted ASAP.  Thanks

Thanks

Jason

Photo of Ann Hiner

Ann Hiner

  • 1 Post
  • 0 Reply Likes
Same thing here, all day long. "Specified folder is read-only" Until this is fixed I've been exporting to original folder and manually moving the files to my desired folder. Win 10
Photo of Hannes

Hannes

  • 1 Post
  • 1 Reply Like
Same problem with me, using Windows 10. I used several publishing routines to "publish" smart collections on our office LAN server. It worked fine with Lightroom 8.2.1.
Since Lightroom 8.3 writing-access to the office LAN server was denied when trying to export or publish to/on the server. Downgrading back to Lightroom 8.2.1 solved the problem.
Would be great to be informed when the bug is solved.
Thanks, Hannes (Germany)
Photo of Kallum Harris

Kallum Harris

  • 1 Post
  • 0 Reply Likes
I have also had this exact issue and spent 2 hours trying to fix updating permissions with no luck. Glad I found this
Photo of Jessica Muller

Jessica Muller

  • 1 Post
  • 0 Reply Likes
I am also having this issue, also using windows 10. as mentioned above saving to C drive seems to be working for the interim.
Photo of 99jon

99jon

  • 17 Posts
  • 2 Reply Likes

It was reported on this forum thread that if the destination in the export dialog (Export to) is set to desktop or choose later it seems to work. Maybe this is a workaround until a bug fix is available.

https://forums.adobe.com/thread/2622582


(Edited)
Photo of Lucas Swinden

Lucas Swinden

  • 1 Post
  • 0 Reply Likes
Mine won't even export to my desktop :/ 
Photo of Michael Gibbs

Michael Gibbs

  • 1 Post
  • 1 Reply Like
this also affected Windows 10 HOME. Unable to export into the users folder "Pictures" These folders are of course remapped folders which could be causing issues with the redirector and LR. Wish they would test this stuff before releasing it. To get something like this wrong is major.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5353 Posts
  • 1110 Reply Likes
Windows 10 has some issues on remapped Picture folders not working correctly. If you reset to your default Picture folder, then restart your computer, then repoint your Pictures folder to the previously mapped location, it should help. 
Photo of avpman

avpman

  • 115 Posts
  • 82 Reply Likes
What does "... reset to your default Picture folder..." mean?
Photo of Laura Shoe

Laura Shoe, Champion

  • 74 Posts
  • 47 Reply Likes
@avpman, I don't have direct experience with resetting the default Pictures folder, but I found this article with instructions.