Outlook New Experience update - network save location bug

Anonymous
2022-07-21T05:58:48+00:00

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

Outlook | Windows | Classic Outlook for Windows | For home

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.

0 comments

78 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-11-15T22:03:10+00:00

    The fix is available in the Office Beta channel and Current Channel Preview in builds 15813.10000 and higher. The fix will go to Current Channel production ~11/28/22 with Version 2211. Monitor the Update History page to see when Version 2211 goes to production Current Channel, Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn. If you have the option, I would test it in Current Channel Preview and confirm it addresses the issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-11-15T16:51:17+00:00

    Not sure exactly how to "follow" this thread so I am posting this reply and ticking the notification box.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-11-08T15:29:15+00:00

    The fix is still just at the Office Beta channel in builds 15813.10000 and higher. Once the fix gets some testing in Beta it will be backported to production channels. If backports are not done soon I would expect the fix to get to production with Version 2211 on about ~11/28/22. We can monitor the Update History page to see when Version 2211 goes to production Current Channel, Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-11-08T15:03:26+00:00

    Adding that our org is experiencing the same issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-10-20T06:57:12+00:00

    I will try it out.

    Thank you!

    Was this answer helpful?

    0 comments