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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-09-01T00:16:45+00:00

    We have dozen or so computers running version 2208 and still having same issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-09-01T12:02:02+00:00

    Thanks for the tip on WebClient!

    After looking into the WebClient service (i.e. WebDAV), here are the two workarounds that worked for us (see below). We wanted to avoid disabling the service outright.

    Workaround #1

    Block WebDAV/WebClient Traffic to your local SMB/file server from each client PC.

    Assumes you don't have HTTP/s services running on your local SMB/file server.

    #PowerShell

    $SMBServerIPs = @('192.168.111.111','1111:1111:1111:0000:0000:0567:5673:1111')

    New-NetFirewallRule -DisplayName "Block Outbound WebDAV (WebClient) Traffic to SMB File Server" `

    -Group "!!Troubleshooting (IT Dept)" `

    -Direction Outbound `

    -Protocol TCP `

    -RemotePort 80,443 `

    -Action Block `

    -RemoteAddress $SMBServerIPs

    Workaround #2

    Disable WebDAV/WebClient Traffic for Websites (that might be) running Sharepoint or Office Web Server.

    Potential issues with MS365 services(???).

    Set HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\AcceptOfficeAndTahoeServers to 0 (Default is 1) (https://docs.microsoft.com/en-us/iis/publish/using-webdav/using-the-webdav-redirector)

    Hope this helps someone else.

    D

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-09-02T13:00:08+00:00

    Workaround Solution #1 worked for standard SMB file shares but did not seem to fix for DFS Shares.

    Thanks for the Workaround

    Does anyone have a workaround for DFS ?

    Thanks

    JD

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-09-08T20:59:56+00:00

    We use DFS for our home directories. None of the other suggested changes would save us.

    We changed the office default save location to point to the mapped home drive letter (H:\ in our case) instead of the UNC path for their home directory. For whatever reason this made it work. This path can be set through settings GUI for Word and Excel but must set in the registry for Outlook.

    For this to help, you'll need to have their home folder mapped to a drive letter in ADUC or through a login script.

    https://docs.microsoft.com/en-us/outlook/troubleshoot/data-files/how-to-change-the-folder-where-emails-and-attachments-saved

    It feels like MS did something that changes the way URLs / UNC paths are handled and it tries to connect to the web ports on the file server then times out. Using a drive letter/path bypasses this new "feature".

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-09-09T15:36:34+00:00

    Hi all,

    Office has implemented some changes that should help with the network save location issues. The change was implemented in build 15617.10000. This build has just recently made it to Beta and Current Channel Preview. If you could test with either of those channels, please see if those help resolve the issues. The production build is expected to Current Channel ~9/26/22.

    Was this answer helpful?

    0 comments