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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-10-19T18:00:53+00:00

    The latest update is that the fix is now in Office Insider Beta channel. Fix build is 15813.10000 and that is the same build as Beta currently. The Office Team will backport the fix once it's been tested and validated but for now, we do not know an ETA yet for production. I recommend testing Beta channel and make sure the fix is working for your environment.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-19T15:24:15+00:00

    We have the same problem for some months at our company with some computers, some are really bad affected and others get it once in a while.

    Hope there is a fix soon

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-14T14:12:13+00:00

    The fix was checked into build 15813.10000. This build is just now rolling out to internal dogfood. The Office Team wants to monitor feedback and make sure it's good before it goes to production. This build should go to Office Insider Beta channel likely next week. I would recommend putting a machine on Beta to be ready for it and please share if you see any issues. We can monitor when it will get to Beta from this page, Update History for Office Beta Channel - Office release notes | Microsoft Learn.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-10-14T11:06:41+00:00

    Is there an update and eta on this bug fix? We are experiencing this behaviour more and more across our community. v2210 has the same issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-10-03T19:56:26+00:00

    Sadly still NOT fixed in 16.0.15726.20000. Been suffering since June!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments