Forum Discussion
GETTING ERROR WHILE OPENING A DOWNLOADED FILE
Issue is getting only in Edge browser. IE and Chrome works properly
Looks like issue is with File name .
File Name:
\\rdt.XXX.net\dfs\Braxxxx\Workgroup\Axxx\Projects\(G) Automated xxxxx\(R) Monthly_xxxxxx_Setting\2020\1. XXXs\RAW_SAW\Mapping XXXXX 1 7 2020.xlsx
Content Type application/octet-stream
TSPORTE310 wrote:Please see the version. File opening properly in all other ways( folder, other browsers). I assume the file path used by Edge is not properly passing.
Microsoft Edge 44.18362.449.0
Microsoft EdgeHTML 18.18362
Well sorry but you posted in the wrong section. you are using the legacy (old) Edge browser.
and its community is here:
https://techcommunity.microsoft.com/t5/microsoft-edge/ct-p/MicrosoftEdge
it's going to be replaced by the new Edge browser (based on Chromium) in January 15 (2 days later)
you can download it from here:
https://www.microsoftedgeinsider.com/en-us/
it's very likely that the new Edge won't be having that problem you are experiencing.
if you are using Windows 10 version 1803 and above and Pro or Home edition, you will be receiving it from the Windows update automatically and it will replace the legacy Edge.
more info:
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates
https://docs.microsoft.com/en-au/deployedge/microsoft-edge-blocker-toolkit
5 Replies
- Hi,
Which Edge insider channel/version are you using?
From the screenshot, it looks like a problem with Excel failing to open that file. it could be also that Edge didn't download that file properly or 100%.Please see the version. File opening properly in all other ways( folder, other browsers). I assume the file path used by Edge is not properly passing.
Microsoft Edge 44.18362.449.0
Microsoft EdgeHTML 18.18362
TSPORTE310 wrote:Please see the version. File opening properly in all other ways( folder, other browsers). I assume the file path used by Edge is not properly passing.
Microsoft Edge 44.18362.449.0
Microsoft EdgeHTML 18.18362
Well sorry but you posted in the wrong section. you are using the legacy (old) Edge browser.
and its community is here:
https://techcommunity.microsoft.com/t5/microsoft-edge/ct-p/MicrosoftEdge
it's going to be replaced by the new Edge browser (based on Chromium) in January 15 (2 days later)
you can download it from here:
https://www.microsoftedgeinsider.com/en-us/
it's very likely that the new Edge won't be having that problem you are experiencing.
if you are using Windows 10 version 1803 and above and Pro or Home edition, you will be receiving it from the Windows update automatically and it will replace the legacy Edge.
more info:
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates
https://docs.microsoft.com/en-au/deployedge/microsoft-edge-blocker-toolkit
