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-08-17T13:14:18+00:00

    I've found elsewhere you can mitigate this by disabling the WebClient service. The only issue is that I'm not sure what else this will break. I believe at the very minimum it will break Sharepoint, which I don't use so I can't test. I haven't noticed an issue with sharing files in Teams, nor have I found an issue with using Excel on the Web. I'm able to open that same spreadsheet that I have open in Excel on the Web (we use it for tracking ticket issues as a team) in Excel on my PC. So I'm a bit confused with what this service will actually break if it's anything beyond Sharepoint.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-15T19:13:14+00:00

    Same issue here, and our MS365 tenant is also through a CSP so we have no way to open a ticket directly with Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-08-15T10:42:35+00:00

    The only way to let Microsoft know about this issue is to rise a support ticket. Unfortunately I'm unable to do it as my Microsoft Office365 license is from CSP without including direct support from Microsoft. So if you experience the same problem as mine and have Office365 just rise a ticket so Microsoft can fix this.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-08-15T09:38:05+00:00

    Just to add - I have clients with the exact same issue - resolved after downgrading.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-08-08T17:17:23+00:00

    Our company has multiple clients that are all in the same boat. Have confirmed that a roll back to 2205 resolves the issue. Has MS acknowledged this bug yet?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments