Microsoft Edge can't open files (HTML, PDF etc.) stored on NAS

Hi,

Thank you for your interest in Windows 10.

Are you able to open HTML or PDF files stored locally using Edge?

Is the issue specific to a particular file saved on NAS?

Try the following methods and check if it helps.

Method 1:

1. Double-click the ‘.html’ file.

2. In the Open File-Security Warning dialog box, click to clear the Always ask before opening this file check box.

3. Click Open.

Method 2:

1. Right-click on the ‘HTML’ file and click ‘Properties’.

2. Click Unblock.

3. Double-click the ‘.html’ file to open the file.

Also refer to the thread below and check if it helps:

http://answers.microsoft.com/en-us/windows/forum/apps_windows_10-msedge/microsoft-edge-doesnt-open-some-pdf-files-if-they/b2ff7318-4367-4169-82fa-3853a7d6c163

Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

I can open all files stored locally in Edge.

The problem is just with files, stored on the NAS and opened through File Explorer. If I do that Edge says that the file can't be found. What kind of file (html or pdf) doesn't matter.

I have the same problem. Samething happens with Edge and network printer

I have the same (similar) problem. I develop a number of htm / html files and they are stored on a local file server. I my case "Z" drive. I tried your suggestions and none of them work for me to open the file(s) in Edge. They will open fine in IE11 or any other browser, but Edge appears to want to go first to the web and look for the file. Of course it is not there. As an example...Edge returns:  

• Make sure you’ve got the right URL:ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///Z:/Bertie2/Double_click_to_start.htm

This is a local file really. There is no file security warning or Unblock in the properties.

I THINK Edge is assuming any HTML (or ASP, or PHP, etc.) is a web file and therefore ...go to the web. This is not always the case, especially for web developers.

I get the same error when trying to open a pdf located on a NAS or on another pc in the network it is always the same error.

Make sure you’ve got the right URL: ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///F:/

So it is pointless of having a browser opening only local files when most of us store files on NAS or on a server.

Hopefully there is a fix for this.

Did further testing and the issue is seems only to appear if I open from a mapped network drive if I open file from \\server\files\test.pdf it works but if I open it from F:\test.pdf then the dns error occurs.

Yes, I duplicated the same behavior: works when navigating to file in file explorer using \\server... and double-clicking the file, but fails if navigating to the file in file explorer using mapped drive letter.

Clearly appears to be a bug to me.

I have the same problem here:

ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///S:/Documents/path/file.pdf

Drive S is a mapped network drive. The file server is a Mac mini Server.

If I copy the pdf file to the local computer, I can open it in edge without any problem.

Accessing the file on the mapped network drive with Adobe Acrobat Reader is also working fine.

I have encrypted files on my local drive (using boxcryptor), which map to a new drive when decrypted.  I have to copy PDF files to my regular drive in order to open them, they won't open from the mapped drive using Edge or Reader.  I didn't have these kind of problems before upgrading to Windows 10.  Chrome will open them from the mapped drive, but I can't edit the PDFs from Chrome (for example can't sign them with the stylus on Surface Pro 3). 

This is not even something on a NAS or network, it's all in my local drive.  Seems a bug with mapped drives.

      

Your solution does not work.  I can't get Edge to open a file on a network drive, but the exact same file on my C drive can be opened.

I've tried accessing the file on the network via a mapped drive ("L:\filename.html") and via DFS ("\\my.dfs\someshare\filename.html")

This is a BIG problem.  Microsoft OS (Windows 10), Microsoft Browser (Edge), Microsoft network authentication, but it still does not work.