This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My default save location when saving documents from Word/Excel/Outlook is on network folder via folder redirection for Documents and Desktop. When i switch to new experience interface and try to save email attachment from Outlook it's trying to open the shared folder via port 80 instead SMB file share which cause an pop up display Connecting: Trying to connect to: \fileserver\share...
Microsoft® Outlook® for Microsoft 365 MSO (Version 2206 Build 16.0.15330.20260) 64-bit
If I manually change the default save location to point on some local folder and then navigate to the file share via "save as" dialog it browse the shared folders normally and open the network shares normally. Also if i disable the new experience switch and return to the old interface of outlook it works ok. This problem is observed only in the New experience interface for all Office products (word/excel/outlook) when the default save location is pointing to the network share.
For Word and Excel there's option for default save location
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi all,
The Outlook Support Escalation Team is working with our peers in Office and Windows to get a bug escalated for this issue. To formally track it I posted a Known Issue article, Outlook Desktop is slow to save attachments to a network path - Microsoft Support.
We can confirm, we updated to Version 2305 -16501.20196 and expirience the same issue again. It was solved with the update a few weeks ago but has returned again to probably all users in our organization.
I am on 2305 - 16501.20228 Click-to-Run
I got the issue again yesterday when saving an embedded image from the body of an email in Outlook Desktop.
The Save as Image option will always create the issue.
I don't get the issue when saving attachments but that is what used to do it.
There is a difference between the behaviour of Save As / Save All for attachments and Save Image As.
Saving an attachment defaults correctly to the Save location specified in my Outlook settings (My User Profile is a mapped drive containing My Documents)
Save as Image tries to open the location as a UNC path to the file server to the last used location in the same location that my profile home drive is mapped to.
This is clearly a coding difference and indicates this is a problem with the way 365 opens UNC paths.
I have investigated a report that this is the way that 365 calls to a network location when the network location is not using Encrypted File System (EFS) but the source file is.
Saving documents to network server is slow - Office | Microsoft Learn
Although our source folders are not using EFS our drives are using Bitlocker so the whole disk is encrypted.
I have already applied the workaround of disabling EFS in the registry of the server because it was not applied to any volumes.
It does not stop the Save as Image bug but it did seem to help with a very similar bug we were seeing with Excel both 2013 and 365. The article referenced above does say the bug has been there since Office 2010 and they haven't fixed it.
Based on that I am not betting on MS fixing this one anytime soon.
We can confirm, we updated to Version 2305 -16501.20196 and expirience the same issue again. It was solved with the update a few weeks ago but has returned again to probably all users in our organization.
So far PG has not done any backports of the fix. If nothing else changes SAEC won't get the fix until Version 2211 gets to that channel. Since that channel updates in July and January I would estimate July before it gets to SAC.
PG wants to backport, but they are investigating a possible folder redirection issue with Outlook. It's not clear yet if that is due to this change or a different bug. Not until this issue is investigated will it get considered for earlier backport to SAEC.
Assuming Office/OL desktop MS does nor support the use of an outlook connected data file on a Lan/Network/Cloud location, as it can lead to data corruption (it has never been supported)
Any connected data file should be on the local PC, the default location being \MyDocuments\Outlook Files\
And if 365 the default save location for Word etc docs being OneDrive