Lightroom Classic 8.3: Issues exporting photos to a Network Drive

  • 51
  • Problem
  • Updated 3 weeks ago
  • Solved
  • (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

  • 8 Posts
  • 5 Reply Likes

Posted 1 month ago

  • 51
Photo of Roelof Moorlag

Roelof Moorlag

  • 178 Posts
  • 52 Reply Likes
Do you work on Apple or Windows?
Photo of Chris

Chris

  • 8 Posts
  • 5 Reply Likes
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
  • 10 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 Laura Shoe

Laura Shoe, Champion

  • 80 Posts
  • 52 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

  • 2 Posts
  • 1 Reply Like
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 Stephen W

Stephen W

  • 1 Post
  • 0 Reply Likes
yep same here been exporting to a folder on my Windows 10 laptop's desktop for over a year now. And 8.3 has just killed that.  In fact it will not export at all.  "major fail!" Adobe needs to start testing their updates better before rolling them out to the masses.  
Photo of Smit Keniya

Smit Keniya, Employee

  • 223 Posts
  • 99 Reply Likes
Hi All,

Please share the Screenshot of the Securities tab from the Folder Properties using the File Explorer for the folder where you are facing this issue. Please select your user for the same.

See below for a sample


Thanks,
Smit
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 471 Posts
  • 133 Reply Likes
Smit,

This property dialog is irrelevant when the folder is located on a NAS accessed using UNC names, which seems to be the case for many affected users. In that case, the listed permissions are related to NAS users, not to Windows users. When accessing NAS resources from Windows, a user must logon with the NAS credentials, at least the first time. Then the permissions specified on the NAS apply. It seems that there's a problem with this when LR tries to access these resources.

Photo of Yvon Daigle

Yvon Daigle

  • 7 Posts
  • 3 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

  • 229 Posts
  • 110 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 GARY FIELD

GARY FIELD

  • 4 Posts
  • 0 Reply Likes
This is obviously a regression caused by a change made between v 8.2.1 and v 8.3 and it's in the permission checking code that is bypassed by selecting the "choose folder later" option.
Everyone using v8.3 with a NAS (seems like mostly Synology NAS) is seeing this problem, why don't you? Obviously not the NAS since it works fine with v8.2.1!
Photo of Tom Mickow

Tom Mickow

  • 387 Posts
  • 147 Reply Likes
"Everyone using v8.3 with a NAS (seems like mostly Synology NAS) is seeing this problem, why don't you?"

I'm guessing the folks at Adobe would love it to be that simple.  Trouble is, that's not the case.  I'm using 8.3 on Win10 with a Synology NAS and can't replicate the issues.
Photo of GARY FIELD

GARY FIELD

  • 4 Posts
  • 0 Reply Likes
As someone else implied, it must have to do with the NAS user account being used. I do have a NAS account with a different name than the Windows user name...
Photo of Tom Mickow

Tom Mickow

  • 387 Posts
  • 147 Reply Likes
Same here...Windows account & Synology account are completely different.
Photo of Jay Wilcox

Jay Wilcox

  • 2 Posts
  • 0 Reply Likes
For the record, I'm having the same problem as everyone else, but I don't even know what a "Synology NAS" is.  I am trying to publish to a shared folder on a hard drive on another PC in my home network.  Until 8.3, this worked for years without a hitch.  The export workaround works for me, but it doesn't help publishing.  I can live without publish for awhile, so I'm not rolling back to 8.2.   

Also wanted to add that I can export OR publish to a local folder with no problem whatsoever.  Only the shared drive/folder on my other Windows 10 PC has the problem.  Thanks for the action on this!
(Edited)
Photo of Thomas Hendel

Thomas Hendel

  • 6 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

  • 123 Posts
  • 89 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 GARY FIELD

GARY FIELD

  • 4 Posts
  • 0 Reply Likes
Yes, when googling this problem I saw that in version 6 they had the same problem. Obviously no regression testing is being done...
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

  • 6 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

  • 7 Posts
  • 3 Reply Likes
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

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

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5541 Posts
  • 1166 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

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

avpman

  • 123 Posts
  • 89 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

  • 5541 Posts
  • 1166 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

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

Roelof Moorlag

  • 178 Posts
  • 52 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
  • 1 Reply Like
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 Ruud Haan

Ruud Haan

  • 1 Post
  • 0 Reply Likes

Same here. It is obvious there are no issues with permissions for drives or folders because even Lightroom can write to a folder as soon as so select the folder later.






Photo of Jason Byrne

Jason Byrne

  • 3 Posts
  • 1 Reply Like

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 Jason Byrne

Jason Byrne

  • 3 Posts
  • 1 Reply Like
Just to help clarify, I'm trying to export to a Synology NAS drive.  It worked perfectly before V8.3, but will not work at all now.  I can export to my desktop and cut and paste to the NAS so I do not believe its a security issue on my system, rather than a bug in Lightroom.

Thanks
Photo of Jason Byrne

Jason Byrne

  • 3 Posts
  • 1 Reply Like
I have rolled back to V8.2.1 and the issue has gone away
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

  • 2 Posts
  • 2 Reply Likes
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

  • 5506 Posts
  • 1157 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

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

Laura Shoe, Champion

  • 84 Posts
  • 52 Reply Likes
@avpman, I don't have direct experience with resetting the default Pictures folder, but I found this article with instructions.
Photo of Smit Keniya

Smit Keniya, Employee

  • 228 Posts
  • 108 Reply Likes
Hi All,

Please share the Screenshot of the Securities tab from the Folder Properties using the File Explorer for the folder where you are facing this issue. Please select your user for the same.

See below for a sample


Also, meanwhile, could you try a potential workaround for the issue mentioned in this help doc: https://helpx.adobe.com/lightroom-classic/kb/error_export_folder.html

Thanks,
Smit
(Edited)