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 No comments

78 answers

Sort by: Most helpful
  1. Anonymous
    2023-05-24T20:34:41+00:00

    Any updates on this?

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2023-03-27T11:05:25+00:00

    Any update on this?

    We are running the latest version of SAEC and still having the same issue if the Web Client service is not set to Disabled.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-24T11:50:40+00:00

    Looks like PG missed getting this fix into the CC release notes. The fix is in Version 2211 in Current Channel.

    The fix will get to MEC shortly when it updates to Version 2211. That should happen mid to late Jan 2023.

    Semi Annual Enterprise Channel was updated in our environment to 2208 15601.20456 - which still contains this issue.

    Previous channel version 2202 did not have this issue.

    When will Semi Annual Enterprise Channel receive a fix for this issue?

    We have resorted to disabling the Web Client service for now.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-01-05T15:23:25+00:00

    Looks like PG missed getting this fix into the CC release notes. The fix is in Version 2211 in Current Channel.

    The fix will get to MEC shortly when it updates to Version 2211. That should happen mid to late Jan 2023.

    Was this answer helpful?

    0 comments No comments