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.
Just wanted to say that this issue popped up for, so far, 2 users in our company too. Hope the update fixes this soon and thanks already! :)
I will post back when there is more information JD. The Office Team is working on the fix but there is no estimate yet for release date. Like most fixes it should go to the Beta Channel first so if you want to do validation, setup a machine on Beta and you can test as soon as it is ready.
Can you update us when it is fixed or should it expected to be fixed in the October Monthly Enterprise Release ?
Thanks
JD
I checked the bug and there was a regression that caused a crash in some situations. The fix has been pulled for Version 2209. It is being actively worked on but there is no new ETA for the fix yet.
I still have users on v2209 build 15629.20156 having the issue.