Outlook 2016 - Save Multiple Attachments not saving to Network Drives

Anonymous
2017-12-19T21:20:43+00:00

I recently updated a user from Office 2010 to Office 2016 through Office 365, soon after the update, the user informed me that they were no longer able to use the "Save Multiple Attachments" feature in Outlook to save multiple attachments to a Network location.

This method can save files to a Local drive without an issue, but will not save to a Mapped Network folder. I have tested this on two other computers, both in a different environment, with the same results.

Files can be saved individually, even through the Save Multiple Attachments dialogue, it is only when attempting to save 2 or more files simultaneously. I'm hoping someone knows of a solution to this issue as this user can receive upwards of 10+ attachments in a single email for a project that they need to make available to a project folder.

They did not have this issue prior to the upgrade. Any thoughts or recommendations would be appreciated.

***Moved from: Office / Outlook / Microsoft Office Programming / Office 2016***

***Moved from: Office / Outlook / Other/unknown / Office 365 Home***

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
Answer accepted by question author
Anonymous
2018-02-14T07:48:49+00:00

Hi Angela,

No, right now the issue is still being investigated and there are two workarounds described in the following article, you can keep monitoring it to get the latest update about it.

  1. Save the documents to your own computer, and then copy them to the shared network drive.
  2. Save the documents one at a time to the shared network drive.

https://support.office.com/en-us/article/unable-to-save-all-attachments-to-a-shared-network-drive-4e9d1fd2-3a4b-4a22-acd0-2ff1217edd8c?ui=en-US&rs=en-US&ad=US

Regards,

Leo

Was this answer helpful?

2 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-01-12T03:20:13+00:00

Hi All,

I totally understand the inconvenience this thing may cause you. Our related team are currently working on this issue. As workarounds, you can save the attachments one by one or revert to an earlier version. Your time and understanding will be highly appreciated.

Best Regards,

Iry

Was this answer helpful?

2 people found this answer helpful.
0 comments

81 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-12-27T19:41:31+00:00

    I can confirm that this just started occurring with my users after an update on Office 2016. Local works fine. Network does not.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-28T15:24:40+00:00

    Hi Jonathon & Mikefried S,

    Under your scenarios, you can save the multiple attachments to local drives, but cannot save to third-party network location, which is out of our support scope. I apologize for the inconvenience this thing may cause you, and still recommend you to contact the related network drives support for further help.

    Thanks for your understanding,

    Iry

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-28T16:32:35+00:00

    I can understand that this is outside of your support scope, however, I have contacted VMWare, who is the support contact for my SAN at my primary office. Their statement is that this is an Outlook issue.

    As such, please direct me as to where I can make a bug report other than this forum, or elevate the status of this report, so that a software engineer can look at this, because otherwise I am afraid a solution will never be found.

    On this post, in the last week, you have three unique reports of this issue, all of us seem to have tracked it down to an issue with an update to Outlook 2016 made recently. I suspect as time goes on, more and more will be looking for a solution.

    Over the course of the next couple days, I will be attempting to incrementally roll-back my office updates in an attempt to locate the source of the issue. Should I find that, I will post that here as well.

    Was this answer helpful?

    0 comments