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.
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.
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.