P: Issues exporting photos to a Network Drive

For what it's worth, I too discovered the problem immediately after updating to 8.3 when trying to update a long-ago-established-and-much-used published collection on a network folder.  Tried a straight export to the same network folder and had the same problem (i.e. "not writable").  Then I set up a published collection on a LOCAL drive and had no problem publishing,  I am using a fully updated Windows 10 PC. The "choose folder later" workaround is great (thanks), but helpful only on export since this option is not available for published collections.  Need a fix soon.

> Oh man, I can't say anything these days.

Victoria,

I hope there's no misunderstanding here. I do appreciate your work. I'm a premium member of your site. I've never considered you as an Adobe evangelist. Just, you should take into account the enormous frustration that is generated among many customers by the way Adobe manage their business and their software. Every post that is apparently "defending" Adobe (be that true or not) can generate irritated reactions.

Like you, I always want to be positive but very frankly, their behavior is questionable. I'm a former developer and system engineer. I have taught software engineering for years. Lightroom is an open book about their internal difficulties and I don't observe any attempt to do something about that. Regression testing obviously bypassed, bugs lasting since years, trend to consider that problems are on the user's side, ready-made answers (the famous "rollback-reinstall-reset" trio mentioned above),... This kind of behavior always appears in monopolistic situations. They should be cautious, though.

I upgraded yesterday, to try the new Texture feature, and I'm hitting the same problem when I try to export.  Shame there wasn't any warning, and that the upgrade was still being offered when there's such a significant bug.

Yes, the work around works for me, but I've wasted an hour trying to find the cause.

The same for me. Publish services which had a OneDrive folder as a destination have stopped working with the error "Folder is not writable". 
I'm able to use the "workaround" for Export, but not for Publish services. And actually Publish services are the comfortable way of burning jpegs, without them exporting photos becomes a pain for me.

Oh man, I can't say anything these days. 

• I'm not saying it's not a bug.
• I'm not saying Adobe shouldn't fix it ASAP.
• I'm not saying that rolling back or using a workaround is a permanent solution. 

I alerted my readers to it because some may be affected, and I wanted them to know where to come for information if they were.

I haven't told people not to upgrade, because most people clearly aren't affected and will want to benefit from the new features. Of course that doesn't make it any less of a problem for the people who are affected.

If you are affected, this is the right place to find out the latest information and help Adobe figure out why they can't reproduce this bug yet. That'll get the solution we all want much quicker. And in the meantime, rolling back is a reliable workaround.

Wow, I cannot believe what Victoria has said above.

The workaround does NOT work for existing publish services, which cannot change the destination once they were set up. And a lot of people, like me, have many publish services, which renders creating new ones is not an option, either.

Telling a paid user not to use the latest version and rolling back to an old version is not a solution at all. We might be forced to roll back WHILE ADOBE IS FIXING THE CODES, but it is definitely not a solution without filling it as a bug.

This is absolutely not the reason we are paying for the subscription. Contrarily, we are paying for continuously bug fixing, new features, quality improvement, and good customer support. Again, telling a paid user to roll back as a solution is totally unacceptable.

All my files are on my NAS. I can export on the original directory but not on an others directory.

Somewhere above it was stated no NAS no problem, not true. I do not have the issue, but both in this feedback site and over at https://forums.adobe.com/community/li... customers without NSS are having the problem. look at
No Export after update
"The specified folder is not writeable" during Export after update to LR Classic 8.3
All folders on Synology NAS are write protected
Exportproblem nach update auf LR 8.3
Lightroom 8.3 unable to write to hard drive after update
export message "the specified folder is not writable"?
Lightroom Classic 8.3 error "the destination folder is not writable"

I have rolled back to V8.2.1 and the issue has gone away

Victoria,

Rollback, reinstall, reset (your preferences) : indeed, these are the 3 words that anyone wanting to update a version of Lightroom should learn.

The fact that not everyone is affected doesn't mean anything and it's not a indication that it's not a bug. It is one, obviously. When a developer changes something in the code and a program feature no longer works afterwards while nothing changed in the user's environment, how to call this other than a bug ? We can't reproduce so we don't file this as a bug. Interesting. Is this how code quality is measured at Adobe ?

I'm rather irritated by this kind of Pavlovian reflex at Adobe tending to systematically insinuate that we are the problem. The main problem at Adobe is the ever declining  quality of the code. They are now unable to release a new version without breaking something. And this didn't start with version 8.3 of LR.  Each time, it's a loss of time (and sometimes of data) for many users. This indicates problems

- with the development methodology and tools  (LUA, OMG, why LUA ?)
- with the quality insurance dpt.

Anyone having experience in software development and observing what's happening can draw the same conclusion.