Can't save download file to network share with Edge Browser

Confirmed Issue #13621874 • Assigned to Divya G.


Douglas R.
Sep 7, 2017
This issue is public.
Found in
  • Microsoft Edge
Reported by 14 people

Sign in to watch or report this issue.

Steps to reproduce

I cannot download files directly to a network share with the Microsoft Edge Browser. I can download to any local folder, but not to a network folder. The error message I get is "myfile.exe or myfile.pdf might have been moved or deleted". If I then go to the network folder, I can see the file name and partial download.

This isn’t a new problem for me, it’s been there since day one. I can download to any network share just fine with Microsoft IE or Google Chrome.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Divya G.”

      Changed Status to “Confirmed”

    • I swapped out my newer Netgear “N” with an older D-Link “G” router. So, except for the modem, it’s really a totally different network. I still have exactly the same problem. I tried changing a number of other settings and what not, but no difference.

      I just have a feeling there is probably just some setting that needs changing and all will be fine.

      At this point, I think I will just use Google Chrome, which works just fine.

    • I think the issue is either with my cable modem or my ISP (Charter). I had my son test this at his house. He has exactly the same router and basically the same network setup that I have. However, he has a dsl connection with a different ISP.

      He ran the test and was able to download without a problem. So it seems to me that it’s some kind of compatibility issue with my cable modem or ISP.

      Microsoft IE and Google Chrome work fine and do not have this problem.

    • I’ve also noticed this issue since applying the 1703 Windows 10 feature update.

      In my case the problem occurs when downloading a file, from the internet, to a Netgear RN204 share (running OS 6.8.0). However it doesn’t occur when downloading to a Synology DS215j share (running DSM 6.1.3-15152 Update 4).

      I traced the issue with Wireshark and it looks like the error is coming from the RN204, which at one point issued a “file not found” error when Edge was attempting to access the .partial file. Therefore I don’t think the problem is ISP or Router based.

      Similar to Douglas R. the problem doesn’t manifest when using other browsers.

    • Happens also for me when saving PDF files that are opened in Edge, using an AVM Fritzbox 7490 (?) router, and saving to a network share hosted by a WD MyCloud EX4100 NAS (Transfer mode set to SMB 2 protocol & share mapped as network drive). Saving to local drive works fine.

    • Snorre U

      If you try saving with a different browser, does it work OK?

    • Yes, it works. But if it doesn’t work with Edge, there’s no error message.

    • This really is a weird problem. Obviously, it doesn’t affect everyone, maybe just a few people. With my problem, it seems like a compatibility issue between Edge and my cable modem or the ISP.

      As you probably have noticed, this problem has been confirmed. Maybe with the Fall Update to Windows 10, they will get this fixed.

      Except for this problem, I do find Edge quite usable.

    • I have the same issue. I’ve applied all the latest updates (including the September 25th update) and the issue still persists. I don’t understand what edge is trying to do with the routers/modems? Doesn’t seem to make any sense since it’s just data transfers.

    • I also have the same problem. I can save the same file in another browser. I have used two different routers and even connected to a mobile hotspot with the same results. This happens on my HP envy x360, dell venue 8 pro, and Lenovo w-520.
      It’s very frustrating.

    • It’s hard to say how common this problem is. A bit of Googling doesn’t show many complaints of this exact problem. It is a problem confirmed by Microsoft though, so it’s probably not our hardware.

      It might be some unique combination of hardware and/or software that is causing the problem. After every “Patch Tuesday” I look for the problem to be resolved. So far, no resolution.

      I don’t mind using Google Chrome as my browser, but I keep getting nags from MS to try the Edge browser. Well, I would if they fixed it!

    • I just downloaded and installed the latest Windows 10 fall update. Sadly, this problem with the download to a network share has not been fixed. I was so hoping. So, I will just continue using Google chrome.

      Of course, MS will still keep wanting us to use their broken $hit Edge browser.

    • I experience the same problem. Looks like a problem with Edge saving to a Samba-share. With debug logging on, downloading from IE reports only the access to the share. When downloading using Edge, the temporary file is created and filled, the actual file is created with size 0.
      smb reports:

      smbd[21120]: smbd/posix_acls.c:1762(create_canon_ace_lists)
      smbd[21120]: create_canon_ace_lists: unable to map SID S-1-5-21-etc. to uid or gid.

      smbd[21120]: smbd/posix_acls.c:1762(create_canon_ace_lists)
      smbd[21120]: create_canon_ace_lists: unable to map SID S-1-15-2-etc to uid or gid.

      smbd[21120]: smbd/posix_acls.c:1762(create_canon_ace_lists)
      smbd[21120]: create_canon_ace_lists: unable to map SID S-1-15-3-etc to uid or gid.

      The first SID is the local user-account which hasn’t got the proper rights on the share.
      The second and third SID’s are Microsoft internal ID’s.

      When I save the download to an ntfs-share on a windows server in a different domain, the download works but the file gets assigned access rights for the same ID’s (which are classified as "Account Unknown (s-1-5-2 etc.)")

      It looks to me that Edge does not save the file as the user used to connect to the share but as the security identities in which it runs. That might be more secure but does pose a problem when downloading files to a share.

    • Experiencing the same issues here, just as we were adopting our customer to use the 'next gen browser’. All the symptoms Maxim v. describes are exactly the same.

    • I have had the same problem. I have my network drive attached to my netgear router. I can save my downloads to a local drive but not my network drive. The only way around it I have found is to download the files to my local drive and then cut and past them to my network drive in the Windows 10 file manager.

    • Robert F
      That’s exactly the problem that I have. I also have a Netgear router with a USB flash drive attached. I think if you try a download with Internet Explorer or Google Chrome, it will work just fine.

    • Interestingly, I had this same problem (error number) working with edge to fill a PDF form on a SMB share. I tried copying the file to my desktop and editing there, and the error persisted! Opening in Adobe Reader DC, minor edits, and a save as over the old file… then editing and saving in Edge worked again. So I think there’s something about the file itself - at least in my case.

    • Absolutely questionable design choices, which abound in the Microsoft Ecosystem lately. I think the code is all written by developers with PhDs, and zero work experience. I know I spend a lot of time training people with much more advanced degrees than I have, but no clue as to how anything actually works. They can write a thesis on the topic, but they can’t do the work.

      Saving to a network share, either in or out of a domain environment, is so basic, anyone who doesn’t address it in the initial alpha release doesn’t know what they’re doing.

    • I’m not sure how wide spread this problem is. I don’t see many people complaining about this issue. There must be some common element, a few of us share, that is causing the problem. My son has the same network hardware as I have and he doesn’t have a problem. He does have a different ISP though.

    • I also can not save files on Network storage with edge. this were tested by an german Computer Magazin, they also reproduced the Problem.
      Please fix it. thanks

    • I tested it with my home-server (ubuntu 16.04), edge do not save file.
      But with my qnap ts212, edge save files.
      So there must be a setting in the Server, that will prevent this.
      But what a Setting?

    • Believe it or not, I think the problem has been fixed! After reading Stefan H’s post, I decided to try saving a downloaded PDF to a network share. I also have a home-server (ubuntu 16.04), which Edge saved to just fine. I also have a USB drive connected to my Netgear Router and it saved to that just fine. I tried this from both a network wired computer and a wireless. It worked fine from both. Up to this point I have never been able to do this.

      This is the version of Microsoft Edge that’s installed on my computer.

      Microsoft EDGE 41.16299.15.0
      Microsoft EDGEHTML 16.16299

    • For me the problem still exist.
      I believe there is a setting in smb.conf

    • Hi Stefan,

      This really is a crazy problem! Last evening everything worked perfectly. This morning I repeated the test and now it’s not working again. Same problem as before.

      I wonder if it’s a matter of following some specific sequence that determines success or failure? I’m usually working between several different computers and browsers. Maybe it matters which one is the first to try saving to the network share.

      I will need to do some experimenting.


    • You are not alone. i have exactly the same problem.
      partial file is created but edge throws error "file moved".

      download is completed… just rename the partial file.

    • Same issue here with EDGE, the error in Edge is: This file could not be downloaded. The problem comes from EDGE and occurs with all the network folders.
      Microsoft Edge 40.15063.674.0
      Microsoft EdgeHTML 15.15063
      Thank you

    • Problem hits us too. We configured Redirected folders to a DFS Share on “Downloads” and Edge only creates a .partial file with the content and the destination file with 0 bytes.

      Then Edge tells us that this file could not be downloaded.

      Just a little byte frustrating.

      Best Regard

    • I have had the same problem on 3 computers.
      It came after the installation update W10 version 1709

      WD MyCloud 4TB with the latest firmware
      Microsoft EDGE 41.16299.15.0

      Please fix it.
      I do not have this problem with other browsers.

    • I have the same problem on my 3 computers. No problems saving to local drives then cutting and pasting…but always get error when trying to save to network drive.

      Microsoft Edge 41.16299.15.0

    • Error is still not resolved. It may not be hard for Microsoft to set up a Samba server and reproduce the problem. Only when this problem is resolved, I will be able to make friends with Edge.

    • I’ll add my name to the list. Error is still not resolved. Although the work-around to save to a local drive works, it’s very annoying to have to rename files or open a File Explorer window to ensure the down load was successful and then drag to the location you wanted. Although there may be some security benefits to Edge, I don’t enjoy the layout and lack of a menu, and as far as I can tell, the only ‘benefit’ to Edge is Big Brother’s ability to show more advertising to make things even harder to get work accomplished.

    • In Edge, Go to Settings -> View Advanced Settings -> Turn Off “Help protect me from malicious sites and downloads with Windows Defender SmartScreen” and try.

    • Amazingly, the Edge browser seems to be downloading to network shares without making the change that Damitha A. suggested. I was going to try her suggestion, but before making the change I thought I would give it one more try. To my surprise, it downloaded perfectly.

      I don’t know if it’s too early to say the problem has been fixed, but let’s hope so!

    • @Damitha A.:
      Your suggestion does not solve the Problem

      @Douglas R.:
      The problem is still there.
      Microsoft Edge 41.16299.248.0

    • Correct, The problem is still there.
      In Edge 41.16299.248.0

      Do they only change the version numbers at Microsoft?

    • I have the same problem.
      i.e. If I download any file via Microsoft Edge - it works fine if I save to the default C: drive location, however, when I try to save to my Y: drive, which is mapped to a network share, it fails with this message: xxx might have been moved or deleted, where xxx is the file to be downloaded. In the intended folder on Y: there are two files, the first with the xxx filename but 0 length and a second with this extension added to xxx: weh5r9o.partial.
      If I repeat the exercise with Firefox or Chrome it works fine.
      I am using Microsoft Edge 41.16299.402.0, running on Windows/10 Home 1709 16299.402
      I see from this thread and many others on Google, I am not alone with this problem - Does Microsoft intend to fix it, or am I wasting my time with Edge?

    • Exact same problem:
      Edge-Version: 42.17134.1.0
      Windows 10: 1803 (Build 17134.48)
      Networkshare: NAS-Storage (SMB-Share)

    • Upvote. Has been an issue for several builds at this point.

    • the problem still exists here with Microsoft Edge 42.17134.1.0. I still have to switch to other browsers. Networkshare: smb-Share

    • Same problem with

      Microsoft Edge 42.17134.1.0
      Microsoft EdgeHTML 17.17134

      Fix this fast plz!! its very annoying having to delete and rename all the files!!

    • My computers are fully up to date. Problem occurs to be when saving to my SMB share on my nas device. IE, Chrome etc no problem only on Edge and how edge is trying to do something the NAS SMB share does not like or Edge does not like.

    • Matthew H
      This is exactly the same problem that everyone else is experiencing. It’s been this way a long time and no mention of a fix. Apparently, it’s not a high priority for Microsoft. I’m not sure how they expect us to use Edge when it has this problem.

    • I’m still having this issue. Perhaps we all should open a new issue on this?

    You need to sign in to your Microsoft account to add a comment.

    Sign in